From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-07-29
Date: Sun, 31 Jul 2016 22:49:58 +0200 [thread overview]
Message-ID: <bcb2bb49-c33c-2d84-0de6-57e3713be8f3@gmail.com> (raw)
In-Reply-To: <e7d1f683-c220-4609-26a4-464fffb11798@gmail.com>
Le 31/07/2016 ? 22:06, Romain Naour a ?crit :
> Hi Thomas, All,
>
> Le 30/07/2016 ? 23:23, Thomas Petazzoni a ?crit :
>> Hello,
>>
>> We've got lots of failures, so your need is definitely needed to fix
>> some of them. Waldemar, Maxime (Hadjinlian and Ripard), Olivier
>> (Schonken and Singla), Gustavo, Romain, Alexey, Vlad, Yann, Frank,
>> Angelo, Fabrice, Bernd, Julien, Dagg, Vicente, Baruch, Peter, please
>> look below, there are lots of things for you! :-)
>>
>> Thanks for your participation!
>>
>
>>
>>> microblazeel | bluez_utils-4.101 | NOK | http://autobuild.buildroot.net/results/871c93da958e5014a9f77212bec89047d4ada6f3/
>>> microblazeel | bluez_utils-4.101 | NOK | http://autobuild.buildroot.net/results/06998c35e0aae47f03f82b150c6824e06e768550/
>>> microblazeel | bluez_utils-4.101 | NOK | http://autobuild.buildroot.net/results/d8987371bef51567afbd60674b9aa36bb1399481/
>>
>> BFD (GNU Binutils) 2.25.1 assertion fail elf32-microblaze.c:1491
>>
>> Romain, would you have the time to see if binutils 2.26 still has the
>> issue, and see what is the proper approach (exclude bluez_utils from
>> Microblaze, backport a patch, etc.) ?
>>
>
> Same issue with Binutils 2.26.
>
> I think this may be a uClibc-ng issue :
> Scrt1.o: probably compiled without -fPIC? (Waldemar?)
I added --disable-pie to BLUEZ_UTILS_CONF_OPTS and bluez_utils build fine with
this toolchain. So it seems that PIE is not supported on microblaze.
Also I backported binutils upstream patch
47993b4af18c6ef1cad300f6393bf896d3cb5e5c but I'm not sure it's required to fix
this issue.
>
>>
>>> microblazeel | cifs-utils-6.5 | NOK | http://autobuild.buildroot.net/results/a5848753eb0e2b0ddf55e226c45b85fd3a1c84f3/
>>
>> Romain, same issue as bluez_utils. Try with binutils 2.26 ?
>
> [snip]
>
>>
>>> microblazeel | iproute2-4.5.0 | NOK | http://autobuild.buildroot.net/results/118c92055daca52d9b10d764835c0d0c0b24fdc2/
>>
>> cannot find -lpthread
>>
>> Not sure what happens here :-/
>>
> The microblaze internal toolchain is build without thread support
> (BR2_PTHREADS_NONE=y), also there is the same issue on arm [1]
>
> I'm not sure about the required thread support (w/ NPTL ?)
iproute2 build fine without NPTL support, tested with
http://autobuild.buildroot.net/toolchains/configs/br-m68k-68040-full.config
I'll send a patch.
Best regards,
Romain
>
> [1] http://autobuild.buildroot.net/?reason=iproute2-4.5.0
>
> Best regards,
> Romain
>
>
>>
>>> microblazeel | lvm2-2.02.161 | NOK | http://autobuild.buildroot.net/results/2897a2fa72b98736333fe0c2fa9da802ba982e32/
>>> microblazeel | lvm2-2.02.161 | NOK | http://autobuild.buildroot.net/results/e260a992d4ca29a55e356b81d81d44bdafb7fe14/
>>
>> Yet another:
>>
>> BFD (GNU Binutils) 2.25.1 assertion fail elf32-microblaze.c:1491
>>
>> Romain ?
>>
> [snip]
>>
>> Thanks a lot!
>>
>> Thomas
>>
>
next prev parent reply other threads:[~2016-07-31 20:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-07-29 Thomas Petazzoni
2016-07-30 21:23 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-07-31 7:44 ` Peter Korsgaard
2016-07-31 8:48 ` Waldemar Brodkorb
2016-07-31 12:44 ` Bernd Kuhls
2016-08-04 8:12 ` Khem Raj
2016-07-31 18:56 ` Baruch Siach
2016-07-31 20:56 ` Thomas Petazzoni
2016-07-31 20:06 ` Romain Naour
2016-07-31 20:49 ` Romain Naour [this message]
2016-07-31 21:42 ` Waldemar Brodkorb
2016-07-31 21:25 ` Yann E. MORIN
2016-08-01 15:43 ` Vlad Zakharov
[not found] ` <CACcFhEWvcokFB0WFsVpv6PaB-5QBnDNvhgSPFGmk43=zq8D6=A@mail.gmail.com>
2016-08-02 7:19 ` Thomas Petazzoni
2016-08-03 8:27 ` Olivier Schonken
2016-08-03 20:10 ` Angelo Compagnucci
2016-08-03 20:23 ` Yann E. MORIN
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=bcb2bb49-c33c-2d84-0de6-57e3713be8f3@gmail.com \
--to=romain.naour@gmail.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