public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilfridge at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29780] New: possible parallel make issue in glibc-2.36 (siglist-aux.S: No such file or directory)
Date: Sat, 12 Nov 2022 21:01:56 +0000 [thread overview]
Message-ID: <bug-29780-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29780
Bug ID: 29780
Summary: possible parallel make issue in glibc-2.36
(siglist-aux.S: No such file or directory)
Product: glibc
Version: 2.36
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: dilfridge at gentoo dot org
CC: carlos at redhat dot com
Target Milestone: ---
Automated build testing in Gentoo found this error:
x86_64-pc-linux-gnu-gcc -m64 -pipe -march=native -fno-diagnostics-color -O2
-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 _itowa.c -c
-std=gnu11 -fgnu89-inline -pipe -march=native -fno-diagnostics-color -O2 -Wall
-Wwrite-strings -Wundef -fmerge-all-constants -frounding-math -fstac
x86_64-pc-linux-gnu-gcc -m64 -pipe -march=native -fno-diagnostics-color -O2
-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0
../sysdeps/unix/sysv/linux/renameat.c -c -std=gnu11 -fgnu89-inline -pipe
-march=native -fno-diagnostics-color -O2 -Wall -Wwrite-strings -Wundef
-fmerge-all-con
x86_64-pc-linux-gnu-gcc -m64 -pipe -march=native -fno-diagnostics-color -O2
-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0
../sysdeps/posix/cuserid.c -c -std=gnu11 -fgnu89-inline -pipe -march=native
-fno-diagnostics-color -O2 -Wall -Wwrite-strings -Wundef -fmerge-all-constants
-fro
x86_64-pc-linux-gnu-gcc -m64 -pipe -march=native -fno-diagnostics-color -O2
-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 siglist.S -c
-U_FORTIFY_SOURCE -I../include
-I/var/tmp/portage/sys-libs/glibc-2.36-r5/work/build-amd64-x86_64-pc-linux-gnu-nptl/stdio-common
-I/var/tmp/port
siglist.S:4:11: fatal error: siglist-aux.S: No such file or directory
4 | # include "siglist-aux.S"
| ^~~~~~~~~~~~~~~
Sources are given by the tag
https://gitweb.gentoo.org/fork/glibc.git/tree/?h=gentoo/glibc-2.36-5
(roughly release/2.36/master as of 15 October).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-12 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 21:01 dilfridge at gentoo dot org [this message]
2022-11-12 21:02 ` [Bug build/29780] " dilfridge at gentoo dot org
2022-11-12 21:46 ` schwab@linux-m68k.org
2022-11-12 22:09 ` dilfridge at gentoo dot org
2022-11-12 22:10 ` dilfridge at gentoo dot org
2022-11-21 16:39 ` schwab@linux-m68k.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-29780-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).