From: Vania Joloboff <vania.joloboff@tsinghua.edu.cn>
To: buildroot@busybox.net
Subject: [Buildroot] Bug with gmp and mpfr
Date: Mon, 20 Apr 2009 16:29:39 +0800 [thread overview]
Message-ID: <49EC3273.5000100@tsinghua.edu.cn> (raw)
In-Reply-To: <4989680E.4010807@liama.ia.ac.cn>
Hi,
We have a problem. We have build gcc with buildroot and in most cases it
works fine.
But in one case we do not want to use the _start entry point because we
redefine it.
So we use option -nostdlib and then we explicitly want to link with
libstdc++ and libgcc
so we use a command like
g++ -nostdlib path/to/ourfiles $options -lstdc++ -lc -lgcc
We get
/usr/local/cross/arm/usr/bin/../lib/gcc/arm-linux-uclibc/4.3.2/../../../../arm-linux-uclibc/bin/ld:
warning: libgcc_s.so.1, needed by
/usr/local/cross/arm/usr/arm-linux-uclibc/lib/libstdc++.so, not found
(try using -rpath or -rpath-link)
and then many undefined references to _Unwind_*
We have tried using
1. -L options on the command line with the directories where are
libgcc_s.so.1 and libstdc++
2. the -static-libgcc option
3. using export LD_LIBRARY_PATH=/path/to/libs
4. using LD_RUN_PATH=/path/to/libs
None of the 4 above work.
Does anybody have any clue ?
Can we build buildroot so that it uses only static linking ?
PS: Using the -L option just works fine if we build gcc with binutils
and newlib.
It does not work with uclibc.
--
Sincerely,
-- Vania Joloboff
======================================================================
Tsinghua University, FIT Building, 3-605, Beijing 100040, China
Tel: +80 10 6279 6979 x605
email: vania.joloboff at tsinghua.edu.cn
next parent reply other threads:[~2009-04-20 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4989680E.4010807@liama.ia.ac.cn>
2009-04-20 8:29 ` Vania Joloboff [this message]
2009-02-05 2:17 [Buildroot] Bug with gmp and mpfr Vania Joloboff
2009-02-05 3:59 ` Maxim Grigoriev
2009-02-09 10:10 ` Peter Korsgaard
2009-02-09 13:03 ` Peter Korsgaard
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=49EC3273.5000100@tsinghua.edu.cn \
--to=vania.joloboff@tsinghua.edu.cn \
--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