public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "todd_richmond at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/106779] GCC 12.2 fails to compile in libiberty - uknown symbol PTR - requires later patch Date: Tue, 30 Aug 2022 19:07:16 +0000 [thread overview] Message-ID: <bug-106779-4-43p4NGrveM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106779-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106779 --- Comment #7 from Todd Richmond <todd_richmond at hotmail dot com> --- i was playing w/ cmdline and had deleted an extra arg. the 12.2 path is before the 12.1 path. However, our build scripts include the correct gcc header dir to all configure lines to ensure we don't pull in the system gcc headers. This causes 12.2 to include the source include dir (var/tmp...) last instead of first It is strange that this only fails for 12.2. I rebuilt 12.1 yesterday w/o issue so did something change in Makefile.in or a configure script that changed the include order? I can confirm that removing the original gcc include paths from the compile works correctly fail: /tools/arch/Linux_3.10.0-x86_64/gcc-12.1.0-bootstrap/bin/gcc -c -DHAVE_CONFIG_H -fPIC -O3 -pipe -DNDEBUG -Wno-error=unused-value -Wno-unused-variable -I/tools/arch/Linux_3.10.0-x86_64/gcc-12.2.0-bootstrap/include -I/tools/arch/Linux_3.10.0-x86_64/gcc-12.1.0-bootstrap//include -I. -I/var/tmp/gcc-12.2.0-bootstrap/gcc-12.2.0/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE -fcf-protection /var/tmp/gcc-12.2.0-bootstrap/gcc-12.2.0/libiberty/objalloc.c -o objalloc.o succeed: /tools/arch/Linux_3.10.0-x86_64/gcc-12.1.0-bootstrap/bin/gcc -c -DHAVE_CONFIG_H -fPIC -O3 -pipe -ffunction-sections -fdata-sections -march=nehalem -mtune=broadwell -DNDEBUG -Wno-error=unused-value -Wno-unused-variable -I. -I/var/tmp/gcc-12.2.0-bootstrap/gcc-12.2.0/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE -fcf-protection /var/tmp/gcc-12.2.0-bootstrap/gcc-12.2.0/libiberty/objalloc.c -o objalloc.o
next prev parent reply other threads:[~2022-08-30 19:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-30 16:30 [Bug bootstrap/106779] New: " todd_richmond at hotmail dot com 2022-08-30 16:33 ` [Bug bootstrap/106779] " todd_richmond at hotmail dot com 2022-08-30 17:12 ` jakub at gcc dot gnu.org 2022-08-30 17:59 ` todd_richmond at hotmail dot com 2022-08-30 18:00 ` todd_richmond at hotmail dot com 2022-08-30 18:04 ` jakub at gcc dot gnu.org 2022-08-30 18:10 ` jakub at gcc dot gnu.org 2022-08-30 19:07 ` todd_richmond at hotmail dot com [this message] 2022-08-30 23:42 ` egallager at gcc dot gnu.org 2022-08-31 7:48 ` jakub 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-106779-4-43p4NGrveM@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).