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 > > . > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
