misc/80698: Explicitly calling __xuname() has bad effect!

[Kris Kennaway]

The following reply was made to PR kern/80698; it has been noted by GNATS.

From: Kris Kennaway <kris at obsecurity.org>
To: Huver <huver at amgraf.com>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: misc/80698: Explicitly calling __xuname() has bad effect!
Date: Tue, 10 May 2005 16:54:03 -0700

 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 at 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