problem building from CVS on FreeBSD

[Chuck Tuffli]

Ralf -

Thanks for the suggestion, but both 'gmake' and 'gmake RTEMS_BSP=pc386'
produce the same output as 'gmake all' (see below). Could there be
something that went wrong with the configure? Thanks!

[314] gmake
Making all in make
gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
Making all in custom
gmake[2]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make/custom'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make/custom'
gmake[2]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build'
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build'
[315] gmake RTEMS_BSP=pc386
Making all in make
gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
Making all in custom
gmake[2]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make/custom'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make/custom'
gmake[2]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build'
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build'

Ralf Corsepius wrote:
> On Sun, 2003-08-31 at 15:51, chuck_tuffli at agilent.com wrote:
>
>>I'm trying to build RTEMS from the CVS head and am running into some
>>pretty basic problems. The host system is an x86 running FreeBSD 4.7
>>with autoconf 2.57 and automake 1.7 from ports.
>>After running configure and 'gmake all', I get the output below. Any
>>ideas why I get the messages about "Nothing to be done"?
>
> Because, make descended into a directory and detected that there is
> nothing to do for it. This is normal, and there is nothing wrong with it
> (cf. below)
>
>
>>[161] AUTOCONF="autoconf257" AUTOHEADER="autoheader257"
>>AUTOM4TE="autom4te257" AUTOMAKE="automake17" ACLOCAL="aclocal17"
>>../rtems/configure --target=i386-rtems --enable-docs
>>--enable-rtemsbsp=pc386
>
>
>>[...}
>>configure: creating ./config.status
>>config.status: creating Makefile
>>
>>target architecture: i386.
>>available BSPs: pc386.
>>'gmake all' will build the following BSPs: pc386.
>>other BSPs can be built with 'gmake RTEMS_BSP="bsp1 bsp2 ..."'
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This is the message you seem to have missed (cf. below).
>
>
>>config.status: creating Makefile
>>config.status: creating make/Makefile
>>config.status: creating make/custom/Makefile
>>[162] gmake all
>>Making all in make
>>gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
>>Making all in custom
>>gmake[2]: Entering directory
>>`/usr/home/ctuffli/dev/rtems/build/make/custom'
>>gmake[2]: Nothing to be done for `all'.
>>gmake[2]: Leaving directory
>>`/usr/home/ctuffli/dev/rtems/build/make/custom'
>>gmake[2]: Entering directory `/usr/home/ctuffli/dev/rtems/build/make'
>>gmake[2]: Nothing to be done for `all-am'.
>>gmake[2]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
>>gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build/make'
>>gmake[1]: Entering directory `/usr/home/ctuffli/dev/rtems/build'
>>gmake[1]: Nothing to be done for `all-am'.
>>gmake[1]: Leaving directory `/usr/home/ctuffli/dev/rtems/build'
>
>
> Now, just enter "gmake" or gmake RTEMS_BSP=pc386
>
> But, attention: You have checked out the CVS trunk, which currently
> contains the current unstable development version of RTEMS.
> It basically should be buildable and functional, but things can be
> pretty volatile, can change rapidly and unexpectedly.
>
> For the stable version, which is far less volatile than CVS-trunk, you
> can check out the rtems-4-6-branch (cvs co -rrtems-4-6-branch).
>
> Ralf
>
>
>
>

-- 
Chuck Tuffli
Agilent Technologies