This is the mail archive of the crossgcc@sources.redhat.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 relying to my own mail here, just so the solutions known.. > >The problem turned out to be that gcc's spec file had been > >written with CR/LF's > >and the spec parser was choking (it was reading asm_spec as > >being "/r/n"..) > > > >Out of interest does anyone know why the spec was written with > >cr/lf's and how > >to stop it? > > Hi Rob, > > Did you use winzip to unpack the archive? That's a no-no for two reasons, > one of which can be fixed and one of which can't. The one that can't be > fixed: it doesn't handly cygwin symlinks correctly. The one that can: by > default WinZip uses CR/LF conversion when unpacking TAR files, which in > theory should give the right line-ends for the host system. Alas cygwin > wants what are (by PC/Dos/Windows standards) the wrong kind of EOLs. To > fix it, start WinZip, go to Options:Configuration:Miscellaneous, and make > sure the tick box next to 'TAR file smart CR/LF conversion' is OFF. > nope. used tar -xzf ;) that's not the issue. the spec file is generated when makeing gcc and gets installed to ${prefix}/lib/gcc-lib/${machine}/${version}. Rob Taylor Flying Pig Systems ------ 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] |