From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] unbound: new package
Date: Mon, 29 Jan 2018 02:58:46 +0200 [thread overview]
Message-ID: <16896612-b4ff-96a3-e72c-e086c4bebd13@petroprogram.com> (raw)
In-Reply-To: <87wp02dk9e.fsf@dell.be.48ers.dk>
Results:
armv5-ctng-linux-gnueabi [ 1/47]: FAILED (cannot execute cross-compiler)
armv7-ctng-linux-gnueabihf [ 2/47]: FAILED (cannot execute cross-compiler)
br-arm-cortex-m4-full [ 8/47]: FAILED (need openssl 0.9.7 or higher)
br-arm-full-static [11/47]: FAILED (need openssl 0.9.7 or higher)
br-bfin-full [12/47]: FAILED (undefined pthread_spin_init,
pthread_spin_lock etc..)
br-m68k-5208-full [15/47]: FAILED (undefined pthread_spin_init,
pthread_spin_lock etc..)
br-m68k-68040-full [16/47]: FAILED (undefined pthread_spin_init,
pthread_spin_lock etc..)
br-microblazeel-full [17/47]: FAILED (undefined pthread_spin_init,
pthread_spin_lock etc..)
br-openrisc-uclibc [23/47]: FAILED (undefined pthread_spin_init,
pthread_spin_lock etc..)
i686-ctng-linux-gnu [34/47]: FAILED (cannot execute cross-compiler)
mips64el-ctng_n32-linux-gnu [37/47]: FAILED (cannot execute cross-compiler)
mips64el-ctng_n64-linux-gnu [38/47]: FAILED (cannot execute cross-compiler)
powerpc-ctng_e500v2-linux-gnuspe [39/47]: FAILED (cannot execute
cross-compiler)
sourcery-arm-armv4t [40/47]: FAILED (need 32-bit support library)
sourcery-arm [41/47]: FAILED (need 32-bit support library)
sourcery-arm-thumb2 [42/47]: FAILED (need 32-bit support library)
sourcery-mips64 [43/47]: FAILED (need 32-bit support library)
sourcery-mips [44/47]: FAILED (need 32-bit support library)
sourcery-nios2 [45/47]: FAILED (need 32-bit support library)
sourcery-x86-64 [46/47]: FAILED (need 32-bit support library)
x86_64-ctng_locales-linux-gnu [47/47]: FAILED (cannot execute
cross-compiler)
So only br-bfin-full, br-m68k-5208-full, br-m68k-68040-full,
br-microblazeel-full, br-openrisc-uclibc
I could only try to patch.
So what is the proper way of checking if external toolchain has thread
support ?
BR2_TOOLCHAIN_HAS_THREADS checks only internal toolchain right?
Best Regards
Stefan
next prev parent reply other threads:[~2018-01-29 0:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 22:26 [Buildroot] [PATCH v2 1/1] unbound: new package Stefan Fröberg
2018-01-13 23:11 ` Bernd Kuhls
2018-01-14 17:56 ` Stefan Fröberg
2018-01-14 18:42 ` Bernd Kuhls
2018-01-16 21:28 ` Stefan Fröberg
2018-01-16 21:48 ` Bernd Kuhls
2018-01-16 21:52 ` Stefan Fröberg
2018-01-28 16:24 ` Peter Korsgaard
2018-01-28 23:43 ` Stefan Fröberg
2018-01-29 7:58 ` Peter Korsgaard
2018-01-29 0:58 ` Stefan Fröberg [this message]
2018-01-29 7:58 ` Peter Korsgaard
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=16896612-b4ff-96a3-e72c-e086c4bebd13@petroprogram.com \
--to=stefan.froberg@petroprogram.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.