gabriel rosenkoetter wrote:
> 
> On Mon, Mar 05, 2001 at 10:01:39PM +0000, Nick Hudson wrote:
> > What is important is the compilers that libtool finds when it is built
> > as these are the only compilers it supports. gcc != cc != /usr/bin/cc !=
> > /usr/bin/gcc != ...
> 
> Huh?

gcc != cc, etc for libtool!


> ...(I
> did get a complaint about trying to install a new libtool-base over
> my installed libtool-1.3.5nb4, but that's for totally legitimate
> reasons, and I'm kind of using my laptop at the moment, so would
> rather not break everything libtool depends on by ripping it out
> and upgrading right now.)

libtool is special - you can delete it at any time (at the moment)

> Fwiw, in my config.log, I have:
> 
> configure:822: checking for gcc
> configure:935: checking whether the C compiler (cc -O2  -Wl,-R/usr/pkg/lib -L/us
> r/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/pkg/lib) works
> configure:951: cc -o conftest -O2   -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -Wl,-R/usr
> /pkg/lib -L/usr/pkg/lib conftest.c  1>&5
> configure:977: checking whether the C compiler (cc -O2  -Wl,-R/usr/pkg/lib -L/us
> r/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/pkg/lib) is a cross-compiler


So you picked up cc (not gcc)

> Ruibaio, based on what my copy of the Makefile picks up for the
> compiler (see the long command line above), something's probably
> misconfigured (whether automatically or actively) on your machine.

I'd agree with this.

Nick
-- 
aka skrll@netbsd.org, skrll@excite.co.uk