On Sun, Nov 03, 2002 at 03:29:04AM -0800, Juli Mallett wrote: > * De: Steve Kargl <[EMAIL PROTECTED]> [ Data: 2002-11-02 ] > [ Subjecte: Re: __sF ] > > On Sat, Nov 02, 2002 at 05:40:08PM -0700, M. Warner Losh wrote: > > > In message: <[EMAIL PROTECTED]> > > > > > > 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
