On Mon, 5 Mar 2001, Nick Hudson wrote:

>OK so your libtool thinks that gcc (not cc) is your default compiler.
>How did you build your libtool? The standard -current pkgsrc one should
>pick up cc

Ok, I renamed /usr/bin/gcc to something else, and tried to build libtool.
This way there should be no gcc interference by your theory, but I got these
errors.  I am using a pretty current pkgsrc with sup update every morningi at 
5:00am.  After I put gcc back, libtool builds fine, but it still picks gcc
over cc.

...
===> Deinstalling for libtool-base-1.4.20010219nb2
Running PKG_DBDIR=/var/db/pkg /usr/sbin/pkg_delete -r
libtool-base-1.4.20010219nb2
=> Checksum OK for libtool-ml-20010219.tar.gz.
===> Extracting for libtool-base-1.4.20010219nb2
/usr/pkgsrc/distfiles//libtool-ml-20010219.tar.gz:       76.8%
===> Patching for libtool-base-1.4.20010219nb2
===> Applying NetBSD patches for libtool-base-1.4.20010219nb2
===> Configuring for libtool-base-1.4.20010219nb2
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found

----------------------------------------------------------
Configuring libtool 1.4a (1.641.2.179 2001/02/15 21:55:40)
----------------------------------------------------------

checking for gcc... gcc
checking whether the C compiler (gcc -O2 ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
*** Error code 1

            Ruibiao