From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Fwd: syntax error in prepare target of main Makefile
Date: Sun, 7 May 2023 20:29:22 +0700 [thread overview]
Message-ID: <db732251-b6fe-c2c5-a0db-bac77dc84314@gmail.com> (raw)
Hi,
I notice a year old bug in bugzilla [1]. As many developers don't
take a look on it, I decided to forward the bug by mail. And
to reach the reporter, you must log in to bugzilla.
Quoting from the bug report:
> Christian 2022-04-08 10:44:17 UTC
>
> Symptom:
>
> make[2]: Entering directory '/usr/src/kernels/5.17.1-1.el8.elrepo.x86_64'
> Makefile:729: target 'include/config/auto.conf' does not exist
> test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
> echo >&2; \
> echo >&2 " ERROR: Kernel configuration is invalid."; \
> echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
> echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
> echo >&2 ; \
> /bin/false)
> Makefile:1717: target 'prepare' does not exist
> if [ "gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)" != ""gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"" ]; then \
> echo >&2 "warning: the compiler differs from the one used to build the kernel"; \
> echo >&2 " The kernel was built by: "gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)""; \
> echo >&2 " You are using: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"; \
> fi
> /bin/sh: -c: line 0: syntax error near unexpected token `('
> /bin/sh: -c: line 0: `if [ "gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)" != ""gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)"" ]; then \'
> make[2]: *** [Makefile:1717: prepare] Error 1
> make[2]: Leaving directory '/usr/src/kernels/5.17.1-1.el8.elrepo.x86_64'
>
>
> Note the double double-quotes in the GCC Version comparison !
>
> This happens to me when I try to compile vmware kernel modules with mainline kernel from elrepo on AlamLinux8.
>
> Since it is coming from the Makefile of the Kernel, I suppose this is the proper upstream tracker to be used. Please advise if not.
>
>
> This is the potion of the Makefile that fails (line 1717..) :
> prepare:
> @if [ "$(CC_VERSION_TEXT)" != "$(CONFIG_CC_VERSION_TEXT)" ]; then \
> echo >&2 "warning: the compiler differs from the one used to build the kernel"; \
> echo >&2 " The kernel was built by: $(CONFIG_CC_VERSION_TEXT)"; \
> echo >&2 " You are using: $(CC_VERSION_TEXT)"; \
> fi
>
>
>
> I don't know where CONFIG_CC_VERSION_TEXT is defined. Which apparently contains "...", but shouldn't.
>
>
To the reporter: It is helpful to try compiling your third-party modules
against latest mainline kernel.
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=215820
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-05-07 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 13:29 Bagas Sanjaya [this message]
2023-05-08 5:26 ` syntax error in prepare target of main Makefile Masahiro Yamada
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=db732251-b6fe-c2c5-a0db-bac77dc84314@gmail.com \
--to=bagasdotme@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox