From: Segher Boessenkool <segher@kernel.crashing.org>
To: 涂家礼 <jl.tu@siat.ac.cn>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Some error when installing the gcc9.4.0，when "make".
Date: Thu, 16 Jun 2022 08:17:35 -0500 [thread overview]
Message-ID: <20220616131735.GF25951@gate.crashing.org> (raw)
In-Reply-To: <6806c378.34a1.18132afeeae.Coremail.jl.tu@siat.ac.cn>
Hi!
On Sun, Jun 05, 2022 at 03:06:39PM +0800, 涂家礼 wrote:
> make[4]: Warning: File `../libiberty/pic/libiberty.a' has modification time 8.1 s in the future
This could be a serious problem. But, it seems unrelated to your
problem. OTOH, "make" very much does not like things that time travel.
> /usr/bin/ld: /usr/local/lib/gcc/x86_64-pc-linux-gnu/9.4.0/crtbeginS.o: unrecognized relocation (0x2a) in section `.text'
Your /usr/bin/ld does not know about the relocation
R_X86_64_REX_GOTPCRELX (which is numeric 42) apparently. Use a newer
linker? You likely used a newer linker and assembler etc. to compile
stuff, to get this far, so figure out why not now?
Segher
next prev parent reply other threads:[~2022-06-16 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 7:06 涂家礼
[not found] ` <dded06c330c45362fa72cc19f31991c187022986.camel@xry111.site>
2022-06-16 8:25 ` 涂家礼
2022-06-16 13:17 ` Segher Boessenkool [this message]
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=20220616131735.GF25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jl.tu@siat.ac.cn \
/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).