From: Yisheng Xie <xieyisheng1@huawei.com>
To: "Zheng, Lv" <lv.zheng@intel.com>,
"Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"wmiles@sgl.com" <wmiles@sgl.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"guohanjun@huawei.com" <guohanjun@huawei.com>,
"wangxiongfeng2@huawei.com" <wangxiongfeng2@huawei.com>
Subject: Re: [PATCH] ACPICA: arm64: fix compile apci tools fail for arm64
Date: Thu, 20 Oct 2016 09:45:43 +0800 [thread overview]
Message-ID: <c88b5433-fbf0-1a15-11b2-b47c1872d48d@huawei.com> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E886A253FBF@SHSMSX101.ccr.corp.intel.com>
Hi,
On 2016/10/19 6:07, Zheng, Lv wrote:
> Hi,
>
> I'm not sure what you mean.
> I mean you need ACPI_USE_SYSTEM_INTTYPES in case s64 has already been defined in that environment.
> Are you sure s64 should be defined for your environment?
>
s64 is not defined in my build environment but in kernel code.
> IMO, s64 is kernel space specific, while you are compiling user space tools.
> It looks to me like there is something wrong with ARM kernel's asm/types.h.
>
>> I listed in change log. And I also have tried that way.
>> However, it still have many other errors.(I am sorry to not have listed all of them.)
>>
>> From the following log, you can see, all of the conflict type is from signal.h.
>> And maybe this patch is a better way to fix these compile error, without too much
>> change of code.
>>
>> Are you sure that it will cause order problem when build ACPICA on other build
>> environment, for it only effect aarch64.
>
> I'm not sure what this is.
> How did you get this?
> Were you compiling kernel acpi tools or compiling the kernel itself?
>
It's about compiling kernel acpi tools.
> For tool compilation, are you sure you have correctly configured your cross-compilation environment?
Maybe it is not my cross-compilation environment problem, for your also can reproduce it,
as your said in another email, right?
> Will you see problems in compiling ACPICA applications from:
> https://github.com/acpica/acpica
>
> Thanks
> Lv
>
> .
>
next prev parent reply other threads:[~2016-10-20 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 23:51 [PATCH] ACPICA: arm64: fix compile apci tools fail for arm64 Yisheng Xie
2016-10-17 22:26 ` Zheng, Lv
2016-10-18 11:46 ` Yisheng Xie
2016-10-18 22:07 ` Zheng, Lv
2016-10-20 1:45 ` Yisheng Xie [this message]
2016-10-20 18:42 ` Zheng, Lv
2016-10-21 19:40 ` Zheng, Lv
2016-10-24 8:01 ` Yisheng Xie
2016-10-24 14:25 ` Zheng, Lv
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=c88b5433-fbf0-1a15-11b2-b47c1872d48d@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=devel@acpica.org \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=wangxiongfeng2@huawei.com \
--cc=wmiles@sgl.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).