From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mpd: bump to version 0.18.7
Date: Tue, 28 Jan 2014 23:16:12 +0100 [thread overview]
Message-ID: <20140128231612.323eb476@skate> (raw)
In-Reply-To: <52E82ADB.8050405@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 28 Jan 2014 19:10:35 -0300, Gustavo Zacarias wrote:
> >> + depends on !(BR2_avr32 || BR2_sparc) # gcc too old
> >
> > Shouldn't we test on the GCC version here instead? There may very well
> > be modern SPARC toolchains, for example.
>
> Probably, but currently we can't check that in external toolchains.
> It was a compromise, for LEON (basically the only embedded SPARC out
> there) we're stuck with gcc <= 4.4.x and mpd requires >= 4.6.x
> The other option for running SPARC is very old Sun hardware which i
> don't think anybody really cares about these days.
> Removing the condition will leads to somewhat clear errors when building
> mpd (it does an #error check in the source).
Aah, right. Those external toolchains are really a pain, I'm wondering
who is the crazy guy insisting on having support for that in
Buildroot :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-28 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 22:17 [Buildroot] [PATCH 1/2] mpg123: bump to version 1.17.0 Gustavo Zacarias
2014-01-13 22:17 ` [Buildroot] [PATCH 2/2] mpd: bump to version 0.18.7 Gustavo Zacarias
2014-01-28 21:54 ` Thomas Petazzoni
2014-01-28 22:10 ` Gustavo Zacarias
2014-01-28 22:16 ` Thomas Petazzoni [this message]
2014-01-13 22:22 ` [Buildroot] [PATCH 1/2] mpg123: bump to version 1.17.0 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=20140128231612.323eb476@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.