This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, > Interesting. To track this down, one would look for the command > that creates tcb-offsets.h.d, and extract it into a very small shell > script > that reproduces the problem without Make getting in the way. > This is a bit of an art. > > You might also consider trying making c:\b a 'managed mode' directory; > there's some tiny chance that would work around some problems. > See the crosstool howto or the cygwin doc about managed mode mounts. Unfortunately I was not able to find out which shell script creates this file (as you already said: "> This is a bit of an art." ... ). I mounted the build directory in the cygwin - 'managed mode' but I still got the same error. So I shortened all other names and path I could: I renamed the target to: i386-linux-gnu (instead of i386-unknown-linux-gnu) I renamed TOOLCOMBO to "go" (instead of glibc-3.2.3-gcc-3.2.3/i386-unknown-linux-gnu) And the compilation completed successfully ! (Is this a workaround or a solution ? ;) ) So now I have to return to my debug-problem I posted earlier - I have the same with this new toolchain... ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |