From: howarth@bromo.msbb.uc.edu (Jack Howarth)
To: howarth@bromo.msbb.uc.edu, schwab@suse.de
Cc: gcc@gcc.gnu.org
Subject: Re: strange error on gcc 4.1.0
Date: Sat, 30 Jul 2005 13:42:00 -0000 [thread overview]
Message-ID: <20050730133848.7BFB11DC154@bromo.msbb.uc.edu> (raw)
Andreas,
Are you sure gnu gcc shouldn't support this? I see -bundle under the
Machine Dependent Options under Darwin options which are not marked as
APPLE-ONLY. I understood that to mean that it should be present in the
gnu gcc compiler (like -all_load which is in the same list and is
supported). Fortunately MacOS X 10.4 now supports a more linux-like dyload
that can use standard dynamic libraries .so files instead of just bundles
for shared library modules.
Jack
next reply other threads:[~2005-07-30 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 13:42 Jack Howarth [this message]
2005-07-30 15:18 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 16:22 Jack Howarth
2005-07-30 16:15 Jack Howarth
2005-07-30 15:55 Jack Howarth
2005-07-30 16:09 ` Andrew Pinski
2005-07-31 4:44 ` Mike Stump
2005-07-30 8:47 Jack Howarth
2005-07-30 9:50 ` Andreas Schwab
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=20050730133848.7BFB11DC154@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
/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).