Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] rebuilding a project on older commits
Date: Sun, 27 Jan 2013 10:11:46 +0100	[thread overview]
Message-ID: <5104EF52.3010608@googlemail.com> (raw)
In-Reply-To: <20130127093035.5537b93f@skate>

Hello Thomas,

Am 27.01.2013 09:30, schrieb Thomas Petazzoni:
> The easiest way is to use an external toolchain. This way, your
> toolchain is never rebuilt, but directly used pre-compiled.

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?

> Does Busybox has the init applet enabled? Is /sbin/init a symbolic link
> to /bin/busybox? Are the shared library loader and the C library both
> available in /lib in your root filesystem?

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?


PS: I'm on a business trip shortly so I can't answer quickly.

-- 
Regards
Carsten

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cst_hdx_2.6.34.13_defconfig
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130127/bd1eeef1/attachment-0003.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: busybox-1.20.2.config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130127/bd1eeef1/attachment-0004.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ct_ng_config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130127/bd1eeef1/attachment-0005.ksh>

  reply	other threads:[~2013-01-27  9:11 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 [this message]
2013-01-27 10:33     ` Thomas Petazzoni
2013-01-27 11:24       ` Stephan Hoffmann
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=5104EF52.3010608@googlemail.com \
    --to=c.schoenert@gmail.com \
    --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