configure bug? / questions to gcc

[Jeffrey A Law]

  In message < 199804080653.IAA25129@keksy.mchp.siemens.de >you write:
  > Hi,
  > I have some questions:
  > 
  > 1. Why does egcs-980404 install libf2c into /usr/local/lib
  >    when doing a 'make cross;make install'? 
  >    There it overwrites the native version of it, which makes
  >    the native g77 worthless. I think it should go into
  >    /usr/local/<target-system>/lib.
A minor in the toplevel configure/build system; it needs to know
that when LANGUAGES is set (via make cross) that the fortran
libs shouldn't be built.

And, yes, libf2c has a few other problems with cross builds that
we're slowly, but surely addressing.  Among other things it
does belong in target-system/lib and it needs to obey the multilib
build rules.


  > 2. I usually make an obj directory an then a
  >    cd obj;
  >    <source-dir-of-egcs>/configure
  >    I realized, that configure changes <source-dir-of-egcs>/
  >    (I think i configured first cross compiler for a
  >     different target system, made it and after a
  >     rm -rf obj/* i configured for the native compiler.
  >     Then the compilation failed) After i reinstalled the
  >     source, it went o.k. I thought, that the trick with the
  >     obj-dir is, that you can have your sources mounted read-only.
  >     Isn't this correct?
Should be.  If it modified something in the obj tree we want to know.

There are a couple exceptions for generated files.

  > 3. I would like to do some hacking of gcc/g77. Is there some
  >    documentation about the compiler internals? How does it work?
  >    Which intermediate code? How is code-generaion done? What
  >    has the front end to provide, which file implements what?...
  >    How long did it take you to get an principal idea of the way it
  >    works?
The standard gcc manual has this information.  The use the emacs
info browser to look a the gcc.info files.

jeff