ckmake build issue with undefined symbol mcount
Tree generated with
./gentree.py --clean --verbose --git-revision next-20140221 /root/linux-next /tmp/next
When running devel/ckmake I see the following
[...]
23 3.7.10 [ LINK ] 24 3.8.13 [ LINK ] 25 3.9.11 [ LINK ] 26 3.10.29 [ LINK ] 27 3.11.10 [ LINK ] 28 3.12.10 [ LINK ] 29 3.13.2 [ LINK ] 30 3.14-rc1 [ LINK ]
Looking at ckmake.log there seems to be a problem with mcount.
Building backport-include/backport/autoconf.h ... done. /root/ksrc-backports/usr/src/linux-headers-3.7.10-030710-generic/arch/x86/Makefile:103: CONFIG_X86_X32 enabled but no binutils support
CC [M] /tmp/next/.tmp.ckmake/3.7.10/compat/lib-cordic.o LD [M] /tmp/next/.tmp.ckmake/3.7.10/compat/compat.o LD [M] /tmp/next/.tmp.ckmake/3.7.10/compat/cordic.o
Building modules, stage 2.
MODPOST 2 modules
WARNING: "mcount" [/tmp/next/.tmp.ckmake/3.7.10/compat/cordic.ko] undefined!
WARNING: "mcount" [/tmp/next/.tmp.ckmake/3.7.10/compat/compat.ko] undefined!
This is also the case for every kernel mentioned above.
Stefan
Quoted 1 line · Stefan Assmann
next-20140221
Did you git reset --hard backports-20140221 ? The respective dated tag for backports must be used for a specific dated tag for linux-next. Likewise for the stable releases.
Luis
Quoted 9 lines · Luis R. Rodriguez
Quoted 1 line · Stefan Assmann
next-20140221
Did you git reset --hard backports-20140221 ? The respective dated tag for backports must be used for a specific dated tag for linux-next. Likewise for the stable releases.
Luis
My backports tree is at 8e946501aef6e3dd5bac12eb45d24df8248672b0 which should be the same as backports-20140221.
Stefan
Quoted 8 lines · Stefan Assmann
Quoted 7 lines · Luis R. Rodriguez
Quoted 1 line · Stefan Assmann
next-20140221
Did you git reset --hard backports-20140221 ? The respective dated tag for backports must be used for a specific dated tag for linux-next. Likewise for the stable releases.
Quoted 8 lines
Quoted 2 lines
Luis
My backports tree is at
8e946501aef6e3dd5bac12eb45d24df8248672b0which should be the same as backports-20140221.Stefan
I tried the same again in a newly installed VM and don't see any issues there. Probably an issue with my build env then. Please ignore.
Stefan
Quoted 12 lines · Stefan Assmann
Quoted 11 lines · Stefan Assmann
Quoted 9 lines · Luis R. Rodriguez
Quoted 1 line · Stefan Assmann
next-20140221
Did you git reset --hard backports-20140221 ? The respective dated tag for backports must be used for a specific dated tag for linux-next. Likewise for the stable releases.
Luis
Quoted 8 lines
Quoted 5 lines
My backports tree is at
8e946501aef6e3dd5bac12eb45d24df8248672b0which should be the same as backports-20140221.Stefan
I tried the same again in a newly installed VM and don't see any issues there. Probably an issue with my build env then. Please ignore.
It may related to the used gcc version. I recall a similar issue with mcount when I had a kernel build with a different gcc than the driver module.
Regards,
Arend
Quoted 5 lines
Stefan
--
To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html