Date: Sat, 02 Nov 2002 17:37:17 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: sgk@troutmask.apl.washington.edu Cc: kris@obsecurity.org, adamk@voicenet.com, mark@grondar.org, freebsd-current@FreeBSD.ORG Subject: Re: __sF Message-ID: <20021102.173717.69849790.imp@bsdimp.com> In-Reply-To: <20021102181031.GB28779@troutmask.apl.washington.edu> References: <20021102102110.A874-100000@sorrow.ashke.com> <20021102174726.GA9686@xor.obsecurity.org> <20021102181031.GB28779@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20021102181031.GB28779@troutmask.apl.washington.edu>
Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
: On Sat, Nov 02, 2002 at 09:47:26AM -0800, Kris Kennaway wrote:
: > On Sat, Nov 02, 2002 at 10:35:03AM -0500, Adam K Kirchhoff wrote:
: >
: > > So is the current position on the matter that __sF is going to remain out
: > > of libc?
: >
: > Yes.
: >
:
: This will break some commercially available software that
: can't easily replaced.
:
: kargl[248] f95 -V a.f90
: NAGWare Fortran 95 compiler Release 4.2(468)
: Copyright 1990-2002 The Numerical Algorithms Group Ltd., Oxford, U.K.
: f95comp version is 4.2(468)
: /usr/local/lib/NAGWare/libf96.so: undefined reference to `__sF'
: collect2: ld returned 1 exit status
:
: I seriously doubt that NAG will support both a
: 4.x and 5.x version of their compiler.
Then you should force it to link with libc.so.4. That's the version
of libc that it build libf96.so against, so you are taking a big
chance having it use libc.so.5.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021102.173717.69849790.imp>