This message is VERY important. PLEASE read the whole thing --
it will save everyone a lot of time and a lot of FAQs.
Sections:
What, Why, How, Who, Where, When, and Installation
WHAT:
(1) automake has been replaced by three separate packages
aut
Brett Porter wrote:
>
> > No. The new path setting is only good for *called*
> > processes in the
> > same fork/exec chain. The parent shell's PATH is
> > not modified, so once
> > 'autoconf' finishes and you drop back into your
> > interactive shell, your
> > old PATH is back in effect.
> >
>
> No. The new path setting is only good for *called*
> processes in the
> same fork/exec chain. The parent shell's PATH is
> not modified, so once
> 'autoconf' finishes and you drop back into your
> interactive shell, your
> old PATH is back in effect.
>
Sorry, I must have misunderstood. The
Brett Porter wrote:
>
> I have a couple of questions regarding this (apologies
> if already covered - I'm on the digest and only got
> this message on announce).
>
> Let's see if I understand correctly:
> 1. you run autoconf
> 2. it sets the path based on a wrapper script
> 3. next execution goe
I have a couple of questions regarding this (apologies
if already covered - I'm on the digest and only got
this message on announce).
Let's see if I understand correctly:
1. you run autoconf
2. it sets the path based on a wrapper script
3. next execution goes to the desired one directly.
Doesn't
> "Corinna" == Corinna Vinschen <[EMAIL PROTECTED]> writes:
Corinna> This message is VERY important. PLEASE read the whole
Corinna> thing -- it will save everyone a lot of time and a lot of
Corinna> FAQs.
Thanks so much for taking the time to both implement the wrapper
scheme, a
This message is VERY important. PLEASE read the whole thing --
it will save everyone a lot of time and a lot of FAQs.
Sections:
What, Why, How, Who, Where, When, and Installation
WHAT:
(1) automake has been replaced by three separate packages
aut
7 matches
Mail list logo
