Date: Fri, 6 May 2005 14:31:45 GMT From: Huver <huver@amgraf.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/80698: Explicitly calling __xuname() has bad effect! Message-ID: <200505061431.j46EVjob092998@www.freebsd.org> Resent-Message-ID: <200505061440.j46Ee1m7099738@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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.
>How-To-Repeat:
>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.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505061431.j46EVjob092998>