[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool(2.2.4) detect native java compiler in cross-compilation envi

From: Roumen Petrov
Subject: Re: libtool(2.2.4) detect native java compiler in cross-compilation environment
Date: Tue, 27 May 2008 22:46:27 +0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080329 SeaMonkey/1.1.9

Ralf Wildenhues wrote:
Hello Roumen,

* Roumen Petrov wrote on Fri, May 09, 2008 at 09:39:11PM CEST:
In my environment exist GNU C and Java compilers along with mingw C cross-compiler. When I build libtool the path to mingw C-compiler (gcc) precede path to native C-compiler.

In configure output I see :
checking for i386-mingw32msvc-strip... i386-mingw32msvc-strip
checking for i386-mingw32msvc-gcc... i386-mingw32msvc-gcc
checking for i386-mingw32msvc-gcj... no
checking for gcj... gcj -> OOPS !!!!!
checking if gcj supports -fno-rtti -fno-exceptions... (cached) no
checking for gcj option to produce PIC...
checking if gcj static flag -static works... no
checking if gcj supports -c -o file.o... yes
checking if gcj supports -c -o file.o... (cached) yes
checking whether the gcj linker (/opt/mingw/i386-mingw32msvc/bin/ld)

Is above detection correct ?

Well, yes and no.  It's not nice and clean, but a compromise out of more
or less necessity.  For example, not always are "cross compilers"
prefixed correctly.  This happens with non-GNU cross compile setups, but
can also happen with, for example, compiling for MSYS under Cygwin.
Users complain if this is turned off.

Thanks. Now I understand why macros don't use first prefix found.
May be there is no solution to test that a specific compiler is cross-compiler.

The workaround for you is to
  ./configure GCJ=no

The check for Fortran compiler look similar but I don't have installed native Fortran-compiler so libtool configure don't detect any.

Same thing (FC=no F77=no) if you have a Fortran compiler installed.


Workarounds can be found after internet search.
If they are stable(standard) may be few words into source files, like - INSTALL, README, info pages or etc, could help more.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]