Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder update
Date: Fri, 11 Mar 2016 09:42:23 +0100	[thread overview]
Message-ID: <20160311094223.6b433df0@free-electrons.com> (raw)
In-Reply-To: <E1aeFbm-0004jE-Q7@fli4l.lan.fli4l>

Hello,

On Fri, 11 Mar 2016 06:27:30 +0100, Bernd Kuhls wrote:

> do we have a config for a buildroot x86 toolchain which lacks
> BR2_X86_CPU_HAS_MMX? An empty defconfig file would be enough imho, the one
> you get when you call "make menuconfig" in a fresh git checkout without
> selecting anything and save this config, like: 
> 
> bernd at buildroot:~/buildroot/buildroot$ make menuconfig
> (select nothing, just save the config)
> bernd at buildroot:~/buildroot/buildroot$ make savedefconfig
> BR2_DEFCONFIG=test cat test
> bernd at buildroot:~/buildroot/buildroot$ cat test
> bernd at buildroot:~/buildroot/buildroot$ 
> 
> I think such a config would be useful because lots of media packages
> contain mmx specific code. 

By default we use i586, right? So what you suggest is an i586 defconfig?

Now we have two options:

 - Use an internal toolchain configuration, which means that the
   toolchain is rebuilt everytime, and when we want on our side to
   reproduce the build failures, we also have to rebuild the toolchain.

 - Use a pre-built external toolchain.

I'm leaning twoards the second option. What do you think?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2016-03-11  8:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 22:47 [Buildroot] Autobuilder update Thomas Petazzoni
2016-03-11  5:27 ` Bernd Kuhls
     [not found] ` <E1aeFbm-0004jE-Q7@fli4l.lan.fli4l>
2016-03-11  8:42   ` Thomas Petazzoni [this message]
2016-03-11 10:57     ` Peter Korsgaard
2016-03-11 13:38       ` Thomas Petazzoni
2016-03-11 14:20         ` Peter Korsgaard
2016-03-11 11:08 ` Peter Korsgaard
2016-03-11 13:37   ` Thomas Petazzoni
2016-03-11 14:21     ` Peter Korsgaard
2016-03-12 22:58 ` Yann E. MORIN
2016-03-13 12:08   ` 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=20160311094223.6b433df0@free-electrons.com \
    --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