boostrap failing

[Jowell, Chris {D177~Roswell}]

Great!

	Installing the correct version of autoconf and automake solved my
problems.  But this leads me to another question... 
How can I have two versions of RTEMS coexisting peacefully on one system,
4.5.0 & 'current' for example.  I know I can specify the install directory
for RTEMS and I need to put the correct version of automake & autoconf in
the rtems/bin directory.  But what about the toolsets?

Thanks
Christopher

-----Original Message-----
From: Ralf Corsepius [mailto:corsepiu at faw.uni-ulm.de] 
Sent: Saturday, January 12, 2002 1:02 PM
To: Joel Sherrill
Cc: Jowell, Chris {D177~Roswell}; RTEMS Mailing List (RTEMS Mailing List)
Subject: Re: boostrap failing

Am Fre, 2002-01-11 um 21.13 schrieb Joel Sherrill:
> 
> 
> > "Jowell, Chris {D177~Roswell}" wrote:
> > 
> > OK I've copied the versions of autoconf and automake from SuSE 7.2
> > (which works... Still!) to /opt/rtems/bin on my 7.3 box which helped.
Nope, this can't help. autoconf and automake are non relocatible.

> > But bootstrap still does not complete without errors, have I missed
> > something else?
Yes, you need to have autoconf-2.13 and automake-1.4/automake-1.4_p5 for
rtems-4.5.x.

> What all did you copy? 

Forget about copying, this can't work. You need to build both,
autoconf-1.13 _and_ automake-1.4x with the same prefix from source.

I.e. If wanting to use rtems-4.5.x and wanting to install it to
/opt/rtems, I would recommend to build
autoconf-2.13
and
automake-1.4
from source, using --prefix=/opt/rtems


> It would be easy to not grabbed them all.
> 
> I think it would be safer to download the old autoconf version,
> configure
> it to be in /opt/rtems and do a make all install.  It builds and
> installs
> from source in seconds.
Right, this is __the__ solution.

> And make sure your PATH has the new tools first.
=> Set PATH=/opt/rtems/bin:$PATH if working with RTEMS-4.5.x

Ralf



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20020114/2a0857df/attachment-0001.html>