From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-02-15
Date: Thu, 16 Feb 2017 22:15:56 +0100 [thread overview]
Message-ID: <20170216221556.59616853@free-electrons.com> (raw)
In-Reply-To: <20170216191445.GI12810@waldemar-brodkorb.de>
Hello,
On Thu, 16 Feb 2017 20:14:45 +0100, Waldemar Brodkorb wrote:
> I have a clear idea what is the problem in uClibc-ng. It is arm
> specific. But I have trouble to reproduce the czmq issue with the
> internal static arm toolchain. (simple config, not the autobuild
> config).
You can try to reproduce this build failure:
http://autobuild.buildroot.net/results/704/7041b34327b0752d3f4294a5541c785dd9989d51/
It occurs with the internal toolchain. Steps to reproduce:
mkdir foobar
cd foobar
wget http://git.buildroot.net/buildroot-test/plain/utils/br-reproduce-build
chmod +x br-reproduce-build
BASE_GIT=/path/to/local/buildroot/git/repository ./br-reproduce-build 7041b34327b0752d3f4294a5541c785dd9989d51
> Is there any difference between internal and external static
> toolchains, when both created with buildroot?
The only differences are:
1. host-mpc, host-mpfr and host-gmp are linked statically inside gcc,
so that we don't have rpath issues
2. the toolchain wrapper is tweak to support the moving of files
outside of the usr/ subdir that I'm doing as part of the toolchain
"packaging"
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-16 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170216072900.AAE4920BC6@mail.free-electrons.com>
[not found] ` <CALdGskKtWsQOyKehenpwZHyaMuYHQ600kiMr4w080DNYGRcBKQ@mail.gmail.com>
2017-02-16 9:21 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-02-15 Thomas Petazzoni
2017-02-16 10:11 ` Thomas Petazzoni
2017-02-16 19:14 ` Waldemar Brodkorb
2017-02-16 21:15 ` Thomas Petazzoni [this message]
2017-02-17 7:13 ` Waldemar Brodkorb
2017-02-17 9: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=20170216221556.59616853@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