From: 涂家礼 <jl.tu@siat.ac.cn>
To: "Xi Ruoyao" <xry111@xry111.site>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Re: Some error when installing the gcc9.4.0，when "make".
Date: Thu, 16 Jun 2022 16:25:11 +0800 (GMT+08:00) [thread overview]
Message-ID: <40709aef.3e5e.1816b9dc7ef.Coremail.jl.tu@siat.ac.cn> (raw)
In-Reply-To: <dded06c330c45362fa72cc19f31991c187022986.camel@xry111.site>
Thank you , the problem does!
"Xi Ruoyao" <xry111@xry111.site>写道：
> On Sun, 2022-06-05 at 15:06 +0800, 涂家礼 wrote:
>
> /* snip */
>
> > /usr/bin/ld: /usr/local/lib/gcc/x86_64-pc-linux-gnu/9.4.0/crtbeginS.o: unrecognized relocation (0x2a) in section `.text'
> > /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
>
> According to a stackoverflow.com answer [1] it seems happening because
> your binutils is too old.
>
> [1]: https://stackoverflow.com/questions/52737698
>
> --
> Xi Ruoyao <xry111@xry111.site>
> School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-06-16 8:25 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 ` 涂家礼 [this message]
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=40709aef.3e5e.1816b9dc7ef.Coremail.jl.tu@siat.ac.cn \
--to=jl.tu@siat.ac.cn \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@xry111.site \
/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).