From: Philipp Rudo <prudo@linux.ibm.com>
To: Jeremy Cline <jcline@redhat.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: s390 depending on cc-options makes it difficult to configure
Date: Tue, 18 Feb 2020 10:37:52 +0100 [thread overview]
Message-ID: <20200218103752.6d4b9167@laptop2-ibm.local> (raw)
In-Reply-To: <20200216185759.GA4091960@dev.jcline.org>
Hi Masahiro,
On Sun, 16 Feb 2020 13:57:59 -0500
Jeremy Cline <jcline@redhat.com> wrote:
> On Sun, Feb 16, 2020 at 01:08:49PM +0900, Masahiro Yamada wrote:
> > On Sat, Feb 15, 2020 at 5:35 AM Jeremy Cline <jcline@redhat.com> wrote:
> > >
> > > On Fri, Feb 14, 2020 at 12:31:05PM +0900, Masahiro Yamada wrote:
> > > > Hi.
> > > >
> > > > On Tue, Feb 11, 2020 at 3:49 AM Philipp Rudo <prudo@linux.ibm.com> wrote:
[...]
> > > > One idea to workaround this is
> > > > to use a fake script that accepts any flag,
> > > > and use it as $(CC) in Kconfig.
> > > >
> > > > RFC patch is attached.
> > > >
> > > > This is not a perfect solution, of course.
I like the approach as it gives both sides what they need without blowing up
Kconfig.
> > > The attached patch doesn't looks like it'd work for what we need,
> >
> > I thought turning all cc-options to y would work
> > for what you need.
> >
> > With this, you can enable
> > CONFIG_MARCH_Z13=y and CONFIG_TUNE_Z14=y
> > instead of CONFIG_TUNE_DEFAULT.
> >
> > If this approach does not work for you,
> > what is your requirement?
> >
>
> Oof, this was an awful typo. It *would* work for what we need. Sorry for
> the confusion :(.
>
> >
> >
> > > although I wonder if it's easier to just check when cc-options is
> > > defined for an environment variable or something and always return y
> > > instead of calling out to $(CC) at all. Comes to the same thing, I
> > > suppose.
> >
> >
> > The macro definition in scripts/Kconfig.include
> > takes precedence over any environment variable.
> >
> > So, if you want to hack it from the environment,
> > you need to change the code somehow.
> >
> > The scripts/dummy-tools/ approach does not change
> > anything for the use-case in upstream.
> >
> > The result is the same, of course.
> >
>
> Indeed. Since I'm not maintaining it I don't have a particularly strong
> opinion about the approach. Whatever you like most works for me.
I agree with Jeremy. Just pick what you think is best.
Thanks a lot
Philipp
prev parent reply other threads:[~2020-02-18 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 16:41 Jeremy Cline
2019-12-10 9:01 ` 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 [this message]
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=20200218103752.6d4b9167@laptop2-ibm.local \
--to=prudo@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jcline@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mkubecek@suse.cz \
/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
all inboxes | Powered by JetHome®