[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

rtems-ss-20030128




Francesco Poletti wrote:
> 
> Hy,now have this error...
> 
> May be the Makefile.am of the shmdr directory broken?
> 
> Making all in shmdr
> gmake[4]: Entering directory
> `/home/poletti/buildmulti1/arm-rtems/c/arm_bare_bsp/lib/libbsp/shmdr'
> arm-rtems-gcc --pipe -B../../../../../lib/
> -B../../../../../arm_bare_bsp/lib/ -specs bsp_specs -qrtems
> -DPACKAGE_NAME=\"rtems-c-src-lib-libbsp\"
> -DPACKAGE_TARNAME=\"rtems-c-src-lib-libbsp\"
> -DPACKAGE_VERSION=\"ss-20030128\"
> -DPACKAGE_STRING=\"rtems-c-src-lib-libbsp\ ss-20030128\"
> -DPACKAGE_BUGREPORT=\"rtems-bugs at OARcorp.com\"         -mcpu=arm7tdmi
> -O2 -g -Wall  -o o-optimize/addlq.o -c
> ../../../../../../../rtems-ss-20030128/c/src/lib/libbsp/shmdr/addlq.c
> Assembler messages:
> FATAL: can't create o-optimize/addlq.o: Not a directory
> gmake[4]: *** [o-optimize/addlq.o] Error 2
> gmake[4]: Leaving directory
> `/home/poletti/buildmulti1/arm-rtems/c/arm_bare_bsp/lib/libbsp/shmdr'
> gmake[3]: *** [all-recursive] Error 1
> gmake[3]: Leaving directory
> `/home/poletti/buildmulti1/arm-rtems/c/arm_bare_bsp/lib/libbsp'
> gmake[2]: *** [all-recursive] Error 1
> gmake[2]: Leaving directory
> `/home/poletti/buildmulti1/arm-rtems/c/arm_bare_bsp'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory `/home/poletti/buildmulti1/arm-rtems/c'
> make: *** [all-recursive] Error 1

This usually indicates that o-optimize isn't being created.
Look at the dependencies on all-local and make sure $(ARCH) is first.

> Ralf Corsepius wrote:
> >
> > Am Fre, 2003-01-31 um 17.58 schrieb Joel Sherrill:
> > > Francesco Poletti wrote:
> > > >
> > > > Yes but my board have yet the shmsupp directory... :-((
> > > > My Makefile.am have shmsupp in the SUBDIRS list
> > > > and the configure.ac had the shmupp in the Makefile list...
> > > > I had run automake and autoconf.
> > > > Need I to run also aclocal?
> > The nominal sequence is
> >
> > aclocal -I <path-to-rtems-toplevel>/aclocal
> > automake
> > autoconf
> >
> > > Run rtems-XXX/bootstrap in your BSP directory.
> > Overkill.
> >
> > If integrating/adding a BSP you need to run bootstrap once inside of
> > c/src/lib/libbsp/<cpu>.
> >
> > Then configure a build-tree with maintainer-mode enabled (configure
> > --enable-maintainer-mode)
> 
> Ralf's right.  Once you have all the Makefile.am's in place and are
> tinkering with them, use --enable-maintainer-mode and things will get
> regenerated without you worrying about it.
> 
> > Automake then will take care about dependencies itself and will
> invoke
> > its underlaying components when needed.
> >
> > >   Never run the
> > > tools by hand.  It is too error prone.
> > What?
> 
> I used a poor choice of words.  I just meant that running bootstrap
> is easy and a single command.  It is not difficult or error prone
> to run the real autotool command sequence.  The only error that can
> happen is a human not doing the commands right.  Bootstrap eliminates
> that risk.
> 
> > <#:( )>
> > Boys, do yourselves a favor:
> > Read the fschking manuals: http://sources.redhat.com/autobook
> > and the RTEMS FAQ.
> > </#:( )>
> 
> Sorry guys.  I used a very poor choice of word.  I really believe in
> automake and autoconf and am glad that RTEMS is using it.
> 
> > Ralf
> 
> --joel