On 3 Jun 2000, Alexandre Oliva wrote:
> On May 30, 2000, Ossama Othman <[EMAIL PROTECTED]> wrote:
>
> > On Wed, May 31, 2000 at 12:46:34AM -0400, Kevin Atkinson wrote:
>
> >> ltconfig: `./ltcf-gcj.sh' does not exist
>
> >> Not that big of a deal but quite annoying, especially since libtoolize
> >> doesn't install it for you.
>
> > Hmm. Alexandre?
>
> Weird... It shouldn't be using this file at all, unless you're using
> AC_PROG_GCJ. Maybe I goofed somewhere?
I actually notice that it not only looks for AC_PROG_GCJ it actually
configures for it:
loading cache ./config.cache within ltconfig
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for objdir... .libs
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... (cached) yes
checking if cc static flag -static works... (cached) yes
checking if cc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking if cc supports -fno-rtti -fno-exceptions ... no
checking whether the linker (ld) supports shared libraries... no
checking how to hardcode library paths into programs... unsupported
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... Linux ld.so
checking command to parse /usr/bin/nm -B output... failed
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for dlfcn.h... (cached) yes
checking whether a program can dlopen itself... (cached) yes
checking whether a statically linked program can dlopen
itself... (cached) no
appending configuration tag "GCJ" to libtool
then it does the same for CXX..... I only want it for CXX...
--
Kevin Atkinson
[EMAIL PROTECTED]
http://metalab.unc.edu/kevina/
