From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14816] Build fails on latest master with a systemd build failure, implicit func declaration gettid() error
Date: Fri, 20 May 2022 07:37:48 +0000 [thread overview]
Message-ID: <bug-14816-163-OB2fJjd5TB@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14816-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14816
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998@free.fr
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Amol, All,
The failure is because systemd calls gettid(), and you are using a toolchain
that is tool old to provide it.
Indeed, gettid() was only introduced in glibc 2.30, but the Linaro toolchain
still uses glibc 2.25.
Use another toolchain.
It is not really trivial to prevent such a configuration, because we dpo not
have kconfig symbols that repreesents the glibc version (like we have for the
kernel headers or gcc), so maybe we should just add an ad-hoc excluion of that
toolchain (and other old ones?) in systemd/Config.in
Regards,
Yann E. MRON.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-20 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 5:24 [Buildroot] [Bug 14816] New: Build fails on latest master with a systemd build failure, implicit func declaration gettid() error bugzilla
2022-05-20 7:22 ` [Buildroot] [Bug 14816] " bugzilla
2022-05-20 7:37 ` bugzilla [this message]
2024-06-15 15:03 ` bugzilla
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=bug-14816-163-OB2fJjd5TB@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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