public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexei1.84 at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/108186] Bootstrap comparison failure.gcc-12.2.0 differs gcc/plugin.o gcc/gcc.o
Date: Wed, 21 Dec 2022 22:52:33 +0000 [thread overview]
Message-ID: <bug-108186-4-6PhfboQyu2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108186-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108186
--- Comment #8 from AlexK <alexei1.84 at mail dot ru> ---
(In reply to Richard Biener from comment #1)
> can you try configuring with --without-build-config please?
make[2]: вход в каталог «/mnt/Git/apt-build/build/gcc-12.2.0/build/c++tools»
/mnt/Git/apt-build/build/gcc-12.2.0/build/./gcc/xg++
-B/mnt/Git/apt-build/build/gcc-12.2.0/build/./gcc/ -nostdinc++ `if test -f
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/scripts/testsuite_flags;
then /bin/bash
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/scripts/testsuite_flags
--build-includes; else echo -funconfigured-libstdc++-v3 ; fi`
-L/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/lib/ -isystem
/tools/gcc-12.2.0/x86_64-pc-linux-gnu/include -isystem
/tools/gcc-12.2.0/x86_64-pc-linux-gnu/sys-include -fchecking=1
-static-libstdc++ -static-libgcc -o g++-mapper-server server.o resolver.o
../libcody/libcody.a ../libiberty/libiberty.a
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):
в функции «std::__throw_logic_error(char const*)»:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:70:
неопределённая ссылка на «libintl_gettext»
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):
в функции «std::__throw_domain_error(char const*)»:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:74:
неопределённая ссылка на «libintl_gettext»
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):
в функции «std::__throw_invalid_argument(char const*)»:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:78:
неопределённая ссылка на «libintl_gettext»
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):
в функции «std::__throw_length_error(char const*)»:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:82:
неопределённая ссылка на «libintl_gettext»
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):
в функции «std::__throw_out_of_range(char const*)»:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:86:
неопределённая ссылка на «libintl_gettext»
/usr/local/bin/ld:
/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(functexcept.o):/mnt/Git/apt-build/build/gcc-12.2.0/build/x86_64-pc-linux-gnu/libstdc++-v3/src/c++11/../../../../../libstdc++-v3/src/c++11/functexcept.cc:100:
далее есть ещё неопределённые ссылки на «libintl_gettext»
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:95: g++-mapper-server] Ошибка 1
make[2]: выход из каталога «/mnt/Git/apt-build/build/gcc-12.2.0/build/c++tools»
make[1]: *** [Makefile:14754: all-c++tools] Ошибка 2
make[1]: выход из каталога «/mnt/Git/apt-build/build/gcc-12.2.0/build»
make: *** [Makefile:1074: all] Ошибка 2
next prev parent reply other threads:[~2022-12-21 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 10:59 [Bug bootstrap/108186] New: " alexei1.84 at mail dot ru
2022-12-20 12:47 ` [Bug bootstrap/108186] " rguenth at gcc dot gnu.org
2022-12-20 13:34 ` pinskia at gcc dot gnu.org
2022-12-21 5:26 ` alexei1.84 at mail dot ru
2022-12-21 9:40 ` alexei1.84 at mail dot ru
2022-12-21 9:41 ` alexei1.84 at mail dot ru
2022-12-21 9:46 ` alexei1.84 at mail dot ru
2022-12-21 22:51 ` alexei1.84 at mail dot ru
2022-12-21 22:52 ` alexei1.84 at mail dot ru [this message]
2022-12-21 23:15 ` alexei1.84 at mail dot ru
2022-12-22 1:18 ` alexei1.84 at mail dot ru
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-108186-4-6PhfboQyu2@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).