From: Jason Curl <jcurlnews@arcor.de>
To: buildroot@busybox.net
Subject: [Buildroot] uclibc toolchain get failed outside of buildroot
Date: Sat, 11 Oct 2008 16:13:12 +0200 [thread overview]
Message-ID: <48F0B478.1090508@arcor.de> (raw)
In-Reply-To: <200810111004414067835@gmail.com>
> hi,all
> I have built buildroot and got the toolchain, I copied staging_dir to
> /usr/local/arm, and compiled application successfully. But if I rename
> buildroot, the compilation got failed, it showed "arm-linux-gcc: No
> such file or directory". In fact, I have exported the search path, I
> can TAB complete the arm-linux-gcc command. That means the toolchain
> can not work out of buildroot. How to fix it?
> I have tried to add sysroot and isysroot options, but got the same result.
I had a similar issue that I've just resolved when compiling uClibc for
i586.
I changed staging dir. But when building gcc, buildroot downloads and
compiles gmp and mpfr. These in my case were not in the path so I
couldn't compile. How to put them somewhere? I did modify the
gcc-uclibc-4.x.mk files to put them based on the staging dir (you'll
also need to update binutils.mk to suit).
Then so that GCC will correctly cross compile (I used GCC 4.3.2) I had
to export LD_RUN_PATH also to where these files were.
I've attached my patch from buildroot. Let me know if this helps you. It
provides in addition the latest GMP, MPFR and also binutils 2.19.50
(unofficial release)
Regards,
Jason.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot-svn23642.patch
Url: http://busybox.net/lists/buildroot/attachments/20081011/8b11b6ea/attachment-0001.txt
next prev parent reply other threads:[~2008-10-11 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 2:04 [Buildroot] uclibc toolchain get failed outside of buildroot dishui
2008-10-11 14:13 ` Jason Curl [this message]
2008-10-13 1:47 ` dishui
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=48F0B478.1090508@arcor.de \
--to=jcurlnews@arcor.de \
--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