Installation query

Thu Aug 6 19:14:33 UTC 2015

Hi,

Thanks for the quick reply.
I tried the steps mentioned on the quickstart page. After downloading
RTEMS, when I try the bootstrap command, I get several warnings, which go
as follows.
.
.
.
Makefile.am:23: warning: source file 'timer/timer.c' is in a subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
Makefile.am:23: warning: source file 'timer/timerisr.c' is in a
subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
Makefile.am:23: warning: source file 'shmsupp/addrconv.c' is in a
subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
Makefile.am:23: warning: source file 'shmsupp/getcfg.c' is in a
subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
Makefile.am:23: warning: source file 'shmsupp/lock.c' is in a subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
Makefile.am:23: warning: source file 'shmsupp/mpisr.c' is in a subdirectory,
Makefile.am:23: but option 'subdir-objects' is disabled
./c/src/lib/libbsp/no_cpu
acinclude.m4 is unchanged
./c/src
./c/src/ada-tests
mptests/mp01/node1/Makefile.am:9: warning: source file
'../../../support/init.c' is in a subdirectory,
mptests/mp01/node1/Makefile.am:9: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the
'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding
output
automake: object file(s) will be placed in the top-level directory.
However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout
your
automake: project, to avoid future incompatibilities.
mptests/mp01/node2/Makefile.am:9: warning: source file
'../../../support/init.c' is in a subdirectory,
mptests/mp01/node2/Makefile.am:9: but option 'subdir-objects' is disabled
mptests/mp02/node1/Makefile.am:9: warning: source file
'../../../support/init.c' is in a subdirectory,
mptests/mp02/node1/Makefile.am:9: but option 'subdir-objects' is disabled
mptests/mp02/node2/Makefile.am:9: warning: source file
'../../../support/init.c' is in a subdirectory,
mptests/mp02/node2/Makefile.am:9: but option 'subdir-objects' is disabled
.
.
.

These warnings repeat themselves for a lot of source files in
subdirectories. I do not understand how to enable the subdir-objects
option. Also, at the very end I also get the following messages.
ada_user/Makefile.am: warning: Oops!
ada_user/Makefile.am:     It appears this file (or files included by it)
are triggering
ada_user/Makefile.am:     an undocumented, soon-to-be-removed automake hack.
ada_user/Makefile.am:     Future automake versions will no longer place in
the builddir
ada_user/Makefile.am:     (rather than in the srcdir) the generated '.info'
files that
ada_user/Makefile.am:     appear to be cleaned, by e.g. being listed in
CLEANFILES or
ada_user/Makefile.am:     DISTCLEANFILES.
ada_user/Makefile.am:     If you want your '.info' files to be placed in
the builddir
ada_user/Makefile.am:     rather than in the srcdir, you have to use the
shiny new
ada_user/Makefile.am:     'info-in-builddir' automake option.
bsp_howto/Makefile.am: warning: Oops!
bsp_howto/Makefile.am:     It appears this file (or files included by it)
are triggering
bsp_howto/Makefile.am:     an undocumented, soon-to-be-removed automake
hack.
bsp_howto/Makefile.am:     Future automake versions will no longer place in
the builddir
bsp_howto/Makefile.am:     (rather than in the srcdir) the generated
'.info' files that
bsp_howto/Makefile.am:     appear to be cleaned, by e.g. being listed in
CLEANFILES or
bsp_howto/Makefile.am:     DISTCLEANFILES.
bsp_howto/Makefile.am:     If you want your '.info' files to be placed in
the builddir
bsp_howto/Makefile.am:     rather than in the srcdir, you have to use the
shiny new
bsp_howto/Makefile.am:     'info-in-builddir' automake option.
.
.
.

Am I going wrong somewhere?

On Thu, Aug 6, 2015 at 4:05 AM, Sujay Raj <sujayraaj at gmail.com> wrote:

> Hi,
>
> 1. Your PC configuration is good, build time (especially for RSB) will be
> fast.
>
> 2. The RSB documentation (and most documentation for sis and pc386) work
> and following it would lead to successful build. All the steps you
> performed are okay ( you are on the right way )
>
> 3. Next step would be to try and run some examples on the gdb sis
> simulator.
> Have a look at the :
> https://devel.rtems.org/wiki/GSoC/GettingStarted
> https://devel.rtems.org/wiki/TBR/UserManual/Quick_Start
> and run some sample applications, modify some codes to get a feel.
>
> 4. About the platform you wish to use, it depends on what work you want to
> do with RTEMS. RTEMS supports a lot of Boards and hardwares.
>
> For example, I am working on the 'xilinx_zynq_a9_qemu'  bsp, on the arm
> arch. It supports networking through the new network stack from
> rtems-libbsd. rtems-libbsd also gives usb support ( though I have not
> worked on usb, but its in active development ).
>
> The simulator for sis doesn't support networking etc. So you need to take
> such things into consideration. I use QEMU for simulation as it gives a lot
> of options to make what I want to do, easier.
>
> Then there is the pc386 bsp for the i386 arch, it works fine with the both
> the old and new stacks, plus I somehow feel that using i386 is easier than
> using ARM, the available amount of documentation about using pc386 is the
> highest.
>
> There are other arch or bsp people might be interested in like the
> raspberry pi, but I don't have much idea about it, there might be better
> people to guide you about that if you intend to go in that direction.
>
> So, a possible direction for you :
>
> 1. Test some applications, maybe on sis or pc386 to have some
> understanding of RTEMS.
>
> 2. Decide on something you want to work on and then choose a suitable arch
> and bsp for it. ( This will depend on you experience, but once you decide
> the work, you can ask for suggestions. People are very helpful here).
> Have a look at :
> https://devel.rtems.org/wiki/Developer/OpenProjects
> and
> https://devel.rtems.org/wiki/Developer/SmallProjects
> for ideas on how you can contribute.
>
>
> Thanks and Regards,
> Sujay Raj
>
>
>
> On Thu, Aug 6, 2015 at 9:37 AM, Sarvesh Patkar <sarveshspatkar at gmail.com>
> wrote:
>
>> Hi all,
>>
>> I am a beginner. I am running Ubuntu 14.04 on Oracle VM VirtualBox on
>> Windows PC. My host PC has the following configuration. Processor= Core i5,
>> RAM=16GB, Hard disk size= 1TB.
>>
>> I wanted to know what platform should I use for learning and developing
>> RTEMS.
>>
>> Also, I installed RSB according to this link https://docs.rtems.org/rsb/ but
>> I am trying to figure out what platform to use.
>>
>>
>> I have roughly used the following commands to install RSB and download
>> RTEMS. I would like to know how to proceed further and whether I was
>> roughly on the right way.
>>
>> cd
>> mkdir -p development/rtems/src
>> cd development/rtems/src
>> sudo apt-get install git
>> git clone git://git.rtems.org/rtems-source-builder.git
>> cd rtems-source-builder
>> sudo apt-get install bison cvs g++ texinfo flex
>> sudo apt-get install build-essential vim zlib1g-dev libncurses5-dev
>> python-dev
>> source-builder/sb-check
>> cd rtems
>> ../source-builder/sb-set-builder --log=l-sparc.txt
>> --prefix=$HOME/development/rtems/4.11 4.11/rtems-sparc
>> $HOME/development/rtems/4.11/bin/sparc-rtems4.11-gcc -v
>> git clone git://git.rtems.org/rtems.git
>> cd rtems
>> export PATH=/development/rtems/4.11/bin:$PATH
>> ./bootstrap
>> cd ..
>> mkdir b-sis
>> cd b-sis
>> ../rtems/configure --target=sparc-rtems4.11 --enable-rtremsbsp=sis
>> --enable-tests=samples --disable-posix
>>
>> Thank you,
>>
>> Sarvesh Patkar
>>
>> _______________________________________________
>> users mailing list
>> users at rtems.org
>> http://lists.rtems.org/mailman/listinfo/users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20150806/31eea914/attachment-0002.html>