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 target/41605] Static linking of libgcc/libgfortran/libstdc++ can cause inconsistent symbol resolution.
Date: Tue, 06 Oct 2009 15:57:00 -0000 [thread overview]
Message-ID: <20091006155649.26152.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41605-17110@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from developer at sandoe-acoustics dot co dot uk 2009-10-06 15:56 -------
Created an attachment (id=18727)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18727&action=view)
make sure that static linking of libraries is consistent
this patch provides:
(a) new spec with direct resolution for libgomp that provides a static version
LINK_COMMAND_SPECS for darwin and darwin9+
(b) file replacement specs for libstdc++.
dependencies:
if static libgcc => link libgomp, libgfortran, libstdc++ statically
if static libstdc++ || libgfortran || libgcc link libgomp statically.
bootstrapped on powerpc-apple-darwin8, i686-apple-darwin9.
object checked by hand with otool for correct library refs, reg-tested for
check-target-libgomp {m32,m64}{-static-libgcc,
static-libgfortran,static-libstdc++,}
Note static-libstdc++ will not work without changes on PR4194/PR4196
log:
*gcc/config/darwin.h(LINK_COMMAND_SPEC): Resolve fopenmp specifically
for target
(LINK_SPEC): replace dynamic libraries by static equivalents where
necessary
*gcc/config/darwin9.h(LINK_COMMAND_SPEC): Resolve fopenmp specifically
for target
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41605
next prev parent reply other threads:[~2009-10-06 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 15:46 [Bug target/41605] New: " developer at sandoe-acoustics dot co dot uk
2009-10-06 15:57 ` developer at sandoe-acoustics dot co dot uk [this message]
2009-10-06 17:08 ` [Bug target/41605] " developer at sandoe-acoustics dot co dot uk
2009-10-08 16:36 ` mrs at gcc dot gnu dot org
2009-10-08 16:44 ` mrs at gcc dot gnu dot org
2009-10-14 11:20 ` developer at sandoe-acoustics dot co dot uk
2009-10-14 13:28 ` mrs at gcc dot gnu dot org
2009-12-22 22:12 ` janis at gcc dot gnu dot org
2009-12-31 1:35 ` davek at gcc dot gnu dot org
2009-12-31 11:40 ` howarth at nitro dot med dot uc dot edu
2009-12-31 17:07 ` developer at sandoe-acoustics dot co dot uk
2009-12-31 20:42 ` jakub at gcc dot gnu dot org
2010-01-02 22:51 ` kargl at gcc dot gnu dot org
2010-01-03 22:46 ` rguenth at gcc dot gnu dot org
2010-01-04 11:49 ` developer at sandoe-acoustics dot co dot uk
2010-01-22 9:39 ` developer at sandoe-acoustics dot co dot uk
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=20091006155649.26152.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).