release branch patches, ... and m4 problem

[Jochen Kuepper]

Dear Jeff,

thank you very much for all the time you put into answering my questions.

Jeffrey A Law <law@hurl.cygnus.com> wrote:
:> 
:> I don't think it's really feasible to do this on a global scale all the time;
:> takes too much time.  Particularly as the development sources move further
:> and further away from the current release sources -- it gets harder and harder
:> to determine what patches will apply, whether or not they're correct for the
:> release (due to dependencies on other patches for example), etc.

Well, I take this for the answer to my initial 'problem'. It's not what  I wanted 
to hear, but definetely one of the answers I expected.
I do accept it, since I want to see egcs 1.0.2, ..., 1.1, 1.2, ... sometime.

:>   > The cvs sources (updated today) complain on compilation that I need to
:>   > provide GNU m4 > v1.1, cause it's using the system m4.
:>   > Shouldn't it find the gm4 that is in the path before the system m4 that's
:>   > later in the path ?
:> This is autoconf that's complaining.  I don't know how autoconf works, so
:> I can't really say with authority what the correct behavior of autoconf
:> should be in this case.

Will look into it.

 [
  Someone around who knows what to do ?
  ( I usually use automake and don't get into the autoconf stuff to much. )
 ]

Please keep on going to do that great job,
Jochen


-----------------------------------------------------------------------
  Jochen K"upper

  Heinrich-Heine-Universit"at D"usseldorf   jochen@uni-duesseldorf.de
  Institut f"ur Physikalische Chemie I
  Universit"atsstr. 1, Geb 26.43 Raum 02.29    phone ++49-211-8113681
  40225 D"usseldorf                            fax   ++49-211-8115195
  Germany             http://www-public.rz.uni-duesseldorf.de/~jochen
-----------------------------------------------------------------------