From: "Fehringer Franz" <Franz.Fehringer@fja.com>
To: <gcc-help@gnu.org>, <gcc@gnu.org>
Subject: AW: AIX link error with g++ 4.4.0
Date: Wed, 10 Jun 2009 09:26:00 -0000 [thread overview]
Message-ID: <3DD4561E58DC6D4690B05037024D58490320DCEB@m-s-app130.global.fjh.com> (raw)
In-Reply-To: <3DD4561E58DC6D4690B05037024D58490320DCE9@m-s-app130.global.fjh.com>
_____________________________________________
Von: Fehringer Franz
Gesendet: Mittwoch, 10. Juni 2009 10:55
An: 'gcc-help@gnu.org'; 'gcc@gnu.org'
Betreff: AIX link error with g++ 4.4.0
Hello all,
I have exactly the same error like described in
http://gcc.gnu.org/ml/gcc-help/2009-05/msg00323.html
namely
collect2: library libstdc++ -lsupc++ not found
I have a POWER6 with AIX 6.1.2, for the build --disable-shared was used
(i think this is the reason why this error does not show up in regular
shared library builds).
When i invoke g++ with both -v and -save-temps and then invoke the final
collect2 step manually (using cut and paste) the link succeeds.
According to my investigations, the reason for this kind of failure is
* collect2 is executed via execvp in gcc.c resp. pex-unix.c
* the link line (i.e. the collect2 invocation) contains -lstdc++
-lsupc++ since we are in the C++ realm.
* The error now is, that -lstdc++ -lsupc++ is given in the execvp
argument vector as one argument instead two separate arguments.
* As a result the call to resolve_lib_name in collect2.c fails,
since it can handle only one -lxxx per call and not multiple ones.
Should i file a bug report and is there an easy resolution?
Best regards
Franz
next parent reply other threads:[~2009-06-10 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DD4561E58DC6D4690B05037024D58490320DCE9@m-s-app130.global.fjh.com>
2009-06-10 9:26 ` Fehringer Franz [this message]
2009-06-10 15:32 ` Ian Lance Taylor
2009-06-10 15:44 ` Dave Korn
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=3DD4561E58DC6D4690B05037024D58490320DCEB@m-s-app130.global.fjh.com \
--to=franz.fehringer@fja.com \
--cc=gcc-help@gnu.org \
--cc=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).