This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
I'm trying to do a Canadian cross from a cygwin (i686-pc-cygwin32) build machine for a mingw32 (i386-mingw32) host to a mips (mips-sony-psx) target. I am able to build the build X target and build X host just fine, but when I try to build the host X target I get stuck because i386-mingw32 tries to build collect2, with only three problems: `pipe()', `kill()', and `fork()' aren't supported on i386-mingw32. This is significant in the fact that when building from i686-pc-cygwin32 to i386-mingw32, collect2 isn't built anyway. But it is built for i686-pc-cygwin32 to mips-sony-psx, so it seems isolated to i686-pc-cygwin32. So why does i386-mingw32 try to build it if it's not supposed to exist natively for it? I've tried adding `use_collect2=no' to the target specification in gcc's configure and configure.in, to no avail. Do I need to specify it in the toplevel configure file? Or does it need to go where i386-mingw32 is specified? Or should I try to hack the configured Makefile and take collect2 out altogether? Any suggestions would be appreciated, thanks. Oh yeah, I've tried specifying `--with-gnu-ld' as well. Marcus ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |