From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 14/16] site: set nanosleep() behaviour for glibc / musl
Date: Fri, 10 Jan 2020 16:53:00 +0000 [thread overview]
Message-ID: <20200110165302.27426-15-git@andred.net> (raw)
In-Reply-To: <20200110165302.27426-1-git@andred.net>
As per coreutils' (gnulib's) autotools test, nanosleep()
misbehaves on glibc (2.29), and works fine on musl.
During cross-compile, recent coreutils assume brokenness
when compiling for linux, which pessimises musl.
Set the correct result for musl, and for coherency reasons,
also specify the result for glibc.
Signed-off-by: André Draszik <git@andred.net>
---
meta/site/common-glibc | 1 +
meta/site/common-musl | 1 +
2 files changed, 2 insertions(+)
diff --git a/meta/site/common-glibc b/meta/site/common-glibc
index ca55d48e72..1a28a271ff 100644
--- a/meta/site/common-glibc
+++ b/meta/site/common-glibc
@@ -33,6 +33,7 @@ gl_cv_func_getcwd_abort_bug=${gl_cv_func_getcwd_abort_bug=no}
gl_cv_func_getcwd_null=${gl_cv_func_getcwd_null=yes}
gl_cv_func_getcwd_path_max=${gl_cv_func_getcwd_path_max=yes}
ac_cv_func_getgroups_works=${ac_cv_func_getgroups_works=yes}
+gl_cv_func_nanosleep=${gl_cv_func_nanosleep='no (mishandles large arguments)'}
gl_cv_func_working_mkstemp=${gl_cv_func_working_mkstemp=yes}
gl_cv_func_working_utimes=${gl_cv_func_working_utimes=yes}
diff --git a/meta/site/common-musl b/meta/site/common-musl
index 1e7efbc311..386991d2c4 100644
--- a/meta/site/common-musl
+++ b/meta/site/common-musl
@@ -39,6 +39,7 @@ gl_cv_func_getcwd_null=${gl_cv_func_getcwd_null=yes}
gl_cv_func_getcwd_path_max=${gl_cv_func_getcwd_path_max='no, but it is partly working'}
ac_cv_func_getgroups_works=${ac_cv_func_getgroups_works=yes}
gl_cv_func_gettimeofday_clobber=${gl_cv_func_gettimeofday_clobber=no}
+gl_cv_func_nanosleep=${gl_cv_func_nanosleep=yes}
gl_cv_func_tzset_clobber=${gl_cv_func_tzset_clobber=no}
gl_cv_func_gettimeofday_posix_signature=${gl_cv_func_gettimeofday_posix_signature=yes}
gl_cv_func_working_mkstemp=${gl_cv_func_working_mkstemp=yes}
--
2.23.0.rc1
next prev parent reply other threads:[~2020-01-10 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 16:52 [PATCH 00/16] site updates (autotools / coreutils) André Draszik
2020-01-10 16:52 ` [PATCH 01/16] site: linux has working chown() André Draszik
2020-01-10 16:52 ` [PATCH 02/16] site: musl has working memcmp() André Draszik
2020-01-10 16:52 ` [PATCH 03/16] site: musl and glibc have working mkstemp() André Draszik
2020-01-10 16:52 ` [PATCH 04/16] site: musl and glibc have glibc compatible calloc() André Draszik
2020-01-10 16:52 ` [PATCH 05/16] site: linux supports unlink() of executing program André Draszik
2020-01-10 16:52 ` [PATCH 06/16] site: musl and glibc have glibc compatible getcwd() André Draszik
2020-01-10 16:52 ` [PATCH 07/16] site: set getcwd() behaviour for long paths for glibc / musl André Draszik
2020-01-10 16:52 ` [PATCH 08/16] site: set getcwd() test result for abort()-bug " André Draszik
2020-01-10 16:52 ` [PATCH 09/16] site: musl and glibc have working getgroups() André Draszik
2020-01-10 16:52 ` [PATCH 10/16] site: linux supports NULL in utime() André Draszik
2020-01-10 16:52 ` [PATCH 11/16] site: musl and glibc have working utimes() André Draszik
2020-01-10 16:52 ` [PATCH 12/16] site: on linux, pipes are fifos with max link count of 1 André Draszik
2020-01-10 16:52 ` [PATCH 13/16] site: on linux, link(2) doesn't follow symlinks André Draszik
2020-01-10 16:53 ` André Draszik [this message]
2020-01-10 16:53 ` [PATCH 15/16] site: strtod() works in glibc / musl André Draszik
2020-01-10 16:53 ` [PATCH 16/16] site: musl and glibc have working mktime() André Draszik
2020-01-10 18:46 ` [PATCH 00/16] site updates (autotools / coreutils) Khem Raj
2020-01-11 14:10 ` Adrian Bunk
2020-01-11 14:32 ` Richard Purdie
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=20200110165302.27426-15-git@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/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