From: "Artem S. Tashkinov" <aros@gmx.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Cannot build Linux 5.17 on Fedora 36
Date: Wed, 18 May 2022 07:58:12 +0000 [thread overview]
Message-ID: <877bc1ca-e72b-1a48-25de-61250df601ad@gmx.com> (raw)
Hi,
I cannot build vanilla Linux 5.17:
# make defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/confdata.o
HOSTCC scripts/kconfig/expr.o
LEX scripts/kconfig/lexer.lex.c
YACC scripts/kconfig/parser.tab.[ch]
HOSTCC scripts/kconfig/lexer.lex.o
HOSTCC scripts/kconfig/menu.o
HOSTCC scripts/kconfig/parser.tab.o
HOSTCC scripts/kconfig/preprocess.o
HOSTCC scripts/kconfig/symbol.o
HOSTCC scripts/kconfig/util.o
HOSTLD scripts/kconfig/conf
*** Default configuration is based on 'x86_64_defconfig'
gold linker is not supported as it is not capable of linking the kernel
proper.
scripts/Kconfig.include:56: Sorry, this linker is not supported.
make[1]: *** [scripts/kconfig/Makefile:87: defconfig] Error 1
make: *** [Makefile:619: defconfig] Error 2
No idea what's going on. I've recently updated gcc and binutils packages.
# dnf update
Dependencies resolved.
Nothing to do.
Complete!
binutils-2.37-27.fc36.x86_64
gcc-12.1.1-1.fc36.x86_64
ls -la /etc/alternatives/ld
lrwxrwxrwx. 1 root root 15 Oct 7 2020 /etc/alternatives/ld ->
/usr/bin/ld.bfd
So, the symbolic link hasn't been changed in more than a year.
No idea what's going on. What am I missing?
Best regards,
Artem
next reply other threads:[~2022-05-18 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 7:58 Artem S. Tashkinov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 9:14 Cannot build Linux 5.17 on Fedora 36 Artem S. Tashkinov
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=877bc1ca-e72b-1a48-25de-61250df601ad@gmx.com \
--to=aros@gmx.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.