From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/boost: bump to version 1.58.0
Date: Sat, 02 May 2015 10:15:25 -0300 [thread overview]
Message-ID: <5544CDED.5010207@zacarias.com.ar> (raw)
In-Reply-To: <20150501162931.5c466549@free-electrons.com>
On 05/01/2015 11:29 AM, Thomas Petazzoni wrote:
>> Hi.
>> It will need some extra tweaking since it failed in a similar way for sh4:
>> http://autobuild.buildroot.net/results/ccd/ccd5c83963032ba49b1627b1dff39e34a9486943/build-end.log
>
> Generally speaking, doing:
>
> if $(arch) != arm && $(arch) != mips1
>
> to decide whether to use -m32 is going to cause numerous problems. It
> should be an opt-in test rather than an opt-out test. I.e only those
> architectures that actually need -m32 should use it, rather than trying
> to exclude all architectures that do not provide -m32.
Actually on second thought they shouldn't even do that, that's compiler
setup and it's up to packaging to care care of it, via CFLAGS.
Regards.
prev parent reply other threads:[~2015-05-02 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 12:08 [Buildroot] [PATCH v2 1/1] package/boost: bump to version 1.58.0 Jörg Krause
2015-05-01 12:32 ` Gustavo Zacarias
2015-05-01 14:29 ` Thomas Petazzoni
2015-05-02 13:15 ` Gustavo Zacarias [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=5544CDED.5010207@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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