From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gpsd: add work-around and re-enable for microblaze
Date: Sun, 22 Nov 2015 13:57:32 +0100 [thread overview]
Message-ID: <20151122135732.3fc6bb45@free-electrons.com> (raw)
In-Reply-To: <1448195040-8082-1-git-send-email-sergio.prado@e-labworks.com>
Dear Sergio Prado,
On Sun, 22 Nov 2015 10:24:00 -0200, Sergio Prado wrote:
> Fix (works around) bug #6872
> https://bugs.busybox.net/show_bug.cgi?id=6872
>
> The gpsd package was disabled due to an internal compiler error for
> the microblaze architecture in the following commit:
> http://git.buildroot.net/buildroot/commit/?id=d517415bcda380336f4a27bf248cef4d81791c9e
>
> The problem is due to an specific GCC optimization flag
> (-fexpensive-optimizations), so disabling it we can work around this
> problem and compile gpsd for the microblaze architecture.
>
> Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Changes v1 -> v2:
> - added a comment explaining why we are disabling the optimization flag.
> ---
> package/gpsd/Config.in | 3 ---
> package/gpsd/gpsd.mk | 8 +++++++-
> package/sconeserver/Config.in | 2 --
> 3 files changed, 7 insertions(+), 6 deletions(-)
Applied to master, thanks. Could you test with gcc 5.x, and if the
problem still exists, report a bug to the gcc bug tracker ? While your
workaround is OK, it is not good for gcc to fail this way when building
gpsd.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-22 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 12:24 [Buildroot] [PATCH v2] gpsd: add work-around and re-enable for microblaze Sergio Prado
2015-11-22 12:57 ` Thomas Petazzoni [this message]
2015-11-22 15:27 ` Sergio Prado
2015-11-22 15: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=20151122135732.3fc6bb45@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