boostrap failing

[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.
> 
> But bootstrap still does not complete without errors, have I missed
> something else?

What all did you copy?  The RTEMS autoconf package has the following
programs in .../bin:

opt/rtems/bin/autoconf
opt/rtems/bin/autoheader
opt/rtems/bin/autoreconf
opt/rtems/bin/autoscan
opt/rtems/bin/autoupdate
opt/rtems/bin/ifnames

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.

And make sure your PATH has the new tools first.

> Thanks!
> Christopher
> 
> This is the error bootstrap produces now:



> ./c
> ./scripts
> /usr/bin/m4: configure.in: 43: Bad regular expression
> `[[[\([[`""]]\)]]]': Unmatched ) or \)
> [configure.in:43[: error: [[[back quotes and double quotes should not
> be escaped in: [[$as_me:__oline__: [error: RPM CPU for ${target} is
> unknown]]]]]]]
> 
> ]/usr/bin/m4: configure.in: 43: ERROR: Recursion limit of 250
> exceeded, use -L<N> to change it
> ./scripts-ada
> ./tools/build
> autoheader: config.h.in is unchanged
> ./tools/cpu/generic
> ./tools/cpu
> ./tools/cpu/hppa1.1
> ./tools/cpu/sh
> ./tools/cpu/unix
> ./tools/updat
> 
> -----Original Message-----
> From: Joel Sherrill [mailto:joel.sherrill at OARcorp.com]
> Sent: Friday, January 11, 2002 1:01 PM
> To: Jowell, Chris {D177~Roswell}
> Cc: RTEMS Mailing List (RTEMS Mailing List)
> Subject: Re: boostrap failing
> 
> > Hi,
> >
> >
> >
> >             We have RTEMS 4.5.0 working fine on other workstations
> but can't get bootstrap to work on a new PC with SuSE 7.3.  I put part
> of the error message below.
> 
> >
> >
> >
> > I'm sure I've missed something simple but for the life of me I can't
> figure out what.
> >
> >
> >
> > I used the pre-built RTEMS 4.5.0 toolset Linux rpms (Including the
> m68k packages) and I've added the location of the toolset and the
> RTEMS_MAKFILE to my path
> 
> >
> >
> >
> > My autoconf is 2.52.44 and automake is 1.4p5-44 if that's
> interesting.
> 
> I think that's the problem.  SuSE has updated the autoconf package.
> Ralf
> and I talked about this a while back expecting this to occur
> eventually
> in various distributions.  The problem boils down to tools (including
> RTEMS) that use autoconf/automake can end up being dependent on
> particular versions of those tools.  In this case, RTEMS 4.5-X uses
> autoconf 2.13 and automake 1.4p5.  RTEMS snapshots past the Aug/Sept
> timeframe require autoconf 2.52 and automake 1.5.
> 
> Notice what I have on the main RTEMS development machine.
> 
> bash$ rpm -qa | grep auto
> autoconf-2.13-5
> automake-1.4-6
> autoconf-rtems-2.52-0
> automake-rtems-1.5-0
> 
> The rtems ones are in /opt/rtems.  When I work with snapshots, I
> bootstrap
> with those at the fron of my PATH.  Otherwise I use the ones shipped
> with
> the OS.
> 
> For now, you need to install autoconf 2.13 somewhere that does not
> conflict with the default version installed and use that to bootstrap.
> 
> --joel
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel at OARcorp.com                 On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
> Support Available                (256) 722-9985

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985