Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] rebuilding a project on older commits
Date: Sun, 27 Jan 2013 12:24:37 +0100	[thread overview]
Message-ID: <51050E75.7020304@relinux.de> (raw)
In-Reply-To: <20130127113309.4623b949@skate>

Am 27.01.2013 11:33, schrieb Thomas Petazzoni:
> Dear Carsten Schoenert,
>
> On Sun, 27 Jan 2013 10:11:46 +0100, Carsten Schoenert wrote:
>
>> Yes, this is the solution. Right now I build the toolchain with ct-ng
>> inside buildroot.
>> Is it possible to move this existing toolchain outside buildroot or
>> should I rebuild from scratch?
> You should build it once with Crosstool-NG outside of Buildroot,
> install it somewhere, and tell Buildroot to use it as an external
> toolchain.
>
>> 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?
> That sounds really odd. Maybe we have a bug in the ct-ng backend, and
> it doesn't copy the libraries? I would have to do a test build, but I'm
> on the battery in the train for now, so I can't do heavy builds for now.
>
> If someone could do a quick test build of a minimal system that uses
> the ct-ng backend, and verify that $(O)/target/lib contains the right
> libraries, that would be nice.
I just tried (took beaglebone-defconfig and only changed toolchain to
ct-ng) and output/target/lib/ seems o.k.
> $ ls output/target/lib/
> ld-uClibc-0.9.33.2.so  libcrypt.so.0      libdl.so.0       
> libm.so.0           libpthread-0.9.33.2.so  libresolv.so.0    
> libuClibc-0.9.33.2.so
> ld-uClibc.so.0         libc.so.0          libgcc_s.so.1    
> libnsl-0.9.33.2.so  libpthread.so.0         librt-0.9.33.2.so 
> libutil-0.9.33.2.so
> libcrypt-0.9.33.2.so   libdl-0.9.33.2.so  libm-0.9.33.2.so 
> libnsl.so.0         libresolv-0.9.33.2.so   librt.so.0        
> libutil.so.0
Kind regards

Stephan
>
> Best regards,
>
> Thomas


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

  reply	other threads:[~2013-01-27 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 17:57 [Buildroot] rebuilding a project on older commits Carsten Schoenert
2013-01-27  8:30 ` Thomas Petazzoni
2013-01-27  9:11   ` Carsten Schoenert
2013-01-27 10:33     ` Thomas Petazzoni
2013-01-27 11:24       ` Stephan Hoffmann [this message]
2013-01-27 11:36       ` 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=51050E75.7020304@relinux.de \
    --to=sho@relinux.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