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] |
> If the toolset isn't 'generic' but for some specific PowerPC-variant, >using the specific '-mcpu=' etc. options for glibc is then also >possible, just as for 'libgcc.a', 'libiberty.a', 'libstdc++.a' etc. >while producing the extra libraries coming with GCC... Putting all >the needed options as defaults ('MULTILIB_DEFAULTS') for the produced >GCC in the configuration may then be motivated. Only the '-mbig' and >'-mcall-linux' are there (in 'gcc/config/rs6000/linux.h') as default. I need a generic tool since I build code for PPC variants, some with and some without a floating point unit. The above looks like it explains how to produce a gcc that doesn't have floating point, but I'm more concerned about producing *glibc* that doesn't have an floating point in it. I can't see how modifying the t-ppcgas file in gcc(since I'm using gas) can affect the code genereated when building glibc. I must be missing something here. -- Peter Barada Peter.Barada@motorola.com Wizard 781-852-2768 (direct) WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax) ------ 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] |