From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of autobuild failures 18-19/11
Date: Tue, 22 Nov 2016 09:26:56 +0100 [thread overview]
Message-ID: <20161122092656.39ae5aa4@free-electrons.com> (raw)
In-Reply-To: <bfc05511-fb21-e223-ced5-6108cd702fea@mind.be>
Hello,
On Tue, 22 Nov 2016 00:38:07 +0100, Arnout Vandecappelle wrote:
> > Hum, I think I had a look, and I was able to reproduce IIRC. I really
> > need to be better at taking notes about what I'm doing. I even think I
> > had found what the issue was.
>
> I wasn't able to reproduce on my laptop (but I didn't do the whole build, just
> kvmtool).
I don't remember, I'll try to restart a full build. It might have been
an issue with the host gcc version, or something like that.
> >> http://autobuild.buildroot.net/results/4fb4353bce614b64b30b05d06831e0d0f38a48dd
> >> bfin / bf532 libarchive-3.2.1 uclibc static
> >>
> >>> ./.libs/libarchive.a(archive_random.o): In function `_archive_random':
> >>> libarchive/archive_random.c:(.text+0x158): undefined reference to `_pthread_mutex_lock'
> >>> libarchive/archive_random.c:(.text+0x20a): undefined reference to `_pthread_mutex_unlock'
> >>
> >> pthread static linking problem with the ADI toolchain. Probably solved with
> >> current uClibc-ng.
> >
> > Let's kill this toolchain. I checked the other day the ADI toolchain
> > SourceForge site, and they don't have any newer version.
>
> OK. But let's do it after the 2016.11 release, OK?
Yes, agreed. Or I could already drop them from the autobuilder testing,
and we wait after 2016.11 to actually remove them from Buildroot.
> Perhaps if/when I (or someone else) do a respin of the external toolchain series?
Does it need a respin?
> >> http://autobuild.buildroot.net/results/0be5e6b6194df5261b5ee569100f9eb2c899b695
> >> powerpc / e500mc lite-0.8.10 uclibc static
> >>
> >>> /bin/sh ../libtool --tag=CC --mode=link /home/buildroot/build/instance-0/output/host/usr/bin/powerpc-linux-gcc -Wall -O3 -pipe -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -static -Werror-implicit-function-declaration -static -o lite_bench bench.o ../leck/libleck.la ../lite/liblite.la -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib -ldirectfb -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib -lz -lfusion -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib -ldirect -lpthread -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib ../leck/libleck.la ../lite/liblite.la -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib -ldirectfb -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/
sysr
> >> oot/usr/lib -lz -lfusion -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib -ldirect -lpthread -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib
> >>> /home/buildroot/build/instance-0/output/host/usr/bin/powerpc-linux-gcc -Wall -O3 -pipe -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -static -Werror-implicit-function-declaration -static -o lite_bench bench.o -L/home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib ../leck/.libs/libleck.a /home/buildroot/build/instance-0/output/build/lite-0.8.10/lite/.libs/liblite.a ../lite/.libs/liblite.a /home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib/libdirectfb.a /home/buildroot/build/instance-0/output/build/directfb-1.7.7/lib/fusion/.libs/libfusion.a /home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib/libfusion.a /home/buildroot/build/instance-0/output/build/directfb-1.7.7/lib/direct/.libs/libdirect.a /home/buildroot/build/instance-0/output/host/usr/powerpc-buildroot-linux-uclibc/sysroot/usr/lib/libdirect.a -lz -lrt /home/build
root
> >> /build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/lib/libstdc++.so -lpthread -Wl,--rpath -Wl,/home/buildroot/build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/lib -Wl,--rpath -Wl,/home/buildroot/build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/lib
> >>> libtool: link: warning: library `/home/buildroot/build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/lib/libstdc++.la' was moved.
> >>> /home/buildroot/build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/bin/ld: attempted static link of dynamic object `/home/buildroot/build/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/powerpc-buildroot-linux-uclibc/5.4.0/../../../../powerpc-buildroot-linux-uclibc/lib/libstdc++.so'
> >>> collect2: error: ld returned 1 exit status
> >>> Makefile:378: recipe for target 'lite_bench' failed
> >>
> >> The linking with libstdc++.so is added by libtool and is caused by directfb.
> >> Not sure what is happening here. This isn't the same thing as for ppc64le, is it?
> >
> > I'm not entirely sure about that one, but it could be the following
> > (usual problem) : your create a C program, that you compile with gcc,
> > but you link it with a C++ library. With dynamic linking, it all works
> > fine because your C++ library has a NEEDED on libstdc++.so, but it
> > fails badly with static linking.
>
> But it actually _is_ linking with stdc++, thanks to libtool. Only it's using
> the dynamic one instead of the static one.
Then I don't know :-/
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-22 8:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 19:23 [Buildroot] Analysis of autobuild failures 18-19/11 Arnout Vandecappelle
2016-11-19 20:55 ` Romain Naour
2016-11-20 15:24 ` Arnout Vandecappelle
2016-11-20 23:18 ` Sam Bobroff
2016-11-24 20:48 ` Arnout Vandecappelle
2016-11-25 0:51 ` Sam Bobroff
2016-11-21 11:21 ` Waldemar Brodkorb
2016-11-21 23:40 ` Arnout Vandecappelle
2016-11-23 11:37 ` Waldemar Brodkorb
2016-11-23 12:06 ` Arnout Vandecappelle
2016-11-25 0:26 ` Waldemar Brodkorb
2016-11-21 11:44 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2016-11-21 14:51 ` Alexey Brodkin
2016-11-21 22:08 ` [Buildroot] " Thomas Petazzoni
2016-11-21 23:38 ` Arnout Vandecappelle
2016-11-22 8:26 ` Thomas Petazzoni [this message]
2016-11-22 15:30 ` Arnout Vandecappelle
2016-11-22 15:38 ` Thomas Petazzoni
[not found] ` <CANLo3Ji8MiH29tYCwmpu4KMDJkcm7-75EUGK1mq3e8Tnih6aZQ@mail.gmail.com>
2016-11-22 19:08 ` Romain Naour
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=20161122092656.39ae5aa4@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.