On Sat, Oct 29, 2016 at 3:23 AM, Zheng, Lv <lv.zheng@xxxxxxxxx> wrote: > Hi, > > Please try this patch: > https://patchwork.kernel.org/patch/9392155/ > Which makes tools/power/acpi build more robust to survive toolchains that are not generated from the current kernel header. Better, but no, it doesn't fully fix the issue. DESCEND power/acpi DESCEND tools/acpidbg output/host/usr/bin/i586-buildroot-linux-uclibc-gcc -D_LINUX -I../../../include -I.. /../../drivers/acpi/acpica -Wall -Wstrict-prototypes -Wdeclaration-after-statement -O1 -g -DDEBUG -DACPI_APPLICATI ON -DACPI_SINGLE_THREAD -DACPI_DEBUGGER -I. -I../../../../../drivers/acpi/acpica -I../../include -c -o acpidbg.o acpidbg.c acpidbg.c:12:23: fatal error: acpi/acpi.h: No such file or directory #include <acpi/acpi.h> ^ compilation terminated. <builtin>: recipe for target 'acpidbg.o' failed > > Thanks > Lv > >> From: Andy Shevchenko [mailto:andy.shevchenko@xxxxxxxxx] >> Subject: Fix in ACPICA tools broke cross compilation of tools/power/acpi >> >> Hi! >> >> Reverting of the commit e323c02dee59 ("ACPICA: MSVC9: Fix <sys/stat.h> >> inclusion order issue") fixes the following issue: >> >> DESCEND power/acpi >> DESCEND tools/acpidbg >> output/host/usr/bin/i586-buildroot-linux-uclibc-gcc -D_LINUX >> -I../../../include -I../../../drivers/acpi/acpica -Wall >> -Wstrict-prototypes -Wdeclaration-after-statement -O1 -g -DDEBUG >> -DACPI_APPLICATION -DACPI_SINGLE_THREAD -DACPI_DEBUGGER -I. >> -I../../../../../drivers/acpi/acpica -I../../../../../include -c -o >> acpidbg.o acpidbg.c >> In file included from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/asm/sigcontext.h:18:0, >> from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/bits/sigcontext.h:30, >> from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/signal.h:335, >> from ../../../../../include/acpi/platform/acenv.h:365, >> from ../../../../../include/acpi/acpi.h:56, >> from acpidbg.c:12: >> ../../../../../include/linux/types.h:14:26: error: conflicting types >> for ‘fd_set’ >> typedef __kernel_fd_set fd_set; >> ^ >> In file included from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/sys/types.h:219:0, >> from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/stdlib.h:198, >> from ../../../../../include/acpi/platform/acenv.h:357, >> from ../../../../../include/acpi/acpi.h:56, >> from acpidbg.c:12: >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/sys/select.h:77:5: >> note: previous declaration of ‘fd_set’ was here >> } fd_set; >> ^ >> In file included from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/asm/sigcontext.h:18:0, >> from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/bits/sigcontext.h:30, >> from >> output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/signal.h:335, >> from ../../../../../include/acpi/platform/acenv.h:365, >> from ../../../../../include/acpi/acpi.h:56, >> from acpidbg.c:12: >> ../../../../../include/linux/types.h:15:25: error: conflicting types for ‘dev_t’ >> typedef __kernel_dev_t dev_t; >> >> And so on... >> >> After revert: >> >> DESCEND power/acpi >> DESCEND tools/acpidbg >> output/host/usr/bin/i586-buildroot-linux-uclibc-gcc -D_LINUX >> -I../../../include -I../../../drivers/acpi/acpica -Wall >> -Wstrict-prototypes -Wdeclaration-after-statement -O1 -g -DDEBUG >> -DACPI_APPLICATION -DACPI_SINGLE_THREAD -DACPI_DEBUGGER -I. >> -I../../../../../drivers/acpi/acpica -I../../../../../include -c -o >> acpidbg.o acpidbg.c >> LD test-topic/acpidbg >> /usr/bin/install -c -d output/target/usr/sbin >> /usr/bin/install -c test-topic/acpidbg output/target/usr/sbin >> >> Any ideas how to fix this properly? >> >> -- >> With Best Regards, >> Andy Shevchenko -- With Best Regards, Andy Shevchenko -- 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
