Unable to build acpi_asus module on current today

Today I tried rebuilding my laptop running current. Building the kernel
module acpi_asus, the build bombed with the error:
===> acpi_asus (all)
cc -O2 -fno-strict-aliasing -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I-
-I/usr/src/sys/modules/acpi/acpi_asus/../../../contrib/dev/acpica -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -c /usr/src/sys/modules /acpi/acpi_asus/../../../dev/acpi_support/acpi_asus.c
/usr/src/sys/modules/acpi/acpi_asus/../../../dev/acpi_support/acpi_asus.c: In function `acpi_asus_attach':
/usr/src/sys/modules/acpi/acpi_asus/../../../dev/acpi_support/acpi_asus.c:584: error: 'for' loop initial declaration used outside C99 mode

But this module has not been touched since April and I have built all of
it many times since then. Several other modules seem to have the same
problem of declaring a variable in a for statement.

I moved the declaration to its own statement before the "for" and it
compiles fine.

Did some compiler default recently change? I have no compile options on my
make.conf.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@xxxxxx Phone: +1 510 486-8634
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: yet another Forth: vmForth
    ... and MidLevel and HLL all Integrated in the Kernel. ... VM assembler and simulator from within the simulator for testing :-) ... higher level Forth constructs, like jz/jnz, lit, execute, call and jump. ... Compiles VM assembler mnemonics into the VM memory. ...
    (comp.lang.forth)
  • Re: compiling a 2.4 kernel
    ... Each patch is designed to be used against a particular version of the ... You might have an incompatible group of patches. ... patches into a single kernel. ... modconf, failed to detect) but this one as a separate module now compiles, ...
    (Debian-User)
  • (no subject)
    ... your module compiles fine on my box using this method ... > I have tried to compile the hello.c module under kernel 2.6.3. ... > int initial_module (void) ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • RE: Real-Time Preemption: BUG initializing kgdb
    ... The resulting kernel ... > which is not what kgdb wants in order to be happy. ... SA_NODELAY (no need to change more locks, as I'm on a non-SMP target). ... These changes resulted in a kernel which compiles and works fine, ...
    (Linux-Kernel)
  • Re: Finding kernel memory starting address on HPUX 11.0
    ... code that compiles under more than one compiler ... data limits initially are the ... There aren't really enforced sizes on shared memory usage (or anonymous ... Again - as with all kernel tunables, ...
    (comp.sys.hp.hpux)