From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "No rule to make target" gcc 9.3.0 error
Date: Tue, 19 Oct 2021 07:47:03 -0400 [thread overview]
Message-ID: <6d03af6b-73c0-c985-297c-39519019ba2d@bonedaddy.net> (raw)
In-Reply-To: <YW6ssXPkYARgEc+f@waltdnes.org>
On 10/19/2021 7:32 AM, Walter Dnes wrote:
> On Tue, Oct 19, 2021 at 11:53:28AM +1000, Miles Malone wrote
>> Select a version of gcc you do have, using gcc-config. Then rebuild
>> libtool, and continue. GCC 9.3.0 doesnt exist because it's been
>> replaced in the gcc9 branch by GCC 9.4.0. You could choose to stick
>> to GCC9, or move to 10 or 11.
> Re-emerging sys-devel/libtool doesn't work. I've only got gcc 10 and
> 11. 9 isn't in the tree. After rebuilding libtool I still get...
>
> [thimk2][root][/usr/src/linux] ../makeover
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> make[4]: *** No rule to make target '/usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/include/stddef.h', needed by '/usr/src/linux-5.4.97-gentoo/tools/objtool/fixdep.o'. Stop.
> make[3]: *** [Makefile:39: /usr/src/linux-5.4.97-gentoo/tools/objtool/fixdep-in.o] Error 2
> make[2]: *** [/usr/src/linux-5.4.97-gentoo/tools/build/Makefile.include:5: fixdep] Error 2
> make[1]: *** [Makefile:67: objtool] Error 2
> make: *** [Makefile:1830: tools/objtool] Error 2
>
> Is there a way to pull an old gcc ebuild into my tree?
This may be overkill but:
1. Copy your .config out of /usr/src/linux
2. make mrproper
3. Copy back your .config
4. make oldconfig
next prev parent reply other threads:[~2021-10-19 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 1:47 [gentoo-user] "No rule to make target" gcc 9.3.0 error Walter Dnes
2021-10-19 1:53 ` Miles Malone
2021-10-19 11:32 ` Walter Dnes
2021-10-19 11:47 ` Todd Goodman [this message]
2021-10-19 13:30 ` [gentoo-user] [SOLVED] " Walter Dnes
2021-10-19 14:30 ` Walter Dnes
2021-10-19 13:28 ` [gentoo-user] " Matt Connell (Gmail)
2021-10-19 14:37 ` Walter Dnes
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=6d03af6b-73c0-c985-297c-39519019ba2d@bonedaddy.net \
--to=tsg@bonedaddy.net \
--cc=gentoo-user@lists.gentoo.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