Baking a i386-rtems image

[Ralf Corsepius]

Martin_Doering at mn.man.de wrote:
> 
> Hello Listers!
> 
> I'm new to RTEMS and all the stuff around. I try it out, because I think
> of creating something like a small unix system on top of a bootable RTEMS
> kernel for i386 (i586). Something like these one floppy linux
> distributions - at first just for my own enjoyment.
> 
> I got the RTEMS beta compiled for to run under linux, but now I downloaded
> the four RPMs for to create a native i386 version. Doing this some few
> questions came up:
> 
> - I configured my system like:
> ./configure --target=i386 --enable-rtemsbsp=i386-rtems
> 

Three faults:
1. ./configure means to configure inside of the build tree. RTEMS
requires to be build in a separate build tree.
2. --target=i386-rtems
3. --enable-rtemsbsp=pc386

Correct procedure for you (Assuming using gnu-tar and bash):

tar xzvf rtems-<version>.tar.gz
export PATH=/opt/rtems/bin:$PATH
mkdir build
cd build
../rtems-<version>/configure --target=i386-rtems
--enable-rtemsbsp=pc386
make
make install

> So now I tried different combinations for the target and the rtemsbsp, but
> in all cases I got some errors. Can somebody give me as a totally newbie a
> tip?
Well, RTFM would have been appropriate :)

Please read the Getting Started and FAQ sections somewhere on
http://www.OARCorp.com.
 
> Another thing: if the documentation is rewritten somday, it would be fine
> to make more clear, that the build directory has to be not the one in the
> distribution, but to be on the same layer of the filesystem, as the
> untarred distribution is. This took me about 1,5 hours.
Which RTEMS version do you use. Recent versions have a check in the
toplevel configure script which should immediately stop and barf.
Didn't this happen for you? If not, we've got something to examine.

./configure --target=i386 --enable-rtemsbsp=i386-rtems
creating cache ./config.cache
checking for gmake... gmake
checking for RTEMS Version... ss-20000811
configure: error: ***
    Attempt to build inside of the source tree
    Please use a separate build directory, instead 

Isn't this explicit enough?

OTOH, I have to admit that the documentation is fairly verbose and
it's difficult to spot the important sections and Joel could
consider to put a very brief README.1st into the toplevel directory
and/or to merge the documentation into the source tree.

Ralf

-- 
Ralf Corsepius 
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
(FAW)
Helmholtzstr. 16, 89081 Ulm, Germany     Tel: +49/731/501-8690
mailto:corsepiu at faw.uni-ulm.de           FAX: +49/731/501-999  
http://www.faw.uni-ulm.de