Building i386 on RED Hat

Joel Sherrill joel.sherrill at OARcorp.com
Sat Jul 29 00:08:25 UTC 2000


Two problems.

1.  bit_rtems is normally invoked "bit_rtems CPU BSP".  Otherwise you
build all BSPs with "bit_rtems CPU". Most people do not want to do this.

1a.  ts_386ex won't link because the i386 toolset does not have
soft-float
support.  The patch it depended on was against egcs and broke other
things.
I have worked on a solution to this and the next (snapshot) RPMs include
an attempt at soft-flot support and will at least link this BSP.

2.  The compilation stopped because there is a typo in
c/src/lib/libbsp/i386/i386ex/startup/linkcmds.

===================================================================
RCS file:
/usr1/CVS/rtems/c/src/lib/libbsp/i386/i386ex/startup/linkcmds,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- rtems/c/src/lib/libbsp/i386/i386ex/startup/linkcmds 1999/11/17
17:50:46     1.10
+++ rtems/c/src/lib/libbsp/i386/i386ex/startup/linkcmds 2000/06/14
13:08:41     1.11
@@ -9,7 +9,7 @@
  *  found in the file LICENSE in this distribution or at
  *  http://www.OARcorp.com/rtems/license.html.
  *
- *  $Id: linkcmds,v 1.10 1999/11/17 17:50:46 joel Exp $
+ *  $Id: linkcmds,v 1.11 2000/06/14 13:08:41 joel Exp $
  * 
  * Memory layout:
  *
@@ -112,7 +112,7 @@
        *(.dtors)
        LONG(0)
        __DTOR_END__ = .;
-       _rodata_start 5 . ;
+       _rodata_start = . ;
        *(.rodata)
        *(.gnu.linkonce.r*)
        _erodata = ALIGN( 0x10 ) ;


angelo at hunterlink.net.au wrote:
> 
> I am unable to get the bit_rtems script to work on a linux Red Hat 6.2 System
> 
> The first issue was the rtems directory which I had to change from rtems-4.5.0-beta3a
> to 4.5.0-beta3a
> 
> After changing the name of the directory I attempted
>     ./bit_rtems i386 i386-rtems
> 
> with a failure in a short period of time
> 
> I then executed
>     ./bit_rtems i386
> which when on building for about an hour and a half before it came up with this
> error:
> /opt/rtems/i386-rtems/bin/ld:../../../../../../i386ex/lib/linkcmds:115: parse
> er
> ror
> collect2: ld returned 1 exit status
> make[5]: *** [o-optimize/hello.exe] Error 1
> make[5]: Leaving directory `/opt/rtems/tools/build/i386-rtems/c/i386ex/tests/samples/hello'
> 
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory `/opt/rtems/tools/build/i386-rtems/c/i386ex/tests/samples'
> 
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/opt/rtems/tools/build/i386-rtems/c/i386ex/tests'
> 
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/opt/rtems/tools/build/i386-rtems/c/i386ex'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/opt/rtems/tools/build/i386-rtems/c'
> make: *** [all-recursive] Error 1
> 
> so I decided to execute the configuration script by copying the result of the
> script verbatim at the prompt, i.e.
> 
> ../4.5.0-beta3a/configure --target=i386-rtems --prefix=/opt/rtems --disable-hwapi
> --disable-multiprocessing
> --enable-cxx --enable-rdbg --disable-tests --enable-networking --enable-posix
> --enable-itron
> 
> which returned
> target architecture: i386.
> available BSPs: i386ex pc386 pc486 pc586 pc686 ts_386ex.
> 'make all' will build the following BSPs: i386ex pc386 pc486 pc586 pc686 ts_386ex.
> 
> other BSPs can be built with 'make RTEMS_BSP="bsp1 bsp2 ..."'
> 
> I then executed make all install and got the failure result that I received
> when I executed bit_rtems i386 (after
> about an hour of building)
> 
> angelo at hunterlink.net.au
> 
> There are those who seek knowledge for the sake of knowledge - that is
> CURIOSITY
> There are those who seek knowledge to be known by others - that is
> VANITY
> There are those who seek knowledge in order to serve - that is LOVE
>     Bernard of Clairvaux (1090 - 1153)
> 
> Home Page
> http://users.hunterlink.net.au/~maaaf/

-- 
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



More information about the users mailing list