From owner-freebsd-bugs@FreeBSD.ORG  Wed May 11 00:00:25 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C360A16A4CE
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 11 May 2005 00:00:25 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id ADA8D43D2F
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 11 May 2005 00:00:24 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4B00OaA035036
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 11 May 2005 00:00:24 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4B00Oru035035;
	Wed, 11 May 2005 00:00:24 GMT
	(envelope-from gnats)
Date: Wed, 11 May 2005 00:00:24 GMT
Message-Id: <200505110000.j4B00Oru035035@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Kris Kennaway <kris@obsecurity.org>
Subject: Re: misc/80698: Explicitly calling __xuname() has bad effect!
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Kris Kennaway <kris@obsecurity.org>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2005 00:00:25 -0000

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

From: Kris Kennaway <kris@obsecurity.org>
To: Huver <huver@amgraf.com>
Cc: freebsd-gnats-submit@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@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