From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756786AbaBFRD7 (ORCPT ); Thu, 6 Feb 2014 12:03:59 -0500 Received: from mail-pa0-f67.google.com ([209.85.220.67]:61650 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752882AbaBFRD5 (ORCPT ); Thu, 6 Feb 2014 12:03:57 -0500 Date: Thu, 6 Feb 2014 09:03:56 -0800 From: Guenter Roeck To: Paul Gortmaker Cc: Jim Davis , Stephen Rothwell , linux-next , linux-kernel , jdelvare@suse.de, lm-sensors@lm-sensors.org Subject: Re: randconfig build error with next-20140206, in drivers/hwmon/ltc2945.c Message-ID: <20140206170356.GB25071@roeck-us.net> References: <52F39718.9070205@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 06, 2014 at 10:07:20AM -0500, Paul Gortmaker wrote: > On Thu, Feb 6, 2014 at 9:07 AM, Guenter Roeck 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