From: Ragnar Ouchterlony <ragnar+buildroot@lysator.liu.se>
To: buildroot@busybox.net
Subject: [Buildroot] libstdc++.la and it's libdir
Date: Sun, 04 May 2008 20:39:20 +0200 [thread overview]
Message-ID: <1209926360.20914.11.camel@localhost> (raw)
Hi,
I'm doing a personal project where I am building a new rootdisk for my
DNS-323 (an ARM machine).
I use buildroot from 20080430 (currently) with gcc-4.2.3. Although I
have a few patches to make things work, I don't have anything that
touches gcc.
Now over to my problem:
The libdir variable in libstdc++.la (residing
in /path/to/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib/libstdc++.la
file is wrong. It says:
libdir='/usr/arm-linux-uclibc/lib'
where I would have expected it to say:
libdir='?/path/to/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib'
This causes problems when using libtool. I.e, I compile a c++ libary (in
this case libsigc++-2.0) and then that library gets in it's .la file a
dependency for ?/usr/arm-linux-uclibc/lib/libstdc++.la and when I in
turn compile a program that uses libsigc++ libtool fails because it
can't find /usr/arm-linux-uclibc/lib/libstdc++.la.
If I manually edit libstdc++.la for it to point to the correct place,
things work as expected when I recompile my dependent libraries.
Have anyone else had this problem and have any idea where I should look
for a more permanent fix instead of doing things manually. I know I can
probably use sed somewhere to change the offending line, but I would
really like to know why it sets it wrong the first time around.
Any help is appreciated.
/Ragnar Ouchterlony
reply other threads:[~2008-05-04 18:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1209926360.20914.11.camel@localhost \
--to=ragnar+buildroot@lysator.liu.se \
--cc=buildroot@busybox.net \
/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