From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: g++ libstdc++ linker question.
Date: Wed, 02 May 2012 11:37:00 -0000 [thread overview]
Message-ID: <4FA11C52.9020009@redhat.com> (raw)
In-Reply-To: <4FA1170F.9060409@ameritech.net>
On 05/02/2012 12:14 PM, F. Heitkamp wrote:
> On 04/30/12 13:47, Jonathan Wakely wrote:
>> On 30 April 2012 18:28, Jonathan Wakely<jwakely.gcc@gmail.com> wrote:
>>> On 30 April 2012 13:39, F. Heitkamp wrote:
>>>
>> The matplotlib I use is built with:
>>
>> python setupegg.py build_ext \
>> --rpath=/opt/gcc-4.4.3/lib64
>> python setupegg.py build
>> python setupegg.py install --user
>>
>> The --rpath option ensures the right libstdc++.so is found at runtime
>> (we have several installed). That build works here, and is linked to
>> libstdc++.so. Unfortunately it builds matplotlib as a python egg,
>> which is a very annoying package format. I'd rather not install it
>> via egg, but have no experience doing so and can't suggest why your
>> build was not linked to libstdc++.
>
> This last suggestion did not work for me. I got the same undefined
> symbol error. My linux setup is a 64 bits kernel running on sort of a
> hybrid 32/64 bits system. By that I mean I have some 64 bits userland
> along with the 32bits. When I configure python programs using the usual
> commands it comes back with arch x86_64. Anyway I guess this is getting
> off topic for this list now, but suggestions are welcome nonetheless.
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.
Andrew.
next prev parent reply other threads:[~2012-05-02 11:37 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 [this message]
2012-05-02 11:02 ` F. Heitkamp
2012-05-03 12:14 ` F. Heitkamp
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=4FA11C52.9020009@redhat.com \
--to=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).