[Buildroot] uclibc toolchain get failed outside of buildroot

[Buildroot] uclibc toolchain get failed outside of buildroot

[dishui]

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.

Best Regards,

kaimi

2008-10-11 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20081011/8144a783/attachment.htm 

[Buildroot] uclibc toolchain get failed outside of buildroot

[Jason Curl]

> 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 

[Buildroot] uclibc toolchain get failed outside of buildroot

[dishui]

I've resolved the problem, I did make uclibc-menuconfig before compilation, I don't know exactly which option works. 


2008-10-13 






> 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 HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20081013/88f1ad21/attachment.htm