From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 1 May 2015 16:29:31 +0200 Subject: [Buildroot] [PATCH v2 1/1] package/boost: bump to version 1.58.0 In-Reply-To: <55437264.90900@zacarias.com.ar> References: <1430482091-8140-1-git-send-email-joerg.krause@embedded.rocks> <55437264.90900@zacarias.com.ar> Message-ID: <20150501162931.5c466549@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Gustavo Zacarias, On Fri, 01 May 2015 09:32:36 -0300, Gustavo Zacarias wrote: > On 05/01/2015 09:08 AM, J?rg Krause wrote: > > > Add upstream patch from [1] to fix autobuild error [2] for mips: > > mipsel-linux-g++: error: unrecognized command line option '-m32' > > > > [1] https://github.com/boostorg/build/commit/c0634341d9ee2c02d3a55c91dafb988afc066c49 > > [2] http://autobuild.buildroot.org/results/66c/66c3a868816dfe4bd4d0ffafec6988fd87a2c058/ > > > > Signed-off-by: J?rg Krause > > 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. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com