powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures
Michael Ellerman
mpe at ellerman.id.au
Wed Aug 3 12:46:47 AEST 2016
"Luis R. Rodriguez" <mcgrof at kernel.org> writes:
> Are linux-next builds being tested for powerpc with allyesconfig and
> allmodconfig ?
Yes, every single version:
http://kisskb.ellerman.id.au/kisskb/target/2659/
> I have some changes I'm making and while debugging my
> build issues I decided to give a clean build a shot and see linux-next
> next-20160729 up to next-20160729 all have build failures without my
> changes. I get:
>
> /opt/gcc-4.9.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
> drivers/built-in.o: .opd is not a regular array of opd entries
> MODPOST vmlinux.o
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> /opt/gcc-4.9.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld:
> drivers/built-in.o: .opd is not a regular array of opd entries
> drivers/built-in.o: In function `.ipw2100_up':
> ipw2100.c:(.text+0x1ff9c90): relocation truncated to fit:
> R_PPC64_REL24 (stub) against symbol `.round_jiffies_relative' defined
> in .text section in kernel/built-in.o
And yes this is a known problem, there have been attempts to fix it, but
none that quite got working.
In fact it's our bug #1 :)
https://github.com/linuxppc/linux/issues/1
Please use allmodconfig, which should build in general. Or one of our
other defconfigs, eg. ppc64/ppc64le defconfig.
cheers
More information about the Linuxppc-dev
mailing list