Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Apr 2002 12:25:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Apr 2002 12:25:38 -0400 Received: from megaela.fe.dis.titech.ac.jp ([131.112.171.110]:13584 "HELO megaela.srvf.org") by vger.kernel.org with SMTP id ; Sat, 20 Apr 2002 12:25:37 -0400 Date: Sun, 21 Apr 2002 01:25:30 +0900 Message-ID: From: GOTO Masanori To: Ben Greear Cc: linux-kernel Subject: Re: unresolved symbol: __udivdi3 In-Reply-To: <3CC08632.8020102@candelatech.com> User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386-debian-linux-gnu) MULE/4.1 (AOI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Fri, 19 Apr 2002 14:03:46 -0700, Ben Greear wrote: > I would like to be able to devide 64bit numbers in a kernel module, > but I get unresolved symbols when trying to insmod. > > Does anyone have any ideas how to get around this little issue > (without the obvious of casting the hell out of all my __u64s > when doing division and throwing away precision.)? Your architecture is i386? *Ad-hoc* solution is linking libgcc, thus you designate the following parameter during linking time: `gcc -print-libgcc-file-name` In addition, some architecture (sh, parisc) links libgcc.a. Look at arch/{sh,parisc}/Makefile. (I heard such architecture's gcc need libgcc for the basic calculation.) -- gotom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/