From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] toolchain/external: fix wrapper by not passing conflicting flags
Date: Wed, 8 Jan 2014 19:01:41 +0100 [thread overview]
Message-ID: <20140108180141.GA3430@free.fr> (raw)
In-Reply-To: <CAGduivw60X1M=cG9xx_ZJqVOgnKB5C7DpfduEwLJD+j0r46sSA@mail.gmail.com>
Maxime, All,
On 2014-01-08 16:57 +0100, Maxime Hadjinlian spake thusly:
> On Wed, Jan 8, 2014 at 4:51 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Dear Maxime Hadjinlian,
> Hi Thomas,
> >
> > On Wed, 8 Jan 2014 13:45:59 +0100, Maxime Hadjinlian wrote:
> >
> >> Shouldn't we change the different defconfig that exists ? At least the
> >> RaspberryPi so it would sets an example (and maybe add something about
> >> this in the manual ?)
> >
> > Why would the defconfig need some changes following this patch?
> To set a visible example of settings the correct -march/mcpu/mtune options ?
> Also, this would eliminate all the warnings that Yann saw while
> building a kernel for the rpi, so it seems like a good candidate.
There is nothing in that patch that impacts the configuration.
There is no reason to change any defconfig to 'activate' this change.
Rather, the config options BR2_GCC_TARGET_CPU, BR2_GCC_TARGET_ARCH, and
BR2_GCC_TARGET_MTUNE, if any, are pased at the time we build the wrapper
itself.
Those options are set automatically when you choose, in the menuconfig,
the type of CPU your target has. And since that will automatically set
the BR2_GCC_TARGET_{ARCH,CPU,MTUNE} options, they are forcibly set.
And since the raspberrypi_defconfig (as you use that as an example)
already sets BR2_arm1176jzf_s=y, this will set BR2_GCC_TARGET_ARCH and
BR2_GCC_TARGET_CPU.
And this is exactly this situation this patch fixes: our options forcing
the compiler flags, when some are already provided on the command line.
So, there is no need (and no reason) to change any of our defconfigs to
take advantage of this change.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-01-08 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 22:46 [Buildroot] [PATCH 0/5] Misc accumulated changes Yann E. MORIN
2014-01-07 22:46 ` [Buildroot] [PATCH 1/5] Makefile: support running graph-depends from out-of-tree Yann E. MORIN
2014-01-09 20:28 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 2/5] toolchain/external: fix wrapper by not passing conflicting flags Yann E. MORIN
2014-01-08 12:45 ` Maxime Hadjinlian
2014-01-08 15:51 ` Thomas Petazzoni
2014-01-08 15:57 ` Maxime Hadjinlian
2014-01-08 18:01 ` Yann E. MORIN [this message]
2014-01-08 18:46 ` Maxime Hadjinlian
2014-01-09 20:28 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 3/5] package/tzdata: install a default localtime Yann E. MORIN
2014-01-09 17:13 ` Arnout Vandecappelle
2014-01-09 22:57 ` Yann E. MORIN
2014-01-09 20:29 ` Peter Korsgaard
2014-01-28 21:13 ` Thomas Petazzoni
2014-01-07 22:46 ` [Buildroot] [PATCH 4/5] system: default to empty issue/hostname for custom skeleton Yann E. MORIN
2014-01-09 20:32 ` Peter Korsgaard
2014-01-09 20:44 ` Yann E. MORIN
2014-01-10 8:52 ` Sagaert Johan
2014-01-10 14:35 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 5/5] manual: add section about dealing efficiently with big image files Yann E. MORIN
2014-01-09 20:29 ` 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=20140108180141.GA3430@free.fr \
--to=yann.morin.1998@free.fr \
--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