From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: kernel 4.18+ build problem "Recursive variable 'KBUILD_CFLAGS' "
Date: Sun, 23 Sep 2018 22:09:04 +0200 [thread overview]
Message-ID: <1537733344.1707.7.camel@sipsolutions.net> (raw)
In-Reply-To: <1537733001.1707.5.camel@sipsolutions.net> (sfid-20180923_220334_818247_9A235E8D)
On Sun, 2018-09-23 at 22:03 +0200, Johannes Berg wrote:
> On Sun, 2018-09-23 at 16:16 +0200, Hauke Mehrtens wrote:
> > Hi,
> >
> > I tried to compile backports against kernel 4.18 and 4.19-rc4 (header
> > files from Ubuntu) and ran into this problem when it wants to link the
> > kernel:
> >
> > LD [M]
> > /home/hauke/compat-wireless/backports-4.19-rc4-1/drivers/net/wireless/realtek/rtlwifi/rtl_usb.o
> > Building modules, stage 2.
> > scripts/Makefile.lib:10: *** Recursive variable 'KBUILD_CFLAGS'
> > references itself (eventually). Stop.
>
> Hmm. I vaguely remember something like that with our driver, but can't
> find it now? I also remember trying to fix it in the upstream kernel ...
Hmm. Well, I can't find any changes from me upstream in this area, so
either I didn't succeed or it didn't get applied. I also can't find a
public record of a patch, so I guess I didn't succeed?
Seems simple enough though, just make cc-option := instead of = in
scripts/Kbuild.include? Or maybe not, dunno.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-09-24 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 14:16 kernel 4.18+ build problem "Recursive variable 'KBUILD_CFLAGS' " Hauke Mehrtens
2018-09-23 20:03 ` Johannes Berg
2018-09-23 20:09 ` Johannes Berg [this message]
2018-09-23 20:48 ` Hauke Mehrtens
2018-09-23 20:49 ` Johannes Berg
2018-09-24 7:18 ` Johannes Berg
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=1537733344.1707.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
/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).