This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: CrossGCC FAQ update.


Michael Schwingen wrote:
> 
> On Thu, May 06, 1999 at 07:24:52PM +0000, Jonathan Larmour wrote:
> 
> [libiberty]
> > > > Do I have a choice ?
> >
> > No. It is required by gcc and others.
> 
> Hm - when compiling, or on the target?

Sorry, only when compiling. The target doesn't (necessarily) need it,
although it may be required if you are using more complex stuff like
libstdc++ on the target.

> > To reduce the number of multilibs, edit the appropriate file commencing with
> > "t-" in the relevant subdirectory of gcc/config. For example, the options
> > for m68k-elf are in "gcc/config/m68k/t-m68kelf". The macros to change are
> > MULTILIB_OPTIONS, MULTILIB_DIRNAMES, MULTILIB_MATCHES and
> > MULTILIB_EXCEPTIONS.
> 
> Ah, great - that *definitely* belongs in the FAQ, IMHO.

I should add that these options are documented in the GCC info files. The
above ones are under "Fragments->Target Fragment" in gcc.texi. It is also
worth looking at MULTILIB_DEFAULTS in "Target Macros->Driver" in tm.texi,
which I forgot to mention. With the example above, MULTILIB_DEFAULTS would
be defined in gcc/config/m68k/m68k-none.h (although this file is included
from the specific m68k files as it happens on m68k).

> > >  - how do I disable building all these other libraries I do not need, but
> > >    which cause compilation errors sometimes?
> >
> > The simplest answer is probably just to move them out of the way
> > temporarily. Even just renaming them will work, e.g. "mv libstdc++
> > libstdc++.foo"
> 
> That's what I did (and edit the toplevel Makefile, IIRC). However, it would
> be nice if I could simply tell configure that I want to build a 'small'
> compiler without the optional stuff - that would make it a lot easier do
> automatically build new compiler versions.

If you're using the "build from one tree" approach (as you should), you
shouldn't need to change the makefile, I believe. It should detect what is
and is not present.

But there's no explicit way to do it from the command-line. It would be
desirable, but would take a bit of effort. Volunteers to do it would be
welcome, of course :-).

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Want a free open source no-royalty RTOS?
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault
_______________________________________________
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
_______________________________________________
To remove yourself from the crossgcc list, send
mail to crossgcc-request@cygnus.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]