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: Sat, 22 Jul 2023 08:27:57 +0000 [thread overview] Message-ID: <bug-110684-4-lI9mwt7oyj@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 #15 from AlexK <alexei_sylver1 at mail dot ru> --- I have attached all patches I have made to several Makefile.in in different folders (I created them with `diff` tool) after that I made building directory: installdir=/tools/gcc-12.2.0 install -v -d mybuild cd mybuild ../configure --prefix="$installdir" --without-build-config LD=ld --enable-libssp --enable-bootstrap --enable-lto --with-isl=/usr/local --with-mpc=/usr/local --with-mpfr=/usr/local --with-gmp=/usr/local --with-system-zlib --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-gcov --enable-languages=c,c++,fortran,objc,obj-c++,jit,go --enable-host-shared --disable-multilib --enable-shared a few changes to Makefile: sed -i 's/^\(@endif bfd\)$/#\1/' Makefile sed -i 's/^\(@endif opcodes\)$/#\1/' Makefile # !!! https://stackru.com/questions/63879492/bez-sbrosa-kompilyatsiya-gcc-na-crostini-zavershaetsya-s-oshibkoj-s-neizvestnoj unset LIBRARY_PATH CPATH C_INCLUDE_PATH PKG_CONFIG_PATH CPLUS_INCLUDE_PATH INCLUDE LD_LIBRARY_PATH make .... stage1 was successfully finished
next prev parent reply other threads:[~2023-07-22 8:28 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 [this message] 2023-07-28 16:47 ` alexei_sylver1 at mail dot ru 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-lI9mwt7oyj@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).