From owner-freebsd-stable Tue Nov 14 23:20: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3BB2C37B479; Tue, 14 Nov 2000 23:19:59 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAF7JAR15566; Wed, 15 Nov 2000 00:19:10 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eAF7L2G47704; Wed, 15 Nov 2000 00:21:02 -0700 (MST) Message-Id: <200011150721.eAF7L2G47704@billy-club.village.org> To: stable@FreeBSD.ORG Subject: Re: libc shlib version Cc: Satoshi - Ports Wraith - Asami In-reply-to: Your message of "Tue, 14 Nov 2000 15:56:11 PST." <20001114155611.A94037@dragon.nuxi.com> References: <20001114155611.A94037@dragon.nuxi.com> <31309.974061923@winston.osd.bsdi.com> <200011130413.eAD4DKj41211@vashon.polstra.com> <200011131727.eADHR8c42388@vashon.polstra.com> <20001113153325.D39667@dragon.nuxi.com> <20001114081845.A76050@dragon.nuxi.com> Date: Wed, 15 Nov 2000 00:21:02 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001114155611.A94037@dragon.nuxi.com> "David O'Brien" writes: : On Tue, Nov 14, 2000 at 02:15:49PM -0800, Satoshi - Ports Wraith - Asami wrote: : > Hmm. That's a good point. So you mean there is no way to build a : > libc that works for 4.2 that will also work with a 4.0 kernel? : : Yes. Maybe I'm crazy, but can't we find and kill the API change that caused this and back it out for 4.x? I suspect it was the per interface stat changes in the network code, but I could very well be wrong. : > (I don't think just changing the libc source on a 4.0 machine will : > accomplish that. Besides, that sounds even more dangerous, to build : > something with mixed sources.) : : IF 4.2-R libc sources would compile on a 4.0-R system the resulting : libc.so.4 will work much better than using a stock 4.2-R libc.so.4. This : is because the /usr/include/sys/ and /usr/include/machine/ headers : (especially the syscall ones) used to compile the 4.2-R libc sources will : match the 4.0-R kernel. Interface changes (as exposed) in /sys/sys and : /sys//include are one of the bigger ways to get a kernel and : userland out of sync. These sorts of things aren't supposed to impact libc at all. Do we know which one caused the problem? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message