From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] mii-diag: link statically if configured to do so
Date: Tue, 3 Jul 2012 19:56:47 +0200 [thread overview]
Message-ID: <20120703195647.078ad47c@skate> (raw)
In-Reply-To: <CA+wH294UjT4T2a7_SNziD+VLeLAvzMNZxZmbyg+hz9CW+pg=zg@mail.gmail.com>
Hello,
Le Sat, 30 Jun 2012 18:09:38 +0100,
Alex Bradbury <asb@asbradbury.org> a ?crit :
> That would be neat. Is there a list of currently tested configurations
> somewhere?
Basically, the way the autobuilds work is that Peter and I have a set
of base configurations, that define the architecture and the toolchain,
and then we do a "make randpackageconfig" to generate a random
selection of packages.
Peter has a few base configurations, and if I understand correctly, on
a given build machine, he always uses the same base configuration.
On my side, I have a single build machine, but I have 39 different base
configurations (mixing architectures, internal/external toolchains with
various configurations and versions), and I select a random one for
each build, before doing the "make randpackageconfig".
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-03 17:56 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 [this message]
2012-07-03 19:08 ` Peter Korsgaard
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=20120703195647.078ad47c@skate \
--to=thomas.petazzoni@free-electrons.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