public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/110467] New: Bootstrap with Ada enabled fails with --enable-host-pie Date: Wed, 28 Jun 2023 19:37:26 +0000 [thread overview] Message-ID: <bug-110467-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110467 Bug ID: 110467 Summary: Bootstrap with Ada enabled fails with --enable-host-pie Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- Since r14-2132: commit 4a48a38fa99f067b8f3a3d1a5dc7a1e602db351f Author: Eric Botcazou <ebotcazou@adacore.com> Date: Wed Jun 21 18:19:36 2023 +0200 ada: Fix build of GNAT tools gcc configured with e.g. .../gcc/configure --enable-languages=all --prefix=`pwd` --enable-checking=yes --with-gnu-ld --with-gnu-as --disable-libsanitizer --disable-bootstrap --enable-host-pie fails: /usr/bin/ld: b_gnatl.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: gnatlink.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: a-except.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: ali.o: relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: butil.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: casing.o: relocation R_X86_64_32S against symbol `csets__identifier_char' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: csets.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: debug.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: fmap.o: relocation R_X86_64_32S against `.bss' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: fname.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: gnatvsn.o: relocation R_X86_64_32S against symbol `gnat_version_string' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: hostparm.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: i-c.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: i-cstrin.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: namet.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: opt.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: osint.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: output.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: s-exctab.o: relocation R_X86_64_32S against symbol `system__exception_table__htable' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: s-secsta.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: snames.o: relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: stylesw.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: switch.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: targparm.o: relocation R_X86_64_32S against symbol `namet__global_name_buffer' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: types.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: validsw.o: relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: widechar.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
next reply other threads:[~2023-06-28 19:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 19:37 mpolacek at gcc dot gnu.org [this message] 2023-06-28 19:38 ` [Bug bootstrap/110467] " mpolacek at gcc dot gnu.org 2023-06-30 9:10 ` ebotcazou at gcc dot gnu.org 2023-06-30 13:50 ` mpolacek at gcc dot gnu.org 2023-06-30 15:36 ` ebotcazou at gcc dot gnu.org 2023-07-01 14:41 ` mpolacek at gcc dot gnu.org 2023-07-05 11:12 ` simon at pushface 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-110467-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).