[GSoC 2020: Daily Update]: Building EPICS with RTEMS5

Mritunjay Sharma mritunjaysharma394 at gmail.com
Mon Jul 13 19:03:48 UTC 2020

Hello everyone,

Good news is that my new system is fully functional now with
the development environment and I resumed the work today.

What I was trying to do was build EPICS 7 with RTEMS 5 by hand
for pc-386.

As advised in the thread, in my new system, I built pc-386 with
'--enable-networking' and used the epics 'playground' code of
Heinz to do 'make' in epics-base.

Few errors came which I was able to remove by installing a few dependencies.
However, the below-mentioned error is something that I haven't been able to
resolve for now:

`./posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or
 #include <rtems/bsd/bsd.h>
compilation terminated.
make[4]: ***
rtems_init.o] Error 1
make[4]: Leaving directory
make[3]: ***
install.RTEMS-pc386] Error 2
make[3]: Leaving directory
make[2]: ***
RTEMS.install] Error 2
make[2]: Leaving directory
make[1]: *** [../configure/RULES_DIRS:84: libcom.install] Error 2
make[1]: Leaving directory
make: *** [configure/RULES_DIRS:84: modules.install] Error 2

Please help me how to fix these and also guide on what should be my target
this week? What should be my next steps?


On Sat, Jul 11, 2020 at 8:16 PM Heinz Junkes <junkes at fhi-berlin.mpg.de>

> It's not my experience.
> I made my first attempts with RTEMS5 for a beatnik-board (MVME6100).
> For this I created the BSP like this:
>  cd build/b-beatnik
>     ../../rtems/configure --enable-maintainer-mode
> --prefix=$HOME/RTEMS/rtems-5 --target=powerpc-rtems5
> --enable-rtemsbsp="beatnik" --enable-posix --enable-cxx --enable-networking
> Through "--enable-networking" I was able to use the "old" rtems-bsdnet.
> With NTP, NFS etc. .
> At the moment I am in the process of using the "new" netbsd. For this I am
> no longer allowed to specify "--enable-networking" when building the bsp.
> That's what it says
> in the documentation and it works. The old NFS also works with it, it just
> lacks NTP (or PTP). And what I still miss very much is the support for the
> RTC and above all
> the libpci to access the vmebus.
> So I played a little with xilinx-zynq and beaglebone. Now I make the
> rtems_init at EPICS dependent on
> xilinx_zynq_zedboard/make/bsp.cfg:HAS_NETWORKING = no (new bsdlib)
> beatnik/make/bsp.cfg:HAS_NETWORKING = yes (old rtemsbsd code)
> Gruss Heinz
> On 11. Jul 2020, at 00:14, Joel Sherrill <joel at rtems.org> wrote:
> Wading in late but I thought I saw something that was contradictory:
> Build BSP with --enable-networking
> Code needs rtems-libbsd
> If the code needs rtems-libbsd, then you MUST build fill with
> --disable-networking.
> If EPICS code needs rtems-libbsd, that limits the number of BSPs that can
> be used but you need to always use libbsd.
> --joel
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200714/20dbf773/attachment.html>

More information about the devel mailing list