Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] mii-diag: link statically if configured to do so
Date: Tue, 03 Jul 2012 21:08:35 +0200	[thread overview]
Message-ID: <87ipe41x3g.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120703195647.078ad47c@skate> (Thomas Petazzoni's message of "Tue, 3 Jul 2012 19:56:47 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Hello,
 Thomas> Le Sat, 30 Jun 2012 18:09:38 +0100,
 Thomas> Alex Bradbury <asb@asbradbury.org> a ?crit :

 >> That would be neat. Is there a list of currently tested configurations
 >> somewhere?

 Thomas> Basically, the way the autobuilds work is that Peter and I have a set
 Thomas> of base configurations, that define the architecture and the toolchain,
 Thomas> and then we do a "make randpackageconfig" to generate a random
 Thomas> selection of packages.

 Thomas> Peter has a few base configurations, and if I understand correctly, on
 Thomas> a given build machine, he always uses the same base configuration.

Indeed. I have a defconfig defining the toolchain configuration and my
script basically does:

cp defconfig .config
yes '' | make oldconfig
make randpackageconfig
make

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-07-03 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 20:03 [Buildroot] [git commit] mii-diag: link statically if configured to do so Peter Korsgaard
2012-06-29 10:16 ` Thomas Petazzoni
2012-06-29 11:23   ` Jonas Keidel
2012-06-30  8:32   ` Peter Korsgaard
2012-06-30  8:55     ` Thomas Petazzoni
2012-06-30 13:02       ` Arnout Vandecappelle
2012-06-30 17:09         ` Alex Bradbury
2012-07-03 17:56           ` Thomas Petazzoni
2012-07-03 19:08             ` Peter Korsgaard [this message]
2012-06-30 22:01         ` Peter Korsgaard
2012-07-01 19:32         ` 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=87ipe41x3g.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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