From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-04-28
Date: Mon, 30 Apr 2018 22:21:35 +0200 [thread overview]
Message-ID: <20180430222135.7aee3a71@gmx.net> (raw)
In-Reply-To: <20180429060019.11112209D4@mail.bootlin.com>
On Sun, 29 Apr 2018 08:00:19 +0200 (CEST), Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Results for branch 'master'
> ===========================
[...]
> arm | log4cplus-1.1.2 | NOK | http://autobuild.buildroot.net/results/a58007263355e2734a8074d52b1b26b88973c39e |
> m68k | log4cplus-1.1.2 | NOK | http://autobuild.buildroot.net/results/7d6fd0872efd23c7de552ab637956902b43c3f58 |
A problem with the log4cplus configure time detection of clock_nanosleep() and later compile
failure with the used toolchain br-arm-cortex-m4-full-2018.02-891-g046c5e2.tar.bz2:
sleep.cxx: In function 'int log4cplus::helpers::unix_nanosleep(const timespec*, timespec*)':
sleep.cxx:55:56: error: 'clock_nanosleep' was not declared in this scope
return clock_nanosleep (CLOCK_REALTIME, 0, req, rem);
The clock_nanosleep() configure detections uses the following:
$ cat test_clock_nanosleep_002.cxx
extern "C" char clock_nanosleep ();
int main(int argc, char* argv[]) {
return clock_nanosleep();
}
$ ./host/usr/bin/arm-linux-g++ test_clock_nanosleep_002.cxx
...and compiles without errors, because libc.a defines clock_nanosleep:
$ nm -A staging/usr/lib/*.a | grep clock_nano
staging/usr/lib/libc.a:clock_nanosleep.o:00000000 T clock_nanosleep
But the definition in the staging/usr/include/time.h header file is disabled:
334 # if defined __USE_XOPEN2K && defined __UCLIBC_HAS_ADVANCED_REALTIME__
335 # ifdef __UCLIBC_HAS_THREADS_NATIVE__
336 /* High-resolution sleep with the specified clock.
337
338 This function is a cancellation point and therefore not marked with
339 __THROW. */
340 extern int clock_nanosleep (clockid_t __clock_id, int __flags,
341 const struct timespec *__req,
342 struct timespec *__rem);
343
I think because __UCLIBC_HAS_THREADS_NATIVE__ is not defined...
Maybe it is possible to overwrite the check via ac_cv_search_clock_nanosleep, but not sure
which are the right conditions for this...
Regards,
Peter
next prev parent reply other threads:[~2018-04-30 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-04-28 Thomas Petazzoni
2018-04-30 20:21 ` Peter Seiderer [this message]
2018-05-01 3:52 ` Baruch Siach
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=20180430222135.7aee3a71@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