From owner-freebsd-current Sun Nov 3 7:48:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F17F137B401; Sun, 3 Nov 2002 07:48:54 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 872BD43E6E; Sun, 3 Nov 2002 07:48:54 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.5) with ESMTP id gA3FmqeZ034074; Sun, 3 Nov 2002 07:48:53 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id gA3Fmq5e034073; Sun, 3 Nov 2002 07:48:52 -0800 (PST) Date: Sun, 3 Nov 2002 07:48:52 -0800 From: Steve Kargl To: Juli Mallett Cc: "M. Warner Losh" , freebsd-current@FreeBSD.ORG Subject: Re: __sF Message-ID: <20021103154852.GB33995@troutmask.apl.washington.edu> References: <20021102181031.GB28779@troutmask.apl.washington.edu> <20021102185841.GZ62585@procyon.firepipe.net> <20021102190642.GA28971@troutmask.apl.washington.edu> <20021102.174008.16163522.imp@bsdimp.com> <20021103005033.GC30494@troutmask.apl.washington.edu> <20021103032859.B5174@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021103032859.B5174@FreeBSD.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 03, 2002 at 03:29:04AM -0800, Juli Mallett wrote: > * De: Steve Kargl [ Data: 2002-11-02 ] > [ Subjecte: Re: __sF ] > > On Sat, Nov 02, 2002 at 05:40:08PM -0700, M. Warner Losh wrote: > > > In message: <20021102190642.GA28971@troutmask.apl.washington.edu> > > > > > > You should be linking against the -stable versions of these items as > > > well as the libc.so.4. If you don't, then you are asking for > > > problems. Maybe you can kludge it to make libc.so.5 work, but the > > > whole reason that it is .5 and not .4 is that it is not binary > > > compatible with .4, and for more reasons than just __sF. > > > > Fine, I'll try to set up a cross build enviroment. > > But, we need to then install a complete set of 4.x > > libraries in /usr/lib/compat. > > No, that's for runtime compatability. You want a true cross environment. > > Read any of the thousands of pages about setting up GCC for cross-platform > development, as that's what you're doing. You just happen to have a chance > of running the cross-created things locally. > Let's say I have an 4.7 app linked against libcam.so. Now, I update to 5.0. What library will this app use? There isn't a COMPAT4X library available and the 5.0 has the same version number and libcam.so has a reference to __sF. There probably aren't many apps that use libcam, so this is perhaps stretch. Well, consider libm.so and the 8000 ports. As to my particular problem, a cross-platform environment won't be of much use because NAG hard-coded several paths into their app, e.g., /usr/bin/cc. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message