From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results
Date: Sun, 16 Nov 2014 11:07:14 +0100 [thread overview]
Message-ID: <20141116100714.GB3965@free.fr> (raw)
In-Reply-To: <20141111234919.3178e9d3@free-electrons.com>
Thomas, All,
On 2014-11-11 23:49 +0100, Thomas Petazzoni spake thusly:
> > i486 | alsa-lib-1.0.28 | NOK | http://autobuild.buildroot.net/results/6ce1ecdf2bf1f14f1497e9960a1b6689568a3658/
> > powerpc | alsa-lib-1.0.28 | NOK | http://autobuild.buildroot.net/results/a990b0deb0269e91bcd7fb008eb40a2e00350114/
>
> This is the same problem twice: uClibc behaving badly when vfork() is
> used in static linking configurations. This is now fixed for the
> internal toolchain backend. The first build failure is with an external
> Crosstool-NG toolchain using uClibc. Yann, what would be your
> recommendation here? Is it something you intend to fix upstream in
> Crosstool-NG? Or should I add an exception for this toolchain to not be
> used in static linking configurations?
Is that fixed in Buildroot with that patch patch:
package/uclibc/0.9.33.2/0062-nptl-remove-duplicate-vfork-in-libpthread.patch
It is not in upstream uClibc yet, so I've pinged them about applying
that patch.
I'm a bit warry of carrying patches in crosstool-NG, that are not
upstream. But uClibc is, well, a special case, isn't it? ;-)
Maybe I could just vampirise the patches from Buildroot, and be done
with it.
> > i686 | qemu-2.1.2 | NOK | http://autobuild.buildroot.net/results/9efc2b14a28fd21ed2ce492f41de538673d13dce/
> > i686 | qemu-2.1.2 | NOK | http://autobuild.buildroot.net/results/0f640d6b701bb854ada2023861a234dfe489f038/
> > x86_64 | qemu-2.1.2 | NOK | http://autobuild.buildroot.net/results/c58f7e10a416e0eaf7e49f0bb5ce9e6f85bc1559/
> > x86_64 | qemu-2.1.2 | NOK | http://autobuild.buildroot.net/results/5979559734620358a92186a6e67aea46b6034b44/
>
> ERROR: fdt disabled but some requested targets require it.
> You can turn off fdt only if you also disable all the system emulation
> targets which need it (by specifying a cut down --target-list).
O...K... Well, fdt support comes later in my series, and it is a part
that is not yet applied.
I'll see to re-order the series to be able to just submit the FDT part,
before the release.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-11-16 10:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-10 Thomas Petazzoni
2014-11-11 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-11-11 23:41 ` Gustavo Zacarias
2014-11-12 2:30 ` Nathaniel Roach
2014-11-12 14:09 ` Jörg Krause
2014-11-16 10:07 ` Yann E. MORIN [this message]
2014-11-22 11:10 ` Bernd Kuhls
-- strict thread matches above, loose matches on Subject: below --
2020-02-27 9:31 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-26 Thomas Petazzoni
2020-02-27 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2020-02-27 23:06 ` Max Filippov
2020-02-27 23:18 ` Giulio Benetti
2020-02-28 8:03 ` Thomas Petazzoni
2020-02-28 18:06 ` Giulio Benetti
2020-02-28 6:21 ` Heiko Thiery
2020-02-28 7:56 ` Sergio Prado
2020-02-28 8:01 ` Thomas Petazzoni
2020-02-28 7:32 ` Romain Naour
2020-02-28 15:02 ` Peter Seiderer
2020-02-29 21:15 ` Romain Naour
2020-02-29 23:17 ` Peter Seiderer
2020-02-19 7:48 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-18 Thomas Petazzoni
[not found] ` <20200220034343.2370e4e4@windsurf>
2020-02-20 13:36 ` [Buildroot] Analysis of build results Giulio Benetti
2020-02-21 8:23 ` Romain Naour
[not found] ` <94c8edad-773d-2b36-5daf-b6ee60dd747f@micronovasrl.com>
[not found] ` <3e7b016b-eca6-b768-3fca-8fd7e44d0299@micronovasrl.com>
[not found] ` <20200220190807.505b4fb2@windsurf>
[not found] ` <00751b5d-ca05-fe42-0e9b-6a1005a09e6d@micronovasrl.com>
[not found] ` <20200220192344.03785f04@windsurf>
[not found] ` <bcc10a0e-c54e-5b75-9b77-8922b85a925a@micronovasrl.com>
[not found] ` <fe7d07df-71a0-e317-6b91-ade479545ec4@smile.fr>
[not found] ` <28258465-4f79-3f47-189d-bb066b0aa9f7@micronovasrl.com>
2020-02-22 19:10 ` Romain Naour
2020-02-22 19:44 ` Giulio Benetti
2020-02-22 21:11 ` Fabrice Fontaine
2020-02-22 21:48 ` Giulio Benetti
2020-02-22 22:00 ` Fabrice Fontaine
2020-02-22 23:48 ` Romain Naour
2014-08-30 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-29 Thomas Petazzoni
2014-08-30 9:07 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-08-25 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-24 Thomas Petazzoni
2014-08-25 16:16 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-08-25 16:26 ` Phil Eichinger
2014-08-25 17:47 ` Thomas Petazzoni
2014-08-25 21:07 ` Peter Korsgaard
2014-08-25 21:13 ` Jörg Krause
2014-08-26 6:17 ` Alexander Lukichev
2014-08-28 12:52 ` Ezequiel Garcia
2014-08-31 16:58 ` Frank Bergmann
2014-08-31 21:13 ` Ezequiel Garcia
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=20141116100714.GB3965@free.fr \
--to=yann.morin.1998@free.fr \
--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