Re: lib question

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Wed Jan 13 1999 - 14:16:07 EST


>
> On Jan 13, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>
> > This link order is carefully crafted, believe it or not.
> > In particular, we cannot do things like "-lc -lm -lc -lm -lc -lm -lc"
> > in the OSKit because we use library overriding a lot (it's totally
> > error prone, and I am totally opposed to it, but that's the way it is).
>
> I see. libc doesn't even appear in configure.in or the Makefiles any
> more, libtool takes care of it. -lm is a bit harder to remove, since
> several libraries depend on it.

What does "takes care of it" mean?
The oskit's script will break if you attempt to invoke them with "-lc",
or "-lm", for that matter. That's because there's no libc.a.
It's called liboskit_c.a.

>
> How portable is this script supposed to be? I mean, if libtool is
> fooled into believing it's compiling for the host, but it's actually
> cross-compiling to a different architecture, we might get in (more)
> trouble
>

My understanding is that configure should respect my choice of
CC and figure out whether it's cross-compiling or not. It tests
for it, does it not?

In short, I expect a configure invocation such as the following to
work:

PATH=$OSKITDIR/bin:$PATH \
CC=i386-oskit-gcc \
../kaffe/configure \
        --prefix=$PREFIX \
        --with-threads=oskit-pthreads \
        --with-engine=intrp \
        --with-staticlib \
        --without-x \
        --host=i386-oskit

    - Godmar


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:41 EDT