On Thu, Feb 06, 2014 at 10:07:20AM -0500, Paul Gortmaker wrote: > On Thu, Feb 6, 2014 at 9:07 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote: > > On 02/06/2014 05:57 AM, Jim Davis wrote: > >> > >> Building with the attached random configuration file, > >> > >> drivers/built-in.o: In function `ltc2945_set_value': > >> ltc2945.c:(.text+0x58b1ad): undefined reference to `__udivdi3' > >> ltc2945.c:(.text+0x58b1cc): undefined reference to `__udivdi3' > >> ltc2945.c:(.text+0x58b1dd): undefined reference to `__udivdi3' > >> ltc2945.c:(.text+0x58b1fb): undefined reference to `__udivdi3' > >> make: *** [vmlinux] Error 1 > >> > > > > I really love those auto-builders :-) > > > > Should be fixed in the next version of -next. > > Looks like the same problem cropped up in mips allmodconfig, but > w/o the nice pointer to the line number in the source... > > CC [M] lib/notifier-error-inject.o > CC [M] lib/pm-notifier-error-inject.o > ERROR: "__udivdi3" [drivers/hwmon/ltc2945.ko] undefined! > make[2]: *** [__modpost] Error 1 > make[1]: *** [modules] Error 2 > make: *** [sub-make] Error 2 > Yeah, having 64 bit divides in 32 bit builds just isn't a good idea. Something is wrong with my auto-build scripts ... they should catch that kind of problem before it hits -next. I'll need to get that fixed. Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
