From: Jeremy Cline <jcline@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: s390 depending on cc-options makes it difficult to configure
Date: Mon, 9 Dec 2019 11:41:55 -0500 [thread overview]
Message-ID: <20191209164155.GA78160@dev.jcline.org> (raw)
Hi folks,
Commit 5474080a3a0a ("s390/Kconfig: make use of 'depends on cc-option'")
makes it difficult to produce an s390 configuration for Fedora and Red
Hat kernels.
The issue is I have the following configurations:
CONFIG_MARCH_Z13=y
CONFIG_TUNE_Z14=y
# CONFIG_TUNE_DEFAULT is not set
When the configuration is prepared on a non-s390x host without a
compiler with -march=z* it changes CONFIG_TUNE_DEFAULT to y which, as
far as I can tell, leads to a kernel tuned for z13 instead of z14.
Fedora and Red Hat build processes produce complete configurations from
snippets on any available host in the build infrastructure which very
frequently is *not* s390.
I did a quick search and couldn't find any other examples of Kconfigs
depending on march or mtune compiler flags and it seems like it'd
generally problematic for people preparing configurations.
Regards,
Jeremy
next reply other threads:[~2019-12-09 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 16:41 Jeremy Cline [this message]
2019-12-10 9:01 ` s390 depending on cc-options makes it difficult to configure Michal Kubecek
2019-12-11 17:18 ` Jeremy Cline
2020-02-10 18:49 ` Philipp Rudo
2020-02-14 3:31 ` Masahiro Yamada
2020-02-14 20:35 ` Jeremy Cline
2020-02-16 4:08 ` Masahiro Yamada
2020-02-16 18:57 ` Jeremy Cline
2020-02-18 9:37 ` Philipp Rudo
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=20191209164155.GA78160@dev.jcline.org \
--to=jcline@redhat.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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 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 NNTP newsgroup(s).