From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x
Date: Tue, 29 May 2018 23:32:19 +0200 [thread overview]
Message-ID: <20180529233219.0eca0f54@windsurf.home> (raw)
In-Reply-To: <1527595765-23055-1-git-send-email-christophe.priouzeau@st.com>
Hello Christophe,
On Tue, 29 May 2018 12:09:27 +0000, Christophe PRIOUZEAU wrote:
> Due to runtime issue with the usage of BINUTILS 2.29.x,
> we need to use the version 2.28.x
>
> Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com>
I know those patches have been committed, but I'd like to say I'm not
totally happy with them: to me, they don't implement the right approach.
Your patches only fix specifically the STM32 defconfigs. Any other
Buildroot user doing Cortex-M4 stuff, for other platforms, will fall
into the same binutils issue.
So in fact the proposal that was made back in April at
http://lists.busybox.net/pipermail/buildroot/2018-April/219223.html was
in the end better.
I still don't like the fact that we are forced to use an old binutils
version, because we are ultimately going to drop support for binutils
2.28 in the future, and if the issue isn't fixed in newer binutils
versions, we are going to have a problem. But regardless of that,
fixing the defconfigs is really not the correct solution here I believe.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-29 21:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 12:09 [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x Christophe PRIOUZEAU
2018-05-29 12:09 ` [Buildroot] [PATCH 2/2] configs/stm32f469: " Christophe PRIOUZEAU
2018-05-29 12:49 ` Romain Naour
2018-05-29 12:39 ` [Buildroot] [PATCH 1/2] configs/stm32f429: " Romain Naour
2018-05-29 12:47 ` Christophe PRIOUZEAU
2018-05-29 12:48 ` Romain Naour
2018-05-29 15:51 ` Peter Korsgaard
2018-05-29 21:32 ` Thomas Petazzoni [this message]
2018-05-30 12:12 ` Laurent GONZALEZ
2018-05-30 16:24 ` Yann E. MORIN
2018-05-30 15:24 ` Christophe PRIOUZEAU
2018-05-30 15:42 ` Thomas Petazzoni
2018-05-30 20:35 ` Arnout Vandecappelle
2018-05-30 20:41 ` Thomas Petazzoni
2018-05-30 20:46 ` Romain Naour
2018-05-31 8:34 ` Christophe PRIOUZEAU
2018-05-31 9:13 ` Arnout Vandecappelle
2018-05-31 9:16 ` 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=20180529233219.0eca0f54@windsurf.home \
--to=thomas.petazzoni@bootlin.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