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] |
On 12/13/05, Wedde, Thomas <thomas.wedde@hfwk.de> wrote: > 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 ? ;) ) Thanks for the info! Sounds like a good workaround that should go into the crosstool howto. > So now I have to return to my debug-problem I posted earlier - I have > the same with this new toolchain... Please repost that in a separate thread. - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv ------ 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] |