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] |
On Wed, 25 Aug 1999, Brendan Simon wrote: > Will Sloan wrote: > > > Brendan Simon wrote: > > > > > Yep. It's a chicken and egg problem. I'm pretty sure you can build the C compiler > > > only without the runtime libs. You can then build the runtime libs with this > > > compiler. Once this is done you should be able to build all the other GCC components > > > such as C++, fortran, etc. > > > > > > > How do I just build the C compiler. I have tried --with-languages=c and make > > LANGUAGES="c" and both seem to build the runtime libs??? > > I think it's different for egcs and gcc. I think gcc-2.95.x uses "enable-languages=c" but > I haven't tried it yet. Do a "grep -i lang configure" to see what format to use. You > could also try "disable-languages" but then you would have to specify ALL the languages to > disable. By default, all language are built. > Yes, you are correct with the --enable-languages= vs. LANGUAGES= statement. To not build the runtime libraries, just temporarily move them out of the way so they are not configured or built. After you have the libc, etc. you can move them back and build them. -- Brian Ford Software Engineer Vital Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 ------ 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] |