From: Al Stone <ahs3@redhat.com>
To: Lv Zheng <lv.zheng@intel.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>
Cc: Lv Zheng <zetalog@gmail.com>,
linux-acpi@vger.kernel.org, Al Stone <ah3@redhat.com>
Subject: Re: [PATCH 1/2] ACPI: ACPICA: Add non-linux host build support
Date: Mon, 3 Apr 2017 15:47:09 -0600 [thread overview]
Message-ID: <5ce80bd8-c0c8-8ba9-872f-80af844a1ac1@redhat.com> (raw)
In-Reply-To: <45fb52dc64ba477ae07c135aecd3b68394f5893b.1490930522.git.lv.zheng@intel.com>
On 03/30/2017 10:53 PM, Lv Zheng wrote:
> _LINUX: used to detect a target build is a linux kernel/application.
> __linux__: used to detect a build is on a linux hosts.
>
> Thus we can see: if a linux kernel build is performed on environments other
> than linux hosts, __linux__ may not be defined by the compiler and _LINUX
> cannot cover linux kernel resident ACPICA files, as it's only defined in
> <linux/acpi.h> and hence only allows non ACPICA kernel files to correctly
> include aclinux.h.
> As a conclusion, we don't actually support such build.
>
> This patch adds -D_LINUX for ACPICA files so that kernel builds on any
> hosts can use unified _LINUX as a linux kernel target indication to
> correctly include aclinux.h.
>
> Cc: Al Stone <ah3@redhat.com>
> Signed-off-by: Lv Zheng <lv.zheng@intel.com>
> ---
> drivers/acpi/acpica/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/acpica/Makefile b/drivers/acpi/acpica/Makefile
> index 32d93ed..dea6530 100644
> --- a/drivers/acpi/acpica/Makefile
> +++ b/drivers/acpi/acpica/Makefile
> @@ -2,7 +2,7 @@
> # Makefile for ACPICA Core interpreter
> #
>
> -ccflags-y := -Os -DBUILDING_ACPICA
> +ccflags-y := -Os -D_LINUX -DBUILDING_ACPICA
> ccflags-$(CONFIG_ACPI_DEBUG) += -DACPI_DEBUG_OUTPUT
>
> # use acpi.o to put all files here into acpi.o modparam namespace
>
These patches do solve the particular compilation problem I was having
(targeting an embedded arm64 system), so thank you for that. The build
test obviously needs fixing, but with the Linaro aarch64-elf compilers,
and the defconfig,
Tested-by: Al Stone <ahs3@redhat.com>
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
next prev parent reply other threads:[~2017-04-03 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 4:53 [PATCH 1/2] ACPI: ACPICA: Add non-linux host build support Lv Zheng
2017-03-31 4:53 ` [PATCH 2/2] ACPI: ACPICA: Cleanup drivers/acpi/acpica Makefile Lv Zheng
2017-04-02 6:29 ` kbuild test robot
2017-04-02 8:16 ` kbuild test robot
2017-04-11 7:19 ` Zheng, Lv
2017-04-11 13:53 ` Rafael J. Wysocki
2017-04-12 2:11 ` Zheng, Lv
2017-04-03 21:47 ` Al Stone [this message]
2017-04-11 7:22 ` [PATCH 1/2] ACPI: ACPICA: Add non-linux host build support Zheng, Lv
2017-04-11 7:48 ` [PATCH v2] " Lv Zheng
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=5ce80bd8-c0c8-8ba9-872f-80af844a1ac1@redhat.com \
--to=ahs3@redhat.com \
--cc=ah3@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=zetalog@gmail.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;
as well as URLs for NNTP newsgroup(s).