From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-07-20
Date: Mon, 22 Jul 2019 20:21:40 +0200 [thread overview]
Message-ID: <20190722202140.207e29c3@gmx.net> (raw)
In-Reply-To: <9f2cfe09-b9af-285f-b192-f7b2bc975d68@andin.de>
Hello Andreas,
On Mon, 22 Jul 2019 16:09:59 +0200, Andreas Naumann <dev@andin.de> wrote:
> Hello Peter, all,
>
>
> Am 21.07.19 um 21:01 schrieb Peter Seiderer:
> > Hello *,
> >
> > On Sun, 21 Jul 2019 06:00:34 -0000, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> >
> >> Hello,
> >>
> >> Build statistics for 2019-07-20
> >
> > [...]
> >
> >> sparc64 | libv4l-1.16.5 | NOK | http://autobuild.buildroot.net/results/79c1e1b7a1bc53c1e9b2ae0c9acb443e6d2e2994 |
> >
> > make[4]: Entering directory '/home/buildroot/build/instance-1/output/build/libv4l-1.16.5/utils/qv4l2'
> >
> > [...]
> >
> > CXXLD qv4l2
> > libtool: warning: library '/home/buildroot/build/instance-1/output/host/bin/../sparc64-buildroot-linux-gnu/sysroot/usr/lib/libQt5Widgets.la' was moved.
> > libtool: error: cannot find the library '' or unhandled argument '/libQt5Gui.so'
> > Makefile:571: recipe for target 'qv4l2' failed
> >
> >
> >>From host/sparc64-buildroot-linux-gnu/sysroot/usr/lib/libQt5Widgets.la:
> >
> > # Libraries that this one depends upon.
> > dependency_libs='-latomic /libQt5Gui.so /libQt5Core.so -lpthread -lrt -lpthread -ldl '
>
>
> I have rebuilt the sparc config that led to this failure as well as an
> arm config (imx6-sabresd_qt5) and can confirm that both now (Qt 5.12.4)
> create lines like
> dependency_libs='-latomic <pkg-build-dir>/lib/libQt5Core.so -lpthread
> -lrt -lpthread -ldl '
>
> instead of (Qt 5.11.3)
> dependency_libs='-L<pkd-build-dir>/lib -lQt5Core -lrt -ldl -latomic
> -lpthread '
>
> Right now I dont have the time to find out why and what exactly has
> changed in Qt (or elsewhere) to cause that.
>
> >
> > This can be fixed by reverting 'qt5: Remove *.la/*.prl fixup script' ([1]), and adding
> >
> > -e "s:\/lib\([a-zA-Z0-9_-]*\)\.so:-l\1:g"
> >
> > to the sed statement, resulting in the following dependency_libs line:
> >
> > # Libraries that this one depends upon.
> > dependency_libs='-latomic -lQt5Gui -lQt5Core -lpthread -lrt -lpthread -ldl '
>
> Obviously the la fixup code in pkg-generic.mk is no longer able to
> handle the occurence of so-files with full path correctly. However, I
> wonder if pkg-generic would be an acceptable place to fix the issue.?
Can confirm that the following (quick hack) fixes the problem too:
--- a/package/pkg-generic.mk
+++ b/package/pkg-generic.mk
@@ -305,6 +305,7 @@ $(BUILD_DIR)/%/.stamp_staging_installed:
-e "s:@TOOLCHAIN_EXTERNAL_INSTALL_DIR@:$(TOOLCHAIN_EXTERNAL_INSTALL_DIR):g") \
-e "s:@STAGING_DIR@:$(STAGING_DIR):g" \
-e "s:@BASE_DIR@:$(BASE_DIR):g" \
+ -e "s:\/lib\([a-zA-Z0-9_-]*\)\.so:-l\1:g" \
"$${la}.fixed" && \
if cmp -s "$${la}" "$${la}.fixed"; then \
rm -f "$${la}.fixed"; \
Regards,
Peter
>
>
> regards,
> Andreas
>
>
> >
> > Regards,
> > Peter
> >
> > [1] https://git.buildroot.net/buildroot/commit/?id=428e5276e4df0b4bbd75df38565298ad53ea4f8b
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
next prev parent reply other threads:[~2019-07-22 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-07-20 Thomas Petazzoni
2019-07-21 19:01 ` Peter Seiderer
2019-07-22 14:09 ` Andreas Naumann
2019-07-22 18:21 ` Peter Seiderer [this message]
2019-07-23 13:14 ` Andreas Naumann
2019-07-23 19:36 ` Peter Seiderer
2019-07-24 8:09 ` Andreas Naumann
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=20190722202140.207e29c3@gmx.net \
--to=ps.report@gmx.net \
--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.