[Bug target/63610] Fixing the libtool bug for Yosemite (darwin14)

howarth at bromo dot med.uc.edu gcc-bugzilla@gcc.gnu.org
Fri Nov 14 11:19:00 GMT 2014


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610

--- Comment #18 from howarth at bromo dot med.uc.edu ---
(In reply to Francois-Xavier Coudert from comment #17)
> (In reply to Iain Sandoe from comment #16)
> > Hmm the patch for __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ has been
> > applied to 4.9 (AFAICT)
> 
> Yes it has.
> 
> 
> > although not to 4.8
> 
> You're right. Provided that the patches are simple, maybe it's good enough
> to document them (as I have in the
> __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ patch for 4.8) and let
> distributors apply them.

There is nothing in the gcc build that *needs* to have MACOSX_DEPLOYMENT_TARGET
set, however some packaging environments, like fink and MacPorts, happen to set
MACOSX_DEPLOYMENT_TARGET by default and thus triggers the configure/libtool.m4
bug...

https://trac.macports.org/ticket/44596#comment:35

The Apple programmers told of the libtool.m4 bug so far all are of the view
that configure/libtool.m4 shouldn't really be defaulting to "-undefined
dynamic_lookup" as that can mask undefined symbols in release code (but should
be default "-undefined error").

https://trac.macports.org/ticket/44596#comment:48

However that is a really libtool bug.



More information about the Gcc-bugs mailing list