public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28860] New: --enable-kernel=5.1.0 build fails because of missing __convert_scm_timestamps
Date: Thu, 03 Feb 2022 18:28:42 +0000 [thread overview]
Message-ID: <bug-28860-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28860
Bug ID: 28860
Summary: --enable-kernel=5.1.0 build fails because of missing
__convert_scm_timestamps
Product: glibc
Version: 2.35
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: nsz at gcc dot gnu.org
CC: carlos at redhat dot com
Target Milestone: ---
if i configure glibc 2.35 for 32bit arm with --enable-kernel=5.1.0
or above then the build fails with
/usr/bin/ld: /work/build/libc_pic.os.clean: in function `__libc_recvmsg64':
/work/glibc/socket/../sysdeps/unix/sysv/linux/recvmsg.c:45: undefined reference
to `__convert_scm_timestamps'
/usr/bin/ld: /work/build/libc_pic.os.clean: in function `__GI___recvmmsg64':
/work/glibc/socket/../sysdeps/unix/sysv/linux/recvmmsg.c:78: undefined
reference to `__convert_scm_timestamps'
/usr/bin/ld: /work/build/libc.so: hidden symbol `__convert_scm_timestamps'
isn't defined
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-02-03 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:28 nsz at gcc dot gnu.org [this message]
2022-02-03 20:15 ` [Bug build/28860] " adhemerval.zanella at linaro dot org
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-28860-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).