Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Nov 2002 16:55:13 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Terry Lambert <tlambert2@mindspring.com>
Cc:        "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>, freebsd-current@FreeBSD.ORG
Subject:   Re: [PATCH] note the __sF change in src/UPDATING
Message-ID:  <20021107005513.GA24375@troutmask.apl.washington.edu>
In-Reply-To: <3DC9B61F.922DAB3D@mindspring.com>
References:  <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <3DC9B61F.922DAB3D@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 06, 2002 at 04:38:55PM -0800, Terry Lambert wrote:
> "Steven G. Kargl" wrote:
> > Could someone add the following patch to UPDATING?
> > Change the words to whatever suits your fancy.
> > +20021031
> > +       Revision 1.24 of lib/libc/stdio/findfp.c has made __sF static.
> > +       This changes the visibility of __sF to a symbol internal to
> > +       libc.  All applications linked against libc or a library that
> > +       depends on libc that were compiled prior to 31 Oct 2002 will
> > +       need to be updated after a "make world".  An error message that
> > +       includes "undefined reference to `__sF'" is an indication that
> > +       that application needs to be recompiled.
> > +
> 
> 
> Any chance we could get rid of all externally visable symbols that
> are not defined as being there by some standard, and not just __sF,
> since we are breaking the FORTRAN compiler and other third party
> code already?
> 

This isn't restricted to my Fortran 95 problem, which I've
found an acceptable work-around.  I just spent the better
part of a day re-installing 122 ports because these ports were
linked against an earlier libc.  All of this is 3rd party
software.  But, if you have a pre-20021031 world and you
build only a post-20021021 libc, then a whole bunch of 
libraries in /usr/lib will becomed unusable.

-- 
Steve

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?20021107005513.GA24375>