Bug 80698

Summary: Explicitly calling __xuname() has bad effect!
Product: Base System Reporter: huver <huver>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description huver 2005-05-06 15:40:01 UTC
      /usr/include/sys/utsname.h:

Declaring "uname()" to be a static inline calling __xuname()" is causing problems.  Many *.so libs in ported packages now all directly calls for
__xuname(), so legacy 3.x/4.x binaries using these *.so libs don't work
anymore -- these binaries do not refer to libc.so.5.

Fix: 

Remove the section defining uname() to be calling __xuname().
Rebuild packages.  Or, remove compat3 and compat4 so to make it clear
that those binaries will very likely fail to start.
Comment 1 huver 2005-05-09 16:23:08 UTC
     Another fix, is for the compat3/4 libc.so.3/4 to include __xuname()
Comment 2 Kris Kennaway 2005-05-11 00:54:03 UTC
On Fri, May 06, 2005 at 02:31:45PM +0000, Huver wrote:
> 
> >Number:         80698
> >Category:       misc
> >Synopsis:       Explicitly calling __xuname() has bad effect!
> >Confidential:   no
> >Severity:       serious
> >Priority:       high
> >Responsible:    freebsd-bugs
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Fri May 06 14:40:01 GMT 2005
> >Closed-Date:
> >Last-Modified:
> >Originator:     Huver
> >Release:        5.4 RC4
> >Organization:
> >Environment:
> FreeBSD test.amgraf.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Tue May  3 16:54:28 CDT 2005     root@amgraf.com:/usr/obj/usr/src/sys/GENERIC  i386
> >Description:
>       /usr/include/sys/utsname.h:
> 
> Declaring "uname()" to be a static inline calling __xuname()" is causing problems.  Many *.so libs in ported packages now all directly calls for
> __xuname(), so legacy 3.x/4.x binaries using these *.so libs don't work
> anymore -- these binaries do not refer to libc.so.5.

Please provide more details.  What combination of libraries causes the
problem?

Kris
Comment 3 Kris Kennaway freebsd_committer freebsd_triage 2005-05-11 00:54:07 UTC
State Changed
From-To: open->feedback

Feedback requested
Comment 4 Kris Kennaway freebsd_committer freebsd_triage 2005-07-30 01:58:39 UTC
State Changed
From-To: feedback->closed

Feedback timeout