From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gcc-4.7.3 potential issue with barebox
Date: Tue, 18 Jun 2013 19:05:30 +0200 [thread overview]
Message-ID: <20130618190530.37e44241@skate> (raw)
In-Reply-To: <51C076A3.4040008@calao-systems.com>
Dear Gr?gory Hermant,
On Tue, 18 Jun 2013 17:02:59 +0200, Gr?gory Hermant wrote:
> Same issue with gcc version 4.7.3 (Sourcery CodeBench Lite 2013.05-24) toolchain.
Then maybe it's a Barebox vs. gcc 4.7.x issue that should be reported
to the Barebox people? I'm pretty sure they have already built and
tested Barebox with gcc 4.7, but maybe there are some remaining
problems in specific areas?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-18 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 12:57 [Buildroot] gcc-4.7.3 potential issue with barebox Grégory Hermant
2013-06-17 14:25 ` Thomas Petazzoni
2013-06-18 15:02 ` Grégory Hermant
2013-06-18 17:05 ` Thomas Petazzoni [this message]
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=20130618190530.37e44241@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