public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/39888] TLS emutls not linked to automatically on Darwin
Date: Fri, 25 Sep 2009 10:54:00 -0000 [thread overview]
Message-ID: <20090925105434.1384.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39888-4688@http.gcc.gnu.org/bugzilla/>
------- Comment #38 from developer at sandoe-acoustics dot co dot uk 2009-09-25 10:54 -------
(In reply to comment #37)
> I just noticed that I have been neglecting to pass
> --enable-version-specific-runtime-libs to configure. What should be the impact
> of that on the build (since I did get the expected libgcc-ext.10.4/5 files)?
> Could that be related to the build failure on x86_64-apple-darwin10?
I don't think any of this stuff makes much sense w/out
--enable-version-specific-runtime-libs; I always use this to enable multiple
versions of gcc installed on the same machine.
I don't know if that's the root of the D10 issue - somehow I doubt it (I try
not to make assumptions about future systems - and probably excluded D10
somewhere ... but hopefully I'll look at that later).
> Are you using...
> make -k check RUNTESTFLAGS="--target_board=unix/-muse-shared-libgcc-ext"
yes. should be listed in the test results.
whether this is default or not can be determined trivially (Init(1)) as and
when the approach is agreed with the relevant maintainers.
> The option behavior should be -muse-static-runtimes instead.
different objective not related to the _ext; mea culpa if that is present in
the patch;
FWIW: -muse-static-runtimes is designed to allow the building of statically
linked (save libSystem) objects on Darwin (this is to assist in deployment of
parallel jobs on clusters - or distibution of apps using more advanced features
than are standard on a given rev)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39888
next prev parent reply other threads:[~2009-09-25 10:54 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 18:39 [Bug other/39888] New: " fago at earthlink dot net
2009-04-27 19:04 ` [Bug other/39888] " developer at sandoe-acoustics dot co dot uk
2009-04-27 19:05 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:06 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:07 ` developer at sandoe-acoustics dot co dot uk
2009-04-27 19:15 ` developer at sandoe-acoustics dot co dot uk
2009-09-22 18:56 ` mrs at apple dot com
2009-09-22 19:20 ` developer at sandoe-acoustics dot co dot uk
2009-09-22 21:18 ` mrs at apple dot com
2009-09-23 3:02 ` howarth at nitro dot med dot uc dot edu
2009-09-23 15:50 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:00 ` developer at sandoe-acoustics dot co dot uk
2009-09-23 16:19 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:28 ` howarth at nitro dot med dot uc dot edu
2009-09-23 16:36 ` developer at sandoe-acoustics dot co dot uk
2009-09-23 16:51 ` howarth at nitro dot med dot uc dot edu
2009-09-23 17:53 ` howarth at nitro dot med dot uc dot edu
2009-09-23 18:41 ` howarth at nitro dot med dot uc dot edu
2009-09-23 18:57 ` howarth at nitro dot med dot uc dot edu
2009-09-23 20:44 ` mrs at apple dot com
2009-09-23 20:48 ` mrs at apple dot com
2009-09-23 20:49 ` mrs at apple dot com
2009-09-23 20:52 ` mrs at apple dot com
2009-09-23 21:06 ` howarth at nitro dot med dot uc dot edu
2009-09-23 21:18 ` howarth at nitro dot med dot uc dot edu
2009-09-23 23:45 ` howarth at nitro dot med dot uc dot edu
2009-09-24 7:47 ` developer at sandoe-acoustics dot co dot uk
2009-09-24 13:06 ` howarth at nitro dot med dot uc dot edu
2009-09-24 13:15 ` howarth at nitro dot med dot uc dot edu
2009-09-24 20:55 ` developer at sandoe-acoustics dot co dot uk
2009-09-24 22:33 ` howarth at nitro dot med dot uc dot edu
2009-09-24 22:42 ` developer at sandoe-acoustics dot co dot uk
2009-09-24 23:47 ` howarth at nitro dot med dot uc dot edu
2009-09-24 23:48 ` howarth at nitro dot med dot uc dot edu
2009-09-25 1:20 ` howarth at nitro dot med dot uc dot edu
2009-09-25 2:19 ` howarth at nitro dot med dot uc dot edu
2009-09-25 10:07 ` developer at sandoe-acoustics dot co dot uk
2009-09-25 10:45 ` howarth at nitro dot med dot uc dot edu
2009-09-25 10:54 ` developer at sandoe-acoustics dot co dot uk [this message]
2009-09-25 19:17 ` howarth at nitro dot med dot uc dot edu
2009-09-25 19:25 ` developer at sandoe-acoustics dot co dot uk
2009-09-25 23:52 ` howarth at nitro dot med dot uc dot edu
2009-09-26 0:54 ` howarth at nitro dot med dot uc dot edu
2009-09-26 1:00 ` howarth at nitro dot med dot uc dot edu
2009-09-26 2:55 ` howarth at nitro dot med dot uc dot edu
2009-09-26 5:51 ` howarth at nitro dot med dot uc dot edu
2009-09-26 17:29 ` developer at sandoe-acoustics dot co dot uk
2009-09-26 20:36 ` howarth at nitro dot med dot uc dot edu
2009-09-28 7:48 ` developer at sandoe-acoustics dot co dot uk
2009-09-28 9:02 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 16:58 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 19:46 ` mrs at apple dot com
2009-09-30 19:54 ` developer at sandoe-acoustics dot co dot uk
2009-09-30 23:36 ` howarth at nitro dot med dot uc dot edu
2009-09-30 23:38 ` howarth at nitro dot med dot uc dot edu
2009-10-01 8:36 ` developer at sandoe-acoustics dot co dot uk
2009-10-01 14:00 ` howarth at nitro dot med dot uc dot edu
2009-10-01 17:22 ` developer at sandoe-acoustics dot co dot uk
2009-10-01 19:18 ` mrs at apple dot com
2009-10-02 8:17 ` developer at sandoe-acoustics dot co dot uk
2009-10-02 10:39 ` developer at sandoe-acoustics dot co dot uk
2009-11-18 7:36 ` andreast at gcc dot gnu dot org
2009-11-18 7:37 ` andreast at gcc dot gnu dot org
2010-01-22 9:59 ` developer at sandoe-acoustics dot co dot uk
2010-03-11 3:30 ` howarth at nitro dot med dot uc dot edu
2010-03-11 12:18 ` ubizjak at gmail dot com
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=20090925105434.1384.qmail@sourceware.org \
--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).