From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-07
Date: Mon, 8 Oct 2018 20:39:26 +0200 [thread overview]
Message-ID: <20181008203926.5aa43bde@gmx.net> (raw)
In-Reply-To: <20181008060013.65E12207CC@mail.bootlin.com>
On Mon, 8 Oct 2018 08:00:13 +0200 (CEST), Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> Build statistics for 2018-10-07
> ===============================
>
[...]
> Results for branch 'master'
> ===========================
> i686 | qt5base-5.11.2 | NOK | http://autobuild.buildroot.net/results/66f55a311dcf9d54ca6148b232287973ba226999 |
> i686 | qt5base-5.11.2 | NOK | http://autobuild.buildroot.net/results/a4759e8cea09a597dbeb82f6c673ddc531d419e8 |
Both fail with:
.obj/qlinuxfbscreen.o: In function `QLinuxFbScreen::initialize()':
qlinuxfbscreen.cpp:(.text+0xa6c): undefined reference to `qt_open64(char const*, int, unsigned int)'
qlinuxfbscreen.cpp:(.text+0x1042): undefined reference to `qt_open64(char const*, int, unsigned int)'
qlinuxfbscreen.cpp:(.text+0x10aa): undefined reference to `qt_open64(char const*, int, unsigned int)'
qlinuxfbscreen.cpp:(.text+0x1746): undefined reference to `qt_open64(char const*, int, unsigned int)'
I suspect this qt commit 'Linux: Bypass glibc's broken open() implementation' ([1]), which introduced
the qt_open64() function, but did not see immediately why it fails here (uclibc?)...
Regards,
Peter
[1] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=1d33493989eae774bafc124f9d3ee68d7a017a10
next prev parent reply other threads:[~2018-10-08 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-07 Thomas Petazzoni
2018-10-08 18:39 ` Peter Seiderer [this message]
2018-10-09 17:37 ` Peter Seiderer
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=20181008203926.5aa43bde@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.