Re: [Mingw-users] gcc compiling problems

[Paul G. <pga...@at...>]

> Hi
> 
> I'm trying to build an ARM targeted gcc using mingw
> 
> I have the following installed on my system
> 
> msysDTK-1.0.1
> MSYS-1.0.9
> MinGW-3.0.0-rc3
> 
> I'm using source for gcc 3.2.2 from ftp.gnu.org
> 
> binutils 2.14 has compiled & installed without problems
> 
> I configured gcc with
> 
> ../gcc-3.2.2/configure --target=$target --prefix=$prefix \
> --enable-targets=arm-elf --with-cpu=arm7tdmi --enable-interwork
> --enable-mul tilib \ --with-gcc --with-gnu-ld --with-gnu-as \
> --without-local-prefix \ --with-gnu-as --with-gnu-ld \
> --disable-win32-registry --disable-threads \
> --enable-languages="c,c++" --disable-nls
> 
> and make LANGUAGES=c
> 
> this bit is disturbing
> 
> make[1]: Leaving directory `/c/projects/mingw/gcc/arm-gcc/gcc'
> Configuring in arm-thumb-elf/libstdc++-v3
> loading cache ../config.cache
> checking host system type... arm-thumb-elf
> checking target system type... arm-thumb-elf
> checking build system type... i686-pc-mingw32
> checking for Cygwin environment... (cached) no
> checking for mingw32 environment... (cached) no
> checking for gawk... (cached) gawk
> checking whether ln -s works... (cached) no
> 
> I don't know why it hasn't detected the mingw environment

	.fstab may not be mounting Mingw directory.  Using Windows Install, there is a post install script that is run.  
Part of what that post-install script does is determine where your Mingw runtime, etc. is at.  Now, you are using ARM, 
so I have to assume you can edit your equivalent of a user level  .fstab script.

	Try modifying your .fstab to accommodate a reference to where your Mingw runtime, etc. is located at 
(directory references).  I do not know if this will solve your problem.  Even so, it seems the most logical "next step" at 
this point.

	If I have analysed this correctly, mounting Mingw runtime, etc. may also resolve the invalid path delimeter 
error noted below.

	I am under the impression (wrong as it may be) that Msys should, under normal conditions, convert both 
ways (ie. windows-type path delimters to unix/posix-type path delimeters to windows-type path delimiters).  I do know 
that Msys, under normal conditions (Windows OS), can deal with both the unix/posix-type of path delimeters and the 
windows-type of path delimeters.

	Paul G.
> 
> this too, something has decided to use \ instead of / in a path
> somewhere
> 
> checking command to parse C:\msys\arm\arm-thumb-elf\bin\nm.exe
> output... ../../../gcc-3.2.2/libstdc++-v3/../ltconfig:
> C:msysarmarm-thumb-elfbinnm.exe: command not found
> ../../../gcc-3.2.2/libstdc++-v3/../ltconfig:
> C:msysarmarm-thumb-elfbinnm.exe: command not found failed
> 
> and the final error
> 
> checking for exception model to use... configure: error: unable to
> detect exception model make: *** [configure-target-libstdc++-v3] Error
> 1
> 
> 
> I have no idea how to proceed from here. Anyone got any ideas
> 
> 
> Dave
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single
> machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual
> machines at the same time. Free trial click here:
> http://www.vmware.com/wl/offer/345/0
> _______________________________________________ MinGW-users mailing
> list Min...@li...
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users