public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63610] Fixing the libtool bug for Yosemite (darwin14)
Date: Fri, 14 Nov 2014 11:19:00 -0000 [thread overview]
Message-ID: <bug-63610-4-4vLaE3kxzK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63610-4@http.gcc.gnu.org/bugzilla/>
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.
prev parent reply other threads:[~2014-11-14 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 18:36 [Bug target/63610] New: OSX 10.10 (Yosemite) segfault in MPIR testsuite with -O0 or -O1 vbraun at physics dot upenn.edu
2014-10-21 18:37 ` [Bug target/63610] " vbraun at physics dot upenn.edu
2014-10-21 18:37 ` vbraun at physics dot upenn.edu
2014-10-21 19:15 ` vbraun at physics dot upenn.edu
2014-10-23 13:22 ` vbraun.name at gmail dot com
2014-10-23 13:56 ` vbraun.name at gmail dot com
2014-10-27 12:48 ` howarth at bromo dot med.uc.edu
2014-10-27 13:07 ` howarth at bromo dot med.uc.edu
2014-10-27 13:13 ` vbraun.name at gmail dot com
2014-11-11 9:15 ` [Bug target/63610] Fixing the libtool bug for Yosemite (darwin14) fxcoudert at gcc dot gnu.org
2014-11-11 20:25 ` fxcoudert at gcc dot gnu.org
2014-11-12 22:44 ` fxcoudert at gcc dot gnu.org
2014-11-12 22:59 ` howarth at bromo dot med.uc.edu
2014-11-14 8:37 ` fxcoudert at gcc dot gnu.org
2014-11-14 8:52 ` iains at gcc dot gnu.org
2014-11-14 9:16 ` fxcoudert at gcc dot gnu.org
2014-11-14 11:19 ` howarth at bromo dot med.uc.edu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-63610-4-4vLaE3kxzK@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).