From: David Howells <dhowells@redhat.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: dhowells@redhat.com, Liz Zhang <lizzha@microsoft.com>,
Lili Deng <v-lide@microsoft.com>,
Manoj Srivastava <srivasta@debian.org>,
torvalds@linux-foundation.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Commit seems to prevent use of GNUmakefile wrappers
Date: Mon, 18 Mar 2019 14:43:37 +0000 [thread overview]
Message-ID: <23500.1552920217@warthog.procyon.org.uk> (raw)
Hi Mashiro,
commit 2b50f7ab63685cd247e32ad321f7338ed130d3d5
Author: Masahiro Yamada <yamada.masahiro@socionext.com>
kbuild: add workaround for Debian make-kpkg
seems to prevent the use of GNUmakefile wrappers to set the ARCH and
CROSS_COMPILE make variables. With this commit, I now see:
make: Entering directory '/data/fs/linux-fs'
Makefile:39: Do not include top Makefile of Linux Kernel
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
Makefile:605: include/config/auto.conf: No such file or directory
make: *** No rule to make target '.config', needed by 'include/config/auto.conf'. Stop.
make: Leaving directory '/data/fs/linux-fs'
Do you have a suggestion as to how to work around this? Here's a sample
GNUmakefile content:
CROSS_COMPILE := x86_64-linux-gnu-
ARCH := x86_64
MFLAGS += CROSS_COMPILE=$(CROSS_COMPILE) ARCH=$(ARCH)
export CROSS_COMPILE
export ARCH
include Makefile
David
next reply other threads:[~2019-03-18 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 14:43 David Howells [this message]
2019-03-19 4:05 ` Commit seems to prevent use of GNUmakefile wrappers Masahiro Yamada
2019-03-19 9:03 ` David Howells
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=23500.1552920217@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizzha@microsoft.com \
--cc=srivasta@debian.org \
--cc=torvalds@linux-foundation.org \
--cc=v-lide@microsoft.com \
--cc=yamada.masahiro@socionext.com \
/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