From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-19
Date: Thu, 20 Nov 2014 11:27:30 +0100 [thread overview]
Message-ID: <20141120112730.156f9ee6@free-electrons.com> (raw)
In-Reply-To: <87y4r6fc2v.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Thu, 20 Nov 2014 10:36:24 +0100, Peter Korsgaard wrote:
> > The uClibc bug about setreuid().
>
> > What do we do about this one? It still isn't fixed upstream. Should we
> > simply disable uClibc for static builds? (But then we would only have
> > musl left as a C library compatible with static builds). Or do we
> > simply blacklist for now the packages that are known to use the symbols
> > causing problems?
>
> > Peter?
>
> uClibc with static linking is useful for quite some setups, so I would
> find it a pity to globally disable it. Let's just disable the affected
> packages with a comment.
So you suggest to disable them within Buildroot, or through an
exception in the autobuild-run script?
Advantage of doing it in the autobuild-run script: we don't need to
propagate to all the reverse dependencies. The script will exclude any
configuration that has the problematic package selected with a uClibc
toolchain.
Drawback of doing it in the autobuild-run script: normal users of
Buildroot may run into the issue.
> I did that yesterday:
>
> http://git.buildroot.net/buildroot/commit/?id=d81d202e97258e440d1fc271ba5cdb7c01f7257f
Yep, Baruch pointed me to this commit, which I had missed.
> >> sh4a | qt-4.8.6 | NOK | http://autobuild.buildroot.net/results/119adf6a31266e71e45fb1951d7e8ebbd1ff41fe/
>
> > Bug in the CodeSourcery SH4 toolchain. I don't think we have any other
> > solution than blacklisting configurations that contain Qt4 Webkit and
> > that use this toolchain. Opinions?
>
> Yes, I also think we should just blacklist it.
I'll add an exception to the autobuilder then.
> >> bfin | thrift-0.9.1 | NOK | http://autobuild.buildroot.net/results/cf2723cf650486586ff18b6ef57c91a74a97bbc9/
>
> > bfin-linux-uclibc-g++:
> > /home/chroot/media/code/buildroot/autobuilder/instance-1/output/host/usr/bfin-buildroot-linux-uclibc/sysroot/opt/uClinux/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.3.5/libstdc++.so:
> > No such file or directory
>
> > Don't know what's going on. Someone to have a look?
>
> I also looked at the log, and it doesn't make sense to me. I haven't
> investigated further though.
Ok.
> All in all, it looks pretty good!
Yes, it starts to look good.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-20 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-19 Thomas Petazzoni
2014-11-20 8:42 ` Baruch Siach
2014-11-20 9:38 ` Peter Korsgaard
2014-11-20 8:44 ` Thomas Petazzoni
2014-11-20 9:09 ` Baruch Siach
2014-11-20 9:16 ` Thomas Petazzoni
2014-11-20 9:36 ` Peter Korsgaard
2014-11-20 10:27 ` Thomas Petazzoni [this message]
2014-11-20 10:48 ` Peter Korsgaard
2014-11-20 18:37 ` Bernd Kuhls
2014-11-20 21:41 ` Peter Korsgaard
2014-11-20 19:58 ` Alexey Brodkin
2014-11-21 8:20 ` Thomas Petazzoni
2014-11-20 20:07 ` Bernd Kuhls
2014-11-21 18:43 ` Bernd Kuhls
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=20141120112730.156f9ee6@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 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.