Date: Wed, 06 Nov 2002 18:40:50 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> 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: <3DC9D2B2.A1AB271@mindspring.com> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <3DC9B61F.922DAB3D@mindspring.com> <20021107005513.GA24375@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > > 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. I'm more concerned about this happening again, the next time someone decides another symbol shouldn't be exposed. If we could get the pain over with all at once, that'd be a good thing. -- Terry 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?3DC9D2B2.A1AB271>