[Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

From: "alexei_sylver1 at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110684] unknown spec function ‘dumps’ error, C compiler cannot create executables
Date: Fri, 28 Jul 2023 16:47:35 +0000	[thread overview]
Message-ID: <bug-110684-4-e4JPLq66rt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110684-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110684

--- Comment #16 from AlexK <alexei_sylver1 at mail dot ru> ---
I have copied already compileed shared libs into new directories:
cp -v prev-libcpp/libcpp.so libcpp/
cp -v prev-libbacktrace/libbacktrace.so libbacktrace/
cp -v prev-libdecnumber/libdecnumber.so libdecnumber/

and continue: make

Configuring stage 2 in ./gcc
configure: loading cache ./config.cache
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking LIBRARY_PATH variable... ok
checking GCC_EXEC_PREFIX variable... ok
checking whether to place generated files in the source directory... no
checking whether a default linker was specified... no
checking whether a default dsymutil was specified... no
checking whether a default assembler was specified... no
checking for x86_64-pc-linux-gnu-gcc... 
/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/xgcc
-B/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/
-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   -fno-checking
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether  /home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/xgcc
-B/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/
-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   -fno-checking accepts -g...
yes
checking for  /home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/xgcc
-B/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/
-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   -fno-checking option to
accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... no
checking whether  /home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/xg++
-B/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/ -nostdinc++
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs

-I/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu

-I/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/include
 -I/home/alexei/build/gcc-12.2.0/libstdc++-v3/libsupc++
-L/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
accepts -g... no
checking for x86_64-pc-linux-gnu-gnatbind...
/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/gnatbind
checking for x86_64-pc-linux-gnu-gnatmake... gnatmake
checking whether compiler driver understands Ada... no
checking for x86_64-pc-linux-gnu-gdc...
/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/gdc
-B/home/alexei/build/gcc-12.2.0/mybuild/./prev-gcc/
-B/tools/gcc-12.2.0/x86_64-pc-linux-gnu/bin/ -O2 -g
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libphobos/libdruntime/gcc
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libphobos/src
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libphobos/src/.libs
-I/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libphobos/libdruntime
-I/home/alexei/build/gcc-12.2.0/libphobos/libdruntime
-L/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libphobos/src/.libs
-B/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/alexei/build/gcc-12.2.0/mybuild/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
checking whether the D compiler works... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in `/home/alexei/build/gcc-12.2.0/mybuild/gcc':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
make[2]: *** [Makefile:4693: configure-stage2-gcc] Ошибка 1
make[2]: выход из каталога «/mnt/Git/apt-build/build/gcc-12.2.0/mybuild»
make[1]: *** [Makefile:27162: stage2-bubble] Ошибка 2
make[1]: выход из каталога «/mnt/Git/apt-build/build/gcc-12.2.0/mybuild»
make: *** [Makefile:1072: all] Error 2

I have GNAT in /opt/GNAT/2021
and
LD_LIBRARY_PATH=/opt/GNAT/2021/lib64:/home/alexei/build/gcc-12.2.0/mybuild/prev-gcc:/usr/local/lib:/usr/local/lib/x86_64-linux-gnu:/home/alexei/.local/lib:/usr/lib:/usr/lib/x86_64-linux-gnu

there is no gdc in compiled prev-gcc directory
I didn't define ada in lang list, and why compiler doesn't understands Ada

next prev parent reply	other threads:[~2023-07-28 16:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 15:09 [Bug other/110684] New: " alexei_sylver1 at mail dot ru
2023-07-16 15:11 ` [Bug other/110684] " alexei_sylver1 at mail dot ru
2023-07-16 15:14 ` alexei_sylver1 at mail dot ru
2023-07-16 15:16 ` alexei_sylver1 at mail dot ru
2023-07-16 15:18 ` alexei_sylver1 at mail dot ru
2023-07-16 17:08 ` pinskia at gcc dot gnu.org
2023-07-17 11:51 ` [Bug bootstrap/110684] " alexei_sylver1 at mail dot ru
2023-07-22  7:57 ` alexei_sylver1 at mail dot ru
2023-07-22  8:02 ` alexei_sylver1 at mail dot ru
2023-07-22  8:03 ` alexei_sylver1 at mail dot ru
2023-07-22  8:11 ` alexei_sylver1 at mail dot ru
2023-07-22  8:11 ` alexei_sylver1 at mail dot ru
2023-07-22  8:14 ` alexei_sylver1 at mail dot ru
2023-07-22  8:15 ` alexei_sylver1 at mail dot ru
2023-07-22  8:22 ` alexei_sylver1 at mail dot ru
2023-07-22  8:27 ` alexei_sylver1 at mail dot ru
2023-07-28 16:47 ` alexei_sylver1 at mail dot ru [this message]
2023-07-28 23:52 ` alexei_sylver1 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-110684-4-e4JPLq66rt@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).