From: 涂家礼 <jl.tu@siat.ac.cn>
To: gcc-help@gcc.gnu.org
Subject: Some error when installing the gcc9.4.0，when "make".
Date: Sun, 5 Jun 2022 15:06:39 +0800 (GMT+08:00) [thread overview]
Message-ID: <6806c378.34a1.18132afeeae.Coremail.jl.tu@siat.ac.cn> (raw)
Hello. I want to know how to solve a problem when install gcc without root and offline. I am installing GCC9.4.0, but there are some errors when executing make command, as follows:
make[4]: Entering directory `/public/home/jltu/gcc-9.4.0/gcc-9.4.0/lto-plugin'
/bin/sh ./libtool --tag=CC --tag=disable-static --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../lto-plugin -I../../ lto-plugin/../include -DHAVE_CONFIG_H -Wall -g -c -o lto-plugin.lo ../../lto-plugin/lto-plugin.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../lto-plugin -I../../lto-plugin/../include -DHAVE_CONFIG_H -Wall -g -c ../../lto-plugin/lto-plugin.c -fPIC -DPIC -o .libs/lto-plugin.o
make[4]: Warning: File `../libiberty/pic/libiberty.a' has modification time 8.1 s in the future
/bin/sh ./libtool --tag=CC --tag=disable-static --mode=link gcc -Wall -g -Wc,-static-libgcc -module -bindir /public /home/jltu/gcc_build/libexec/gcc/x86_64-pc-linux-gnu/9.4.0 -Xcompiler '-static-libstdc++' -Xcompiler '-static-libg cc' -o liblto_plugin.la -rpath /public/home/jltu/gcc_build/libexec/gcc/x86_64-pc-linux-gnu/9.4.0 lto-plugin.lo -Wc,. ./libiberty/pic/libiberty.a
libtool: link: gcc -shared -fPIC -DPIC .libs/lto-plugin.o -static-libgcc -static-libstdc++ -static-libgcc ../lib iberty/pic/libiberty.a -Wl,-soname -Wl,liblto_plugin.so.0 -o .libs/liblto_plugin.so.0.0.0
/usr/bin/ld: /usr/local/lib/gcc/x86_64-pc-linux-gnu/9.4.0/crtbeginS.o: unrecognized relocation (0x2a) in section `.te xt'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make[4]: *** [liblto_plugin.la] Error 1
make[4]: Leaving directory `/public/home/jltu/gcc-9.4.0/gcc-9.4.0/lto-plugin'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/public/home/jltu/gcc-9.4.0/gcc-9.4.0/lto-plugin'
make[2]: *** [all-stage1-lto-plugin] Error 2
make[2]: Leaving directory `/public/home/jltu/gcc-9.4.0/gcc-9.4.0'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/public/home/jltu/gcc-9.4.0/gcc-9.4.0'
make: *** [all] Error 2
Regards
Jiali Tu
next reply other threads:[~2022-06-05 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 7:06 涂家礼 [this message]
[not found] ` <dded06c330c45362fa72cc19f31991c187022986.camel@xry111.site>
2022-06-16 8:25 ` 涂家礼
2022-06-16 13:17 ` Segher Boessenkool
2022-06-20 7:35 ` 涂家礼
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=6806c378.34a1.18132afeeae.Coremail.jl.tu@siat.ac.cn \
--to=jl.tu@siat.ac.cn \
--cc=gcc-help@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).