[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] Re: gcc-3.2 problems in compiling GCL
From: |
Camm Maguire |
Subject: |
[Gcl-devel] Re: gcc-3.2 problems in compiling GCL |
Date: |
18 Feb 2003 16:46:46 -0500 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Greetings, and thanks for the insight. GCL does a subbuild of part of
GMP. With the default configure script canonical host of
m68k-unknown-linux-gnu, gmp3 adds -m68000 to the command line.
Perhaps the autobuilders should use m68020-unknown-linux-gnu as the
lowest common denominator?
In any case, I've done this for GCL myself, so all looks OK now.
Thanks again,
Richard Zidlicky <address@hidden> writes:
> On Sat, Feb 15, 2003 at 08:41:55AM -0500, Camm Maguire wrote:
> > Greetings! I've seen this before in earlier compilers on arm. Is
> > there a work around?
> >
> >
> > ./libgcl.a(gmp3_mpn_mul_n.o)(.text+0xe2c):scan/mul_n.c:977: undefined
> > reference to `__mulsi3'
>
> strange, mulsi3 calls should not be generated unless you happen to use
> -m68000 compiler option. Is there perhaps an explicit call to it from
> sacn/mul_n.c ? What happens if you compile that module with -m68020 ?
>
> Richard
>
>
>
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah