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

Re: [Mingw-users] configure with cross compiler



--- phil@flamewars.org wrote:
> Earnie Boyd <earnie_boyd@yahoo.com> said:
> 
> > phil@flamewars.org wrote:
> > > I've installed the Debian mingw32 package, but can't figure out
> how to 
> build software with it.
> > > 
> > > The binaries appear to be installed in /usr/i586-mingw32msvc/bin,
> and 
> running i586-mingw32msvc-gcc -v gives
> > > 
> > > Reading specs from /usr/lib/gcc-lib/i586-mingw32msvc/3.2/specs
> > > Configured with: /home/ron/devel/debian/mingw32/mingw32-
> 3.2/build_dir/src/gcc-3.2-20020817-1/configure -v --prefix=/usr
> --target=i586-
> mingw32msvc --enable-languages=c,c++ --enable-threads
> --disable-multilib --
> enable-version-specific-runtime-libs
> > > Thread model: win32
> > > gcc version 3.2 (mingw special 20020817-1)
> > > 
> > > So that's alright. But how do I go about getting a configure
> script to 
> use these binaries instead of the native ones? I've tried just about
> every 
> combination of --host, --target, and --build that I can think of, and
> I've 
> read http://www.libsdl.org/extras/win32/cross/README.txt , and that
> hasn't 
> seemed to help me either. Can anyone point me in the right direction?
> > > 
> > 
> > Based on the directory configuration that you give above you should
> be 
> > able to just do  `./configure --host=i586-mingw32msvc' but that may
> be 
> > dependent on the version of autoconf that configure was built with.
>  I 
> > would tend to do `./configure --host=i586-mingw32msvc 
> > --target=i586-mingw32msvc --build=`./config.guess`' to remove any
> doubt 
> > about what the default is.
> > 
> > Earnie.
> > 
> > 
> 
> Here's what I get:
> 
> phil@rama:~/SDL-1.2.5$ ./configure --host=i586-mingw32msvc
> --target=i586-
> mingw32msvc --build='.config.guess'
> loading cache ./config.cache
> checking host system type... i586-pc-mingw32msvc
> checking target system type... i586-pc-mingw32msvc
> checking for a BSD compatible install... (cached) /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) 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
> checking build system type... Invalid configuration `.config.guess':
> machine 
> `.config.guess' not recognized
> 
> checking for ranlib... (cached) ranlib
> checking for gcc... (cached) gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... no
> checking whether we are using GNU C... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for ld used by GCC... (cached) /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
> checking for BSD-compatible nm... (cached) /usr/bin/nm -B
> checking whether ln -s works... (cached) yes
> /configure: line 1473: test: i586-pc-mingw32msvc: unary operator
> expected
> checking for dlltool... no
> checking for as... (cached) as
> checking for objdump... (cached) objdump
> loading cache ./config.cache within ltconfig
> checking for object suffix... o
> checking for executable suffix... (cached) no
> checking for gcc option to produce PIC... none
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.lo... yes
> checking if gcc supports -fno-rtti -fno-exceptions ... yes
> checking if gcc static flag -static works... -static
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the linker (/usr/bin/ld) supports shared
> libraries... yes
> checking command to parse /usr/bin/nm -B output... ok
> checking how to hardcode library paths into programs... immediate
> checking for /usr/bin/ld option to reload object files... -r
> checking dynamic linker characteristics... Win32 ld.exe
> checking if libtool supports shared libraries... yes
> checking if package supports dlls... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for objdir... .libs
> creating libtool
> loading cache ./config.cache
> checking whether make sets ${MAKE}... (cached) yes
> checking for gcc... (cached) gcc
> checking whether the C compiler (gcc -g -O2 ) works... yes
> checking whether the C compiler (gcc -g -O2 ) is a cross-compiler...
> no
> checking whether we are using GNU C... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for inline... inline
> checking for working const... yes
> checking for c++... c++
> checking whether the C++ compiler (c++  ) works... yes
> checking whether the C++ compiler (c++  ) is a cross-compiler... no
> checking whether we are using GNU C++... yes
> checking whether c++ accepts -g... yes
> checking for a BSD compatible install... /usr/bin/install -c
> checking how to run the C preprocessor... gcc -E
> checking for working alloca.h... yes
> checking for alloca... yes
> checking Win32 compiler... no
> configure: error:
> *** Your compiler (gcc) does not produce Win32 executables!

I had this problem,
you need to do this :
see :  
http://introspector.sourceforge.net/dia_win32.htm
Environment Variable Settings:
setpath.sh)
PATH=/usr/i586-mingw32msvc/bin/:/usr/local/win32/build/:$PATH
(exportvars.sh)
CC=i586-mingw32msvc-gcc
LD=i586-mingw32msvc-ld
AR=i586-mingw32msvc-ar
NM=i586-mingw32msvc-nm
RANLIB=i586-mingw32msvc-ranlib
DLLTOOL=i586-mingw32msvc-dlltool
OBJDUMP=i586-mingw32msvc-objdump
STRIP=i586-mingw32msvc-strip
STRIPPROG=i586-mingw32msvc-strip
AS=i586-mingw32msvc-as
LC_ALL=C
SED=sed




=====
James Michael DuPont
http://introspector.sourceforge.net/

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/



Reply to: