[Buildroot] rebuilding a project on older commits
jacmet at uclibc.org
Sun Jan 27 11:36:58 UTC 2013
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com> writes:
>> Is it possible to move this existing toolchain outside buildroot or
>> should I rebuild from scratch?
Thomas> You should build it once with Crosstool-NG outside of Buildroot,
Thomas> install it somewhere, and tell Buildroot to use it as an external
Building it inside Buildroot should also work (E.G. just set
BR2_HOST_DIR to some/place/elsewhere and use that directory as your
external toolchain dir).
>> For the first two points I can answer with yes, but your tip with the
>> /lib folder is the right one. This folder is empty, and this also in
>> the output/target directory so it must be empty in the rootfs.tar too.
>> So the libraries in the /lib folder are missing there must be
>> something wrong with the config of the ct-ng? Any suggestions where I
>> have to look to?
Thomas> That sounds really odd. Maybe we have a bug in the ct-ng
Thomas> backend, and it doesn't copy the libraries? I would have to do
Thomas> a test build, but I'm on the battery in the train for now, so I
Thomas> can't do heavy builds for now.
It sounds like this:
Author: Floris Bos <bos at je-eigen-domein.nl>
Date: Sat Jan 5 19:11:45 2013 +0000
Fix installation of crosstool-ng libraries to target
When using the crosstool-ng toolchain option, the libc libraries were not
installed to target. Buildroot calls the show-tuple function to determine
the directory to copy from, and it seems that outputs the result to stderr
instead of stdout
Signed-off-by: Floris Bos <bos at je-eigen-domein.nl>
Acked-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
Signed-off-by: Peter Korsgaard <jacmet at sunsite.dk>
I don't quite recall when the problem was introduced, but if it's
present in 2012.11, this would certainly be a candidate for 2012.11.2.
Bye, Peter Korsgaard
More information about the buildroot