Re: Making configure.in so the good compiler is choose

[David Burg]

Hello,

I have check and unfortunately, it is still 2.13. The version have not
change. I have no explaination of this.

Best regards,

David Burg.
----- Original Message -----
From: "David Burg" <address@hidden>
To: <address@hidden>
Sent: Tuesday, June 19, 2001 5:56 PM
Subject: Re: Making configure.in so the good compiler is choose


> Hello,
>
> Thank for the help. I was using 2.13 before, I will check if this is still
> the same currently.
>
> Best regards,
>
> David Burg.
>
> ----- Original Message -----
> From: "Ralf Corsepius" <address@hidden>
> To: <address@hidden>
> Sent: Tuesday, June 19, 2001 5:28 PM
> Subject: Re: Making configure.in so the good compiler is choose
>
>
> > David Burg wrote:
> > >
> > > Hello,
> > >
> > > Well, two weeks ago all was fine. A simple
> > >
> > > ./configure --host=arm-linux --build=i686-pc-linux-gnu
> > >
> > > was at last working correctly.
> > Only if using autoconf > 2.13
> >
> > > As you can see, it choose the wrong compiler unless I force it. But I
> have
> > > check in cvs, the configure.in is not changed at all.
> > >
> > > Why does this computer hate me ??? I guess there is something that
> changes
> > > on my linux, I know I have updated from a Suse 7.1 to a Suse 7.2 but I
> don't
> > > understand what may have change...
> > So you probably have downgraded autoconf to 2.13.
> >
> > > Any clue ?
> >
> > You probably are suffering from one or more issues from this list:
> > * having downgraded autoconf
> > * having mixed up autoconf-2.13 and autoconf > 2.13
> > * having screwed up your $PATH and now don't have autoconf > 2.13 as
> > first autoconf in $PATH.
> >
> > Ralf
> >
>
>