From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-09-13
Date: Sat, 14 Sep 2013 17:34:12 +0200 [thread overview]
Message-ID: <523481F4.7000304@googlemail.com> (raw)
In-Reply-To: <20130914170316.52a4eec6@skate>
Hello Thomas,
On 14.09.2013 17:03, Thomas Petazzoni wrote:
> Maybe I should be providing a script that downloads the complete
> chroot, and reproduce the build failure within the chroot, so that
> people can get the exact same behavior as the one in the autobuilder
> machine.
In Debian we use sbuild (Perl), cowbuilder (ELF executable) / pbuilder
(shell) to set up a clean basic chroot and after that clone this base
chroot and build the *.deb packages inside. The core chroot is setted up
by calling debootstrap for the target platform.
Maybe you want to look at it and can grap something?
I just use the tools, Perl isn't my favorite language and pbuilder just
works as expected, so don't ask me anything special. *g*
I personally use pbuilder, it's just a shell script with soem external
calls, there should be something suitable I think.
[1] http://packages.debian.org/wheezy/sbuild
[2] http://packages.debian.org/wheezy/cowbuilder
http://packages.debian.org/wheezy/pbuilder
Regards
Carsten
next prev parent reply other threads:[~2013-09-14 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-09-13 Thomas Petazzoni
2013-09-14 12:36 ` Michael Rommel
2013-09-14 13:19 ` Stephan Hoffmann
2013-09-14 15:03 ` Thomas Petazzoni
2013-09-14 15:16 ` Michael Rommel
2013-09-14 15:34 ` Carsten Schoenert [this message]
2013-09-14 17:00 ` Thomas Petazzoni
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=523481F4.7000304@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.