This is the mail archive of the crossgcc@sources.redhat.com 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] |
* Vermeulen Jan <Jan.Vermeulen@siemens.atea.be> on Fri, Jun 01, 2001: > > After i tried compiling gcc again, it spit out the, expected, library > errors. > Then i made newlib and changed the specs and libgcc1-test.c files > and re-compiled gcc... > Hmm, I don't know anything about the specs m68k-coff uses, but if you initially configure using --without-headers --with-newlib, then do a "make all-gcc", you shouldn't get any errors on that phase of the compiler. The only way I could see you having problems is if m68k-coff's are so screwy that it requires stuff that is needed for libgcc, but I don't think so. Also, do a "make install-gcc" to install gcc by itself, which won't pick up any dependancies that would cause build errors. Then, after you build newlib, you can go back and reconfigure gcc w/out --without-headers --with-newlib, and you can proceed to do a full make (all) and install without any problems. You won't even have to clean that directory, it'll just rebuild a few key files, but everything else remains unchanged. If you do have to modify your specs after building newlib, you may want to try removing "specs" and "specs.ready" in your gcc build directory, before reconfiguring and rebuilding gcc. M. R. ------ 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] |