Date: Sat, 2 Nov 2002 10:34:44 -0800 From: Alfred Perlstein <alfred@FreeBSD.ORG> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/stdio findfp.c Message-ID: <20021102183444.GM24139@elvis.mu.org> In-Reply-To: <20021102180404.GA28779@troutmask.apl.washington.edu> References: <200210310154.g9V1sRiC017013@repoman.freebsd.org> <20021031015818.GU24139@elvis.mu.org> <20021102180404.GA28779@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* Steve Kargl <sgk@troutmask.apl.washington.edu> [021102 10:04] wrote: > On Wed, Oct 30, 2002 at 05:58:18PM -0800, Alfred Perlstein wrote: > > * Alfred Perlstein <alfred@FreeBSD.org> [021030 17:55] wrote: > > > alfred 2002/10/30 17:54:27 PST > > > > > > Modified files: > > > lib/libc/stdio findfp.c > > > Log: > > > Make __sF static. This can not be allowed to exist in 5.x. > > > > My suggestion is to use: > > portupgrade -aF > > after an installworld and things will be fine. > > > > If this is truly too upsetting for some then I recommend that you > > submit a patch to add a make.conf knob for your special case. > > > > I'd much prefer to cut the cord now than to have this bleed over > > into 5.x. > > > > This breaks commercial third party software, which > cannot be easily updated by portupgrade -aF. > > kargl[206] f95 -o a a.f90 > /usr/local/lib/NAGWare/libf96.so: undefined reference to `__sF' > collect2: ld returned 1 exit status > > f95 is NAG's Fortran 95 compiler. It translates Fortran 95 into > C, then hands the C to gcc to complete the compilation. It > does the equivalent of > > f95 -c -o a.c a.f90 > gcc -o a a.c -lf96 -lm -lc > > libf96.so was compiled on a 4.2 system. libm.so and libc.so > are compiled on 5.0. Before Peter backed out his last attempt > to kill __sF, he helped find a hackish work-around. It is > documented here: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=1755928+1759974+/usr/local/\ > www/db/text/2002/freebsd-current/20021013.freebsd-current > > One other work-around may be to directly relink libf96.so to > /usr/lib/compat/libc.so.4. I don't know if this is possible. The simplest fix is to simply locally revert my change until this vendor supplies a binary for 5.x. Either that or compile your code on a 4.x system or in such a way that it links against libc.so.4. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021102183444.GM24139>