linux-kernel - Re: randconfig build error with next-20140206, in drivers/hwmon/ltc2945.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140206170356.GB25071@roeck-us.net>
Date:	Thu, 6 Feb 2014 09:03:56 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Jim Davis <jim.epost@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, jdelvare@...e.de,
	lm-sensors@...sensors.org
Subject: Re: randconfig build error with next-20140206, in
 drivers/hwmon/ltc2945.c

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@...ck-us.net> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/