From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autobuild-run: Do not build civetweb with a known non-working external MIPS toolchain
Date: Mon, 8 Dec 2014 15:26:43 +0000 [thread overview]
Message-ID: <5485C333.6020405@imgtec.com> (raw)
In-Reply-To: <5485A753.6090905@imgtec.com>
Dear Thomas Petazzoni,
On 12/08/2014 01:27 PM, Vicente Olivert Riera wrote:
> On 12/08/2014 12:46 PM, Thomas Petazzoni wrote:
>> Dear Vicente Olivert Riera,
>>
>> On Mon, 8 Dec 2014 12:34:55 +0000, Vicente Olivert Riera wrote:
>>
>>> + # This MIPS uClibc toolchain fails to build the civetweb package
>>> + if 'BR2_PACKAGE_CIVETWEB=y\n' in configlines and \
>>> + 'BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-mipsel-o32-full-2014.08.tar.bz2"\n' in configlines:
>>> + return False
>>
>> I have just updated the BR toolchains used by the autobuilders, so the
>> version is now 2014.11 and not 2014.08.
>>
>> Maybe some other exceptions in the autobuild-run script need to be
>> updated as well.
>
> Ok, I will check all the MIPS exceptions with the new toolchains to
> check if they are still needed. Thanks.
>
> Cheers,
>
I have successfully built conntrack-tools, rt-test and civetweb packages
using the new br-mipsel-o32-full-2014.11 toolchain. I will send a patch
to remove those exceptions from the autobuild-run script.
Cheers,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
prev parent reply other threads:[~2014-12-08 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 12:34 [Buildroot] [PATCH] autobuild-run: Do not build civetweb with a known non-working external MIPS toolchain Vicente Olivert Riera
2014-12-08 12:46 ` Thomas Petazzoni
2014-12-08 13:27 ` Vicente Olivert Riera
2014-12-08 15:26 ` Vicente Olivert Riera [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=5485C333.6020405@imgtec.com \
--to=vincent.riera@imgtec.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.