public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug hurd/28671] New: hurd: Build failure with PIE
Date: Wed, 08 Dec 2021 03:24:19 +0000 [thread overview]
Message-ID: <bug-28671-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28671
Bug ID: 28671
Summary: hurd: Build failure with PIE
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: hurd
Assignee: unassigned at sourceware dot org
Reporter: siddhesh at sourceware dot org
CC: samuel.thibault@ens-lyon.org, tschwinge at sourceware dot org
Target Milestone: ---
When building i686-gnu with build-many-glibcs.py and this patch[1] (with the
hunk changing sysdeps/mach/hurd removed) to enable PIE across the board in
glibc, the Hurd target fails as follows:
build-many-2/install/compilers/i686-gnu/lib/gcc/i686-glibc-gnu/11.2.1/../../../../i686-glibc-gnu/bin/ld:
cannot find build-many-2/build/glibcs/i686-gnu/glibc/csu/rcrt0.o: No such file
or directory
collect2: error: ld returned 1 exit status
make[3]: *** [../Rules:269:
build-many-2/build/glibcs/i686-gnu/glibc/support/test-run-command] Error 1
This prevents PIE from being enabled by default for hurd. I'll post the final
link of the commit and clearer steps to reproduce when it actually goes in.
[1]
https://patchwork.sourceware.org/project/glibc/patch/20211207082638.1960585-1-siddhesh@sourceware.org/
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-12-08 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 3:24 siddhesh at sourceware dot org [this message]
2021-12-13 21:33 ` [Bug hurd/28671] " samuel.thibault@ens-lyon.org
2021-12-14 2:49 ` siddhesh at sourceware dot org
2021-12-14 7:38 ` samuel.thibault@ens-lyon.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-28671-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).