From: Andreas Schwab <schwab@suse.de>
To: howarth@bromo.msbb.uc.edu (Jack Howarth)
Cc: gcc@gcc.gnu.org
Subject: Re: strange error on gcc 4.1.0
Date: Sat, 30 Jul 2005 09:50:00 -0000 [thread overview]
Message-ID: <jewtn8aah8.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050730084400.625CD1DC154@bromo.msbb.uc.edu> (Jack Howarth's message of "Sat, 30 Jul 2005 04:44:00 -0400 (EDT)")
howarth@bromo.msbb.uc.edu (Jack Howarth) writes:
> I am trying to build xplor-nih on MacOS X 10.4 using gcc 4.1.0
> branch's gcc and g++ instead of Apple's and am running into a really
> strange error. I find the following linkage fails...
>
> g++-4 -bundle -flat_namespace -undefined suppress _xplorWrap.o libswigpy-xplor.dylib -o _xplorWrap.so -L/Users/howarth/Desktop/xplor-nih-2.11.2.1/bin.Darwin_8/ -lcommon -lnmrPot -lintVar -lvmd -lpy -lswigpy-xplor \
$ info gcc 'Target Options'
[...]
`-b MACHINE'
The argument MACHINE specifies the target machine for compilation.
[...]
The `-V' and `-b' options work by running the
`<machine>-gcc-<version>' executable, so there's no real reason to use
them if you can just run that directly.
> Shouldn't the stock gcc 4.1.0 support the -bundle flag?
It's an Apple-specific flag.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-07-30 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 8:47 Jack Howarth
2005-07-30 9:50 ` Andreas Schwab [this message]
2005-07-30 13:42 Jack Howarth
2005-07-30 15:18 ` Andrew Pinski
2005-07-30 15:55 Jack Howarth
2005-07-30 16:09 ` Andrew Pinski
2005-07-31 4:44 ` Mike Stump
2005-07-30 16:15 Jack Howarth
2005-07-30 16:22 Jack Howarth
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=jewtn8aah8.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.msbb.uc.edu \
/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).