public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "creatorsmithmdt at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/105474] New: GCC fails to bootstrap with --disable-libstdcxx
Date: Wed, 04 May 2022 08:50:17 +0000 [thread overview]
Message-ID: <bug-105474-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105474
Bug ID: 105474
Summary: GCC fails to bootstrap with --disable-libstdcxx
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: creatorsmithmdt at gmail dot com
Target Milestone: ---
On a Debian WSL2 environment (identified as x86_64-pc-linux-gnu and
5.10.102.1-microsoft-standard-WSL2), gcc fails bootstrapping when configured
like so: ../gcc/configure --disable-libstdcxx --enable-languages=c,c++.
g++ -std=c++11 -g -O2 -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common
-DHAVE_CONFIG_H -DGENERATOR_FILE -static-libstdc++ -static-libgcc -o
build/genchecksum \
build/genchecksum.o .././libiberty/libiberty.a
mawk -f ../../gcc/gcc/opt-functions.awk -f ../../gcc/gcc/opt-read.awk \
-f ../../gcc/gcc/optc-save-gen.awk \
-v header_name="config.h system.h coretypes.h tm.h" < optionlist >
options-save.cc
/usr/bin/ld: .././libiberty/libiberty.a(hashtab.o): relocation R_X86_64_32S
against `.rodata' can not be used when making a PIE object; recompile with
-fPIE
/usr/bin/ld: .././libiberty/libiberty.a(xmalloc.o): relocation R_X86_64_32
against `.rodata.str1.1' can not be used when making a PIE object; recompile
with -fPIE
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:3013: build/genhooks] Error 1
make[3]: *** Waiting for unfinished jobs....
/usr/bin/ld: .././libiberty/libiberty.a(md5.o): relocation R_X86_64_32 against
`.rodata' can not be used when making a PIE object; recompile with -fPIE
/usr/bin/ld: .././libiberty/libiberty.a(xstrerror.o): relocation R_X86_64_32
against `.rodata.str1.1' can not be used when making a PIE object; recompile
with -fPIE
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:3013: build/genchecksum] Error 1
rm gfdl.pod gcc.pod gcov-dump.pod gcov-tool.pod fsf-funding.pod gpl.pod cpp.pod
gcov.pod lto-dump.pod
make[3]: Leaving directory '/home/zopolis4/gccbuild/gcc'
make[2]: *** [Makefile:4954: all-stage2-gcc] Error 2
make[2]: Leaving directory '/home/zopolis4/gccbuild'
make[1]: *** [Makefile:24086: stage2-bubble] Error 2
make[1]: Leaving directory '/home/zopolis4/gccbuild'
make: *** [Makefile:1023: all] Error 2
next reply other threads:[~2022-05-04 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 8:50 creatorsmithmdt at gmail dot com [this message]
2022-05-04 9:25 ` [Bug bootstrap/105474] " rguenth at gcc dot gnu.org
2022-05-04 9:38 ` jakub at gcc dot gnu.org
2022-12-04 6:31 ` creatorsmithmdt at gmail dot com
2024-04-01 5:21 ` pinskia at gcc dot gnu.org
2024-04-01 16:15 ` egallager at gcc dot gnu.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-105474-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: 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).