From: "F. Heitkamp" <heitkamp@ameritech.net>
To: aph@redhat.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ libstdc++ linker question.
Date: Thu, 03 May 2012 12:14:00 -0000 [thread overview]
Message-ID: <4FA2767C.4090607@ameritech.net> (raw)
In-Reply-To: <CAH6eHdTKUTYEvhS1mHGGS5LV7K6h+N5_qi1iyKXmNiXCLMpBYw@mail.gmail.com>
We really need you to answer this question:
> Is _path.so a 32-bit or 64-bit library? From the missing symbol I'm
> assuming 32-bit.
And if it is compiled 32-bit, we need to know why.
It is 32 bit. Probably because the Python it's compiled against is 32 bit?
I don't understand why the build process is not pulling in libstdc++ if _path.so needs it.
Fred
prev parent reply other threads:[~2012-05-03 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 12:40 F. Heitkamp
2012-04-30 17:28 ` Jonathan Wakely
2012-04-30 17:47 ` Jonathan Wakely
2012-05-02 11:14 ` F. Heitkamp
2012-05-02 11:37 ` Andrew Haley
2012-05-02 11:02 ` F. Heitkamp
2012-05-03 12:14 ` F. Heitkamp [this message]
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=4FA2767C.4090607@ameritech.net \
--to=heitkamp@ameritech.net \
--cc=aph@redhat.com \
--cc=gcc-help@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).