Build break

[Joel Sherrill]

R. D. Flowers, Chattanooga TN USA wrote:

How did you configure?  This doesn't look like I would
have expected for a cross build.

You should be configuring to run on like the pc386 BSP
using something like qemu to run it so you don't have
to deal with real hardware.

You appear to be building the very limited "POSIX"
port where we treat a UNIX machine as a port.
Setjmp is used to context switch.  This isn't a good
port to do most things with.

I would recommend using sparc/sis, powerpc/psim,
or i386/pc386 (on qemu) and just running on a simulator.
sis is pretty simple and included in the gdb RPMs.  It
can be built like this

mkdir b-sis
cd b-sis
../rtems-XXX/configure --target=sparc-rtems4.9 \
  --enable-rtemsbsp=sis --prefix=SOME_DIRECTORY \
  --enable-tests=samples
make

find . -name ticker.exe
sparc-rtems4.9-gdb PATH_TO/ticker.exe
(gdb) tar sim
(gdb) load
(gdb) run


> -------- Original Message --------
> Subject: Re: Status and build break and questions
> Date: Wed, 28 May 2008 11:13:46 -0500
> From: Joel Sherrill <joel.sherrill at oarcorp.com>
> To: base at chalice.us <base at chalice.us>
> CC: Eric Norum <norume at aps.anl.gov>
> References: <481FC42D.1080302 at chalice.us> <48206D75.9000400 at oarcorp.com>
> <483C68D9.8010600 at chalice.us>
>
> I have seen this on 64-bit machines.  Best to send this to the
> mailing list.
>
> R. D. Flowers, Chattanooga TN USA wrote:
>   
>> I scavenged ram, beefed up a Pentium III box ( just to 640MB ram ),
>> installed Fedora 9 on it, and then wrestled it into doing kde rather
>> than gnome, so now I guess I have a dev machine that will work for RTEMS.
>>
>> I did bootstrap, configure, which both seemed to run ok. Just did the
>> configure vanilla for now, and not in the source tree.
>>
>> I did a plain
>> sudo make
>> there. It did a lot, hopefull almost all, then errored out with:
>>
>>
>> gmake[5]: Entering directory `/home/rd0/rt48build/c/posix/cpukit/libfs'
>> Making all in src/nfsclient
>> gmake[6]: Entering directory
>> `/home/rd0/rt48build/c/posix/cpukit/libfs/src/nfsclient'
>> gcc --pipe -DHAVE_CONFIG_H   -I../../..
>> -I../../../../cpukit/../../../posix/lib/include  -Wall -fasm
>> -D_BSD_SOURCE -D_POSIX_C_SOURCE -O0 -g -MT src/dirutils_rel-dirutils.o
>> -MD -MP -MF src/.deps/dirutils_rel-dirutils.Tpo -c -o
>> src/dirutils_rel-dirutils.o `test -f 'src/dirutils.c' || echo
>> '../../../../../../../rtems/c/src/../../cpukit/libfs/src/nfsclient/'`src/dirutils.c
>> mv -f src/.deps/dirutils_rel-dirutils.Tpo src/.deps/dirutils_rel-dirutils.Po
>> gcc --pipe -Wall -fasm -D_BSD_SOURCE -D_POSIX_C_SOURCE -O0 -g -r  -o
>> dirutils.rel src/dirutils_rel-dirutils.o
>> /usr/bin/ld: cannot find -lgcc_s
>> collect2: ld returned 1 exit status
>> gmake[6]: *** [dirutils.rel] Error 1
>> gmake[6]: Leaving directory
>> `/home/rd0/rt48build/c/posix/cpukit/libfs/src/nfsclient'
>> gmake[5]: *** [all-recursive] Error 1
>> gmake[5]: Leaving directory `/home/rd0/rt48build/c/posix/cpukit/libfs'
>> gmake[4]: *** [all-recursive] Error 1
>> gmake[4]: Leaving directory `/home/rd0/rt48build/c/posix/cpukit'
>> gmake[3]: *** [all] Error 2
>> gmake[3]: Leaving directory `/home/rd0/rt48build/c/posix/cpukit'
>> gmake[2]: *** [all-recursive] Error 1
>> gmake[2]: Leaving directory `/home/rd0/rt48build/c/posix'
>> gmake[1]: *** [all-recursive] Error 1
>> gmake[1]: Leaving directory `/home/rd0/rt48build/c'
>> make: *** [all-recursive] Error 1
>> [rd0 at localhost rt48build]$
>>
>>
>>
>>
>> I don't understand what went wrong with this build of RTEMS 4.8.
>>
>>     
>
> Does anybody understand what likely went wrong here ?
>
>
> --
> rdflowers, gsoc 2008 student ( lwip integration, Nic Porting Assistant
> (Nipoa) )
>
>
>
>
>   


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