From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-09-17
Date: Thu, 19 Sep 2019 20:35:18 +0200 [thread overview]
Message-ID: <20190919203518.2c215f09@gmx.net> (raw)
In-Reply-To: <20190918061626.A01A88614D@whitealder.osuosl.org>
Hello,
On Wed, 18 Sep 2019 06:16:20 -0000, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> Autobuild statistics for 2019-09-17
> ===============================
[...]
>
> arch | reason | OK? | url | orph?
> -------------+--------------------------------+-----+---------------------------------------------------------------------------------+-------
> arm | apr-1.7.0 | NOK | http://autobuild.buildroot.net/results/4da73982f160305ac2d5d2b4f615fa98eec5a7a3 |
From build/apr-1.7.0/config.log:
configure:24288: checking whether int64_t and long long use fmt %lld
configure:24320: /home/seiderer/Work/Buildroot/build_arm_apr_001/host/bin/arm-linux-gcc -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Werror -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DLINUX -D_REENTRANT -D_GNU_SOURCE conftest.c >&5
In file included from /home/seiderer/Work/Buildroot/build_arm_apr_001/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/sys/types.h:26:0,
from conftest.c:147:
/home/seiderer/Work/Buildroot/build_arm_apr_001/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/include/features.h:218:5: error: #warning requested reentrant code, but thread support was disabled [-Werror=cpp]
# warning requested reentrant code, but thread support was disabled
^~~~~~~
cc1: all warnings being treated as errors
configure:24320: $? = 1
configure: failed program was:
[...]
|
| #include <sys/types.h>
| #include <stdio.h>
| #ifdef HAVE_STDINT_H
| #include <stdint.h>
| #endif
|
| int main(int argc, const char *const *argv) {
|
| int64_t chk1, *ptr1;
| long long chk2, *ptr2 = &chk1;
| ptr1 = &chk2;
| *ptr1 = *ptr2 = 0;
| printf("%lld %lld", chk1, chk2);
|
| return 0; }
|
configure:24330: result: no
The test failure is a result of a toolchain without threads '# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS is not set'
and the given '-D_REENTRANT' compile flag (the same test without '-D_REENTRANT' compiles fine) plus '-Werror'...
Disable apr for toolchains without thread support?
Regards,
Peter
next prev parent reply other threads:[~2019-09-19 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 6:16 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-09-17 Thomas Petazzoni
2019-09-18 20:56 ` Peter Seiderer
2019-09-21 11:26 ` Arnout Vandecappelle
2019-09-23 19:02 ` Peter Seiderer
2019-09-19 18:35 ` Peter Seiderer [this message]
2019-09-21 9:33 ` Arnout Vandecappelle
2019-09-19 19:35 ` 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=20190919203518.2c215f09@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox