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

[Chris Johns]

On 12/7/20 12:46 am, Heinz Junkes wrote:
> 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. .

We call the stack in the rtems source tree the `legacy` stack.

> At the moment I am in the process of using the "new" netbsd. 

The new stack is called 'libbsd'.

I think it will help to use common terms.

> For this I am no
> longer allowed to specify "--enable-networking" when building the bsp. 

Correct.

> That's what it says in the documentation and it works.

Correct.

> The old NFS also works with it, it just lacks NTP (or PTP).

Yes the NFS client stack works with both networking stacks. I am looking at PTP
but I will not have anything in the near term.

> And what I still miss very much is the support for the RTC

Do you mean an RTC driver and chip support or do you mean NTP kernel support in
RTEMS?

> and above all the libpci to access the vmebus.

Do you mean libvme? Why use a PCI bus interface with the VME bus?

The libbsd stack has a generic bus interface.

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

Great. This will help. The rtems_waf repo has this code to detect the setting 
...

https://git.rtems.org/rtems_waf/tree/rtems.py#n355

>> On 11. Jul 2020, at 00:14, Joel Sherrill > > wrote:
>>
>> If the code needs rtems-libbsd, then you MUST build fill with
>> --disable-networking.

Building libbsd will detect if the legacy stack has been built during the
configure stage.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Chris Johns]

Could we please look at separate threads for these status posts, maybe one per
week or per topic or something else?

I do not think having mega-threads helps.

Thanks
Chris

On 12/7/20 4:04 am, Mritunjay Sharma wrote:
> 
> 
> On Sat, Jul 11, 2020 at 2:07 AM Gedare Bloom  <mailto:ged...@rtems.org>> wrote:
> 
> On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma
> mailto:mritunjaysharma...@gmail.com>> 
> wrote:
> >
> > Apologies for the delay in response,
> > It’s an important update that I want to give to my mentors that my 
> current
> development laptop showed some problems yesterday and which worsened 
> today.
> >
> > I have submitted my laptop for repair. The good thing is that I have the
> backup of the work done till day and I have arranged a spare laptop as 
> well
> which will be available tomorrow.
> >
> > Configuring and setting up my laptop for the development may take a 
> couple
> of days and so I will like to request you all to kindly pardon my 
> inactivity
> for the next 2 days.
> >
> 
> Meanwhile, you may also think about reading/writing some more
> documentation, or planning out your next steps.
> 
> 
> Yes, Gedare, I did exactly the same today and wrote this beginner-friendly
> tutorial to 
> introduce more beginners like me to RTEMS community. 
> The link to blog
> is: 
> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
> 
> The spare laptop is also arranged and almost configured. Only a few
> tweaks remaining. 
> I will publish more blogs tomorrow related to EPICS+RTEMS and QEMU. 
> 
> I will certainly request Heinz, Chris and You to help me decide what should be
> my next steps now and
> what should be the goal for the following week. 
> 
> Thanks
> Mritunjay
> 
> 
> > I hope to be back active on Monday with everything set up on the new 
> laptop.
> >
> > Thanks
> > Mritunjay
> >
> > Get Outlook for iOS
> > 
> > From: jan.som...@dlr.de <mailto:jan.som...@dlr.de>  <mailto:jan.som...@dlr.de>>
> > Sent: Thursday, July 9, 2020 12:43:30 PM
> > To: ged...@rtems.org <mailto:ged...@rtems.org>      <mailto:ged...@rtems.org>>; mritunjaysharma...@gmail.com
> <mailto:mritunjaysharma...@gmail.com>  <mailto:mritunjaysharma...@gmail.com>>
> > Cc: rtems-de...@rtems.org <mailto:rtems-de...@rtems.org>
> mailto:rtems-de...@rtems.org>>
> > Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >
>     >
> >
> > > -Original Message-
> > > From: devel [mailto:devel-boun...@rtems.org
> <mailto:devel-boun...@rtems.org>] On Behalf Of Gedare Bloom
> > > Sent: Wednesday, July 8, 2020 9:45 PM
> > > To: Mritunjay Sharma
> > > Cc: RTEMS Devel
> > > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> > >
> > > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
> > > mailto:mritunjaysharma...@gmail.com>> 
> wrote:
> > > >
> > > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with 
> Heinz's
> > > https://github.com/hjunkes/epicsBaseOwnPlayground
> > > > while switching to Branch "7". The previous errors are gone but I am
> facing
> > > the following error:
> > > >
> > > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
> file or
> > > directory
> > > >  #include 
> > > >           ^
> > >
> > > This error indicates it is looking for an installed rtems-libbsd. My
> > > guess is you need to build/install the rtems-libbsd to get this
> > > playground to work.
> > >
> >
> > I did not read everything in this thread, so maybe I misunderstand 
> something.
> > If you want to build rtems-libbsd for a pc-based BSP, please be aware of
> the following:
> > - It should build fine if you use the 5-freebsd-12 branch.
> > - With master branch is should build if you set the option 
> "dev_nic_e1000"
> to off in your buildset.ini. It should compile, but depending on your
> network adapter there might be problems to actually use the network 
> devices.
> >
> > Finishing a patchset for the master br

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

[Mritunjay Sharma]

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
directory
 #include 
  ^
compilation terminated.
make[4]: ***
[/home/mritunjay/development/EPICS/epics-playground/configure/RULES_BUILD:235:
rtems_init.o] Error 1
make[4]: Leaving directory
'/home/mritunjay/development/EPICS/epics-playground/modules/libcom/RTEMS/O.RTEMS-pc386'
make[3]: ***
[/home/mritunjay/development/EPICS/epics-playground/configure/RULES_ARCHS:58:
install.RTEMS-pc386] Error 2
make[3]: Leaving directory
'/home/mritunjay/development/EPICS/epics-playground/modules/libcom/RTEMS'
make[2]: ***
[/home/mritunjay/development/EPICS/epics-playground/configure/RULES_DIRS:84:
RTEMS.install] Error 2
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epics-playground/modules/libcom'
make[1]: *** [../configure/RULES_DIRS:84: libcom.install] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epics-playground/modules'
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?

Thanks
Mritunjay




On Sat, Jul 11, 2020 at 8:16 PM Heinz Junkes 
wrote:

> 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  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@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

On Sat, Jul 11, 2020 at 2:07 AM Gedare Bloom  wrote:

> On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma
>  wrote:
> >
> > Apologies for the delay in response,
> > It’s an important update that I want to give to my mentors that my
> current development laptop showed some problems yesterday and which
> worsened today.
> >
> > I have submitted my laptop for repair. The good thing is that I have the
> backup of the work done till day and I have arranged a spare laptop as well
> which will be available tomorrow.
> >
> > Configuring and setting up my laptop for the development may take a
> couple of days and so I will like to request you all to kindly pardon my
> inactivity for the next 2 days.
> >
>
> Meanwhile, you may also think about reading/writing some more
> documentation, or planning out your next steps.
>

Yes, Gedare, I did exactly the same today and wrote this beginner-friendly
tutorial to
introduce more beginners like me to RTEMS community.
The link to blog is:
https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902

The spare laptop is also arranged and almost configured. Only a few
tweaks remaining.
I will publish more blogs tomorrow related to EPICS+RTEMS and QEMU.

I will certainly request Heinz, Chris and You to help me decide what should
be my next steps now and
what should be the goal for the following week.

Thanks
Mritunjay

>
> > I hope to be back active on Monday with everything set up on the new
> laptop.
> >
> > Thanks
> > Mritunjay
> >
> > Get Outlook for iOS
> > 
> > From: jan.som...@dlr.de 
> > Sent: Thursday, July 9, 2020 12:43:30 PM
> > To: ged...@rtems.org ; mritunjaysharma...@gmail.com <
> mritunjaysharma...@gmail.com>
> > Cc: rtems-de...@rtems.org 
> > Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >
> >
> >
> > > -Original Message-----
> > > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare Bloom
> > > Sent: Wednesday, July 8, 2020 9:45 PM
> > > To: Mritunjay Sharma
> > > Cc: RTEMS Devel
> > > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> > >
> > > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
> > >  wrote:
> > > >
> > > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with
> Heinz's
> > > https://github.com/hjunkes/epicsBaseOwnPlayground
> > > > while switching to Branch "7". The previous errors are gone but I am
> facing
> > > the following error:
> > > >
> > > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
> file or
> > > directory
> > > >  #include 
> > > >   ^
> > >
> > > This error indicates it is looking for an installed rtems-libbsd. My
> > > guess is you need to build/install the rtems-libbsd to get this
> > > playground to work.
> > >
> >
> > I did not read everything in this thread, so maybe I misunderstand
> something.
> > If you want to build rtems-libbsd for a pc-based BSP, please be aware of
> the following:
> > - It should build fine if you use the 5-freebsd-12 branch.
> > - With master branch is should build if you set the option
> "dev_nic_e1000" to off in your buildset.ini. It should compile, but
> depending on your network adapter there might be problems to actually use
> the network devices.
> >
> > Finishing a patchset for the master branch to fix that is on my todo
> list, but I haven't come around to do it yet.
> >
> > > > compilation terminated.
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_BUILD:234: recipe for target 'rtems_init.o' failed
> > > > make[4]: *** [rtems_init.o] Error 1
> > > > make[4]: Leaving directory
> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > > libcom/RTEMS/O.RTEMS-pc386'
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed
> > > > make[3]: *** [install.RTEMS-pc386] Error 2
> > > > make[3]: Leaving directory
> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > > libcom/RTEMS'
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_DIRS:84: recipe for target 'RTEMS.install' 

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

[Joel Sherrill]

On Sat, Jul 11, 2020, 9:46 AM Heinz Junkes  wrote:

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

This is good to hear. Maybe it is in an ifdef in EPICS. Still not sure why
it would include that file though. It doesn't appear to be anywhere except
libbsd.

So the beatnik works with the new stack. That's good news. Do you happen to
know about the mvme3100 or any of the motorola_powerpc boards? It looks
like the drivers are in libbsd but I don't think anyone has reported them
working.

--joel


> Gruss Heinz
>
>
>
>
> On 11. Jul 2020, at 00:14, Joel Sherrill  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@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Heinz Junkes]

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  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@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Joel Sherrill]

On Fri, Jul 10, 2020 at 5:14 PM Joel Sherrill  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.
>

Including  means it can't be built with the old network
stack as best I can tell:

 find rtems rtems-libbsd/ tools/5/sparc-rtems5/include/ -name termios.h
rtems-libbsd/freebsd-org/include/termios.h
rtems-libbsd/freebsd-org/sys/sys/termios.h
tools/5/sparc-rtems5/include/machine/termios.h
tools/5/sparc-rtems5/include/termios.h

Can sys/termios.h be changed to ? That would allow EPICS to
compile with both TCPIP stacks.

>
> --joel
>
> On Fri, Jul 10, 2020 at 3:37 PM Gedare Bloom  wrote:
>
>> On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma
>>  wrote:
>> >
>> > Apologies for the delay in response,
>> > It’s an important update that I want to give to my mentors that my
>> current development laptop showed some problems yesterday and which
>> worsened today.
>> >
>> > I have submitted my laptop for repair. The good thing is that I have
>> the backup of the work done till day and I have arranged a spare laptop as
>> well which will be available tomorrow.
>> >
>> > Configuring and setting up my laptop for the development may take a
>> couple of days and so I will like to request you all to kindly pardon my
>> inactivity for the next 2 days.
>> >
>>
>> Meanwhile, you may also think about reading/writing some more
>> documentation, or planning out your next steps.
>>
>> > I hope to be back active on Monday with everything set up on the new
>> laptop.
>> >
>> > Thanks
>> > Mritunjay
>> >
>> > Get Outlook for iOS
>> > ____________
>> > From: jan.som...@dlr.de 
>> > Sent: Thursday, July 9, 2020 12:43:30 PM
>> > To: ged...@rtems.org ; mritunjaysharma...@gmail.com <
>> mritunjaysharma...@gmail.com>
>> > Cc: rtems-de...@rtems.org 
>> > Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>> >
>> >
>> >
>> > > -Original Message-
>> > > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare
>> Bloom
>> > > Sent: Wednesday, July 8, 2020 9:45 PM
>> > > To: Mritunjay Sharma
>> > > Cc: RTEMS Devel
>> > > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>> > >
>> > > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
>> > >  wrote:
>> > > >
>> > > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with
>> Heinz's
>> > > https://github.com/hjunkes/epicsBaseOwnPlayground
>> > > > while switching to Branch "7". The previous errors are gone but I
>> am facing
>> > > the following error:
>> > > >
>> > > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
>> file or
>> > > directory
>> > > >  #include 
>> > > >   ^
>> > >
>> > > This error indicates it is looking for an installed rtems-libbsd. My
>> > > guess is you need to build/install the rtems-libbsd to get this
>> > > playground to work.
>> > >
>> >
>> > I did not read everything in this thread, so maybe I misunderstand
>> something.
>> > If you want to build rtems-libbsd for a pc-based BSP, please be aware
>> of the following:
>> > - It should build fine if you use the 5-freebsd-12 branch.
>> > - With master branch is should build if you set the option
>> "dev_nic_e1000" to off in your buildset.ini. It should compile, but
>> depending on your network adapter there might be problems to actually use
>> the network devices.
>> >
>> > Finishing a patchset for the master branch to fix that is on my todo
>> list, but I haven't come around to do it yet.
>> >
>> > > > compilation terminated.
>> > > >
>> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
>> > > RULES_BUILD:234: recipe for target 'rtems_init.o' failed
>> > > > make[4]: *** [rtems_init.o] Error 1
>> > > > make[4]: Leaving directory
>> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPla

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

[Joel Sherrill]

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

On Fri, Jul 10, 2020 at 3:37 PM Gedare Bloom  wrote:

> On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma
>  wrote:
> >
> > Apologies for the delay in response,
> > It’s an important update that I want to give to my mentors that my
> current development laptop showed some problems yesterday and which
> worsened today.
> >
> > I have submitted my laptop for repair. The good thing is that I have the
> backup of the work done till day and I have arranged a spare laptop as well
> which will be available tomorrow.
> >
> > Configuring and setting up my laptop for the development may take a
> couple of days and so I will like to request you all to kindly pardon my
> inactivity for the next 2 days.
> >
>
> Meanwhile, you may also think about reading/writing some more
> documentation, or planning out your next steps.
>
> > I hope to be back active on Monday with everything set up on the new
> laptop.
> >
> > Thanks
> > Mritunjay
> >
> > Get Outlook for iOS
> > 
> > From: jan.som...@dlr.de 
> > Sent: Thursday, July 9, 2020 12:43:30 PM
> > To: ged...@rtems.org ; mritunjaysharma...@gmail.com <
> mritunjaysharma...@gmail.com>
> > Cc: rtems-de...@rtems.org 
> > Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >
> >
> >
> > > -Original Message-
> > > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare Bloom
> > > Sent: Wednesday, July 8, 2020 9:45 PM
> > > To: Mritunjay Sharma
> > > Cc: RTEMS Devel
> > > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> > >
> > > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
> > >  wrote:
> > > >
> > > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with
> Heinz's
> > > https://github.com/hjunkes/epicsBaseOwnPlayground
> > > > while switching to Branch "7". The previous errors are gone but I am
> facing
> > > the following error:
> > > >
> > > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
> file or
> > > directory
> > > >  #include 
> > > >   ^
> > >
> > > This error indicates it is looking for an installed rtems-libbsd. My
> > > guess is you need to build/install the rtems-libbsd to get this
> > > playground to work.
> > >
> >
> > I did not read everything in this thread, so maybe I misunderstand
> something.
> > If you want to build rtems-libbsd for a pc-based BSP, please be aware of
> the following:
> > - It should build fine if you use the 5-freebsd-12 branch.
> > - With master branch is should build if you set the option
> "dev_nic_e1000" to off in your buildset.ini. It should compile, but
> depending on your network adapter there might be problems to actually use
> the network devices.
> >
> > Finishing a patchset for the master branch to fix that is on my todo
> list, but I haven't come around to do it yet.
> >
> > > > compilation terminated.
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_BUILD:234: recipe for target 'rtems_init.o' failed
> > > > make[4]: *** [rtems_init.o] Error 1
> > > > make[4]: Leaving directory
> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > > libcom/RTEMS/O.RTEMS-pc386'
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed
> > > > make[3]: *** [install.RTEMS-pc386] Error 2
> > > > make[3]: Leaving directory
> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > > libcom/RTEMS'
> > > >
> > > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > > RULES_DIRS:84: recipe for target 'RTEMS.install' failed
> > > > make[2]: *** [RTEMS.install] Error 2
> > > > make[2]: Leaving directory
> > > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > > libcom'
> > > > ../configure/RULES_DIRS:84: reci

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

[Gedare Bloom]

On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma
 wrote:
>
> Apologies for the delay in response,
> It’s an important update that I want to give to my mentors that my current 
> development laptop showed some problems yesterday and which worsened today.
>
> I have submitted my laptop for repair. The good thing is that I have the 
> backup of the work done till day and I have arranged a spare laptop as well 
> which will be available tomorrow.
>
> Configuring and setting up my laptop for the development may take a couple of 
> days and so I will like to request you all to kindly pardon my inactivity for 
> the next 2 days.
>

Meanwhile, you may also think about reading/writing some more
documentation, or planning out your next steps.

> I hope to be back active on Monday with everything set up on the new laptop.
>
> Thanks
> Mritunjay
>
> Get Outlook for iOS
> 
> From: jan.som...@dlr.de 
> Sent: Thursday, July 9, 2020 12:43:30 PM
> To: ged...@rtems.org ; mritunjaysharma...@gmail.com 
> 
> Cc: rtems-de...@rtems.org 
> Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>
>
>
> > -Original Message-
> > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare Bloom
> > Sent: Wednesday, July 8, 2020 9:45 PM
> > To: Mritunjay Sharma
> > Cc: RTEMS Devel
> > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >
> > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
> >  wrote:
> > >
> > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's
> > https://github.com/hjunkes/epicsBaseOwnPlayground
> > > while switching to Branch "7". The previous errors are gone but I am 
> > > facing
> > the following error:
> > >
> > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file 
> > > or
> > directory
> > >  #include 
> > >   ^
> >
> > This error indicates it is looking for an installed rtems-libbsd. My
> > guess is you need to build/install the rtems-libbsd to get this
> > playground to work.
> >
>
> I did not read everything in this thread, so maybe I misunderstand something.
> If you want to build rtems-libbsd for a pc-based BSP, please be aware of the 
> following:
> - It should build fine if you use the 5-freebsd-12 branch.
> - With master branch is should build if you set the option "dev_nic_e1000" to 
> off in your buildset.ini. It should compile, but depending on your network 
> adapter there might be problems to actually use the network devices.
>
> Finishing a patchset for the master branch to fix that is on my todo list, 
> but I haven't come around to do it yet.
>
> > > compilation terminated.
> > >
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > RULES_BUILD:234: recipe for target 'rtems_init.o' failed
> > > make[4]: *** [rtems_init.o] Error 1
> > > make[4]: Leaving directory
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > libcom/RTEMS/O.RTEMS-pc386'
> > >
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed
> > > make[3]: *** [install.RTEMS-pc386] Error 2
> > > make[3]: Leaving directory
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > libcom/RTEMS'
> > >
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> > RULES_DIRS:84: recipe for target 'RTEMS.install' failed
> > > make[2]: *** [RTEMS.install] Error 2
> > > make[2]: Leaving directory
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> > libcom'
> > > ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
> > > make[1]: *** [libcom.install] Error 2
> > > make[1]: Leaving directory
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
> > > configure/RULES_DIRS:84: recipe for target 'modules.install' failed
> > > make: *** [modules.install] Error 2"
> > >
> > > Today's update is that I tried to fix the above error however I still 
> > > have not
> > been able to clear it.
> > > If anyone has idea, please do tell what can be done.
> > >
> > > Thanks
> > > Mritunjay
> > >
> > > On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma
> >  wrote:
> > >>
> > >>
> > >>
> > >> ___

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

[Mritunjay Sharma]

Apologies for the delay in response,
It’s an important update that I want to give to my mentors that my current 
development laptop showed some problems yesterday and which worsened today.

I have submitted my laptop for repair. The good thing is that I have the backup 
of the work done till day and I have arranged a spare laptop as well which will 
be available tomorrow.

Configuring and setting up my laptop for the development may take a couple of 
days and so I will like to request you all to kindly pardon my inactivity for 
the next 2 days.

I hope to be back active on Monday with everything set up on the new laptop.

Thanks
Mritunjay

Get Outlook for iOS<https://aka.ms/o0ukef>

From: jan.som...@dlr.de 
Sent: Thursday, July 9, 2020 12:43:30 PM
To: ged...@rtems.org ; mritunjaysharma...@gmail.com 

Cc: rtems-de...@rtems.org 
Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5



> -Original Message-
> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare Bloom
> Sent: Wednesday, July 8, 2020 9:45 PM
> To: Mritunjay Sharma
> Cc: RTEMS Devel
> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>
> On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
>  wrote:
> >
> > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's
> https://github.com/hjunkes/epicsBaseOwnPlayground
> > while switching to Branch "7". The previous errors are gone but I am facing
> the following error:
> >
> > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or
> directory
> >  #include 
> >   ^
>
> This error indicates it is looking for an installed rtems-libbsd. My
> guess is you need to build/install the rtems-libbsd to get this
> playground to work.
>

I did not read everything in this thread, so maybe I misunderstand something.
If you want to build rtems-libbsd for a pc-based BSP, please be aware of the 
following:
- It should build fine if you use the 5-freebsd-12 branch.
- With master branch is should build if you set the option "dev_nic_e1000" to 
off in your buildset.ini. It should compile, but depending on your network 
adapter there might be problems to actually use the network devices.

Finishing a patchset for the master branch to fix that is on my todo list, but 
I haven't come around to do it yet.

> > compilation terminated.
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_BUILD:234: recipe for target 'rtems_init.o' failed
> > make[4]: *** [rtems_init.o] Error 1
> > make[4]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom/RTEMS/O.RTEMS-pc386'
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed
> > make[3]: *** [install.RTEMS-pc386] Error 2
> > make[3]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom/RTEMS'
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_DIRS:84: recipe for target 'RTEMS.install' failed
> > make[2]: *** [RTEMS.install] Error 2
> > make[2]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom'
> > ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
> > make[1]: *** [libcom.install] Error 2
> > make[1]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
> > configure/RULES_DIRS:84: recipe for target 'modules.install' failed
> > make: *** [modules.install] Error 2"
> >
> > Today's update is that I tried to fix the above error however I still have 
> > not
> been able to clear it.
> > If anyone has idea, please do tell what can be done.
> >
> > Thanks
> > Mritunjay
> >
> > On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma
>  wrote:
> >>
> >>
> >>
> >> 
> >> From: Heinz Junkes 
> >> Sent: Wednesday, July 8, 2020 1:05 AM
> >> To: Mritunjay Sharma
> >> Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
> >> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >>
> >> I’m away from my keyboard. If you use the epics Adaption to rtems from
> my github “playground?” and bsp’s with —enable-networks should compile.
> >> Heinz
> >>
> >> FHI, Heinz Junkes
> >>
> >> Thank you Heinz, I was doing the same. I went to your GitHub and am
> experimenting with "playground" right now.
> >>
> >> Than

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

[Jan.Sommer]

> -Original Message-
> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Gedare Bloom
> Sent: Wednesday, July 8, 2020 9:45 PM
> To: Mritunjay Sharma
> Cc: RTEMS Devel
> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> 
> On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
>  wrote:
> >
> > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's
> https://github.com/hjunkes/epicsBaseOwnPlayground
> > while switching to Branch "7". The previous errors are gone but I am facing
> the following error:
> >
> > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or
> directory
> >  #include 
> >   ^
> 
> This error indicates it is looking for an installed rtems-libbsd. My
> guess is you need to build/install the rtems-libbsd to get this
> playground to work.
> 

I did not read everything in this thread, so maybe I misunderstand something.
If you want to build rtems-libbsd for a pc-based BSP, please be aware of the 
following:
- It should build fine if you use the 5-freebsd-12 branch.
- With master branch is should build if you set the option "dev_nic_e1000" to 
off in your buildset.ini. It should compile, but depending on your network 
adapter there might be problems to actually use the network devices.

Finishing a patchset for the master branch to fix that is on my todo list, but 
I haven't come around to do it yet.

> > compilation terminated.
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_BUILD:234: recipe for target 'rtems_init.o' failed
> > make[4]: *** [rtems_init.o] Error 1
> > make[4]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom/RTEMS/O.RTEMS-pc386'
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed
> > make[3]: *** [install.RTEMS-pc386] Error 2
> > make[3]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom/RTEMS'
> >
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/
> RULES_DIRS:84: recipe for target 'RTEMS.install' failed
> > make[2]: *** [RTEMS.install] Error 2
> > make[2]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/
> libcom'
> > ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
> > make[1]: *** [libcom.install] Error 2
> > make[1]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
> > configure/RULES_DIRS:84: recipe for target 'modules.install' failed
> > make: *** [modules.install] Error 2"
> >
> > Today's update is that I tried to fix the above error however I still have 
> > not
> been able to clear it.
> > If anyone has idea, please do tell what can be done.
> >
> > Thanks
> > Mritunjay
> >
> > On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma
>  wrote:
> >>
> >>
> >>
> >> 
> >> From: Heinz Junkes 
> >> Sent: Wednesday, July 8, 2020 1:05 AM
> >> To: Mritunjay Sharma
> >> Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
> >> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >>
> >> I’m away from my keyboard. If you use the epics Adaption to rtems from
> my github “playground?” and bsp’s with —enable-networks should compile.
> >> Heinz
> >>
> >> FHI, Heinz Junkes
> >>
> >> Thank you Heinz, I was doing the same. I went to your GitHub and am
> experimenting with "playground" right now.
> >>
> >> Thanks,
> >> Mritunjay
> >>
> >> On 7. Jul 2020, at 18:14, Mritunjay Sharma
>  wrote:
> >>
> >> 
> >> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
> >> Everything worked fine while building the pc-386 with  RTEMS5.
> >>
> >> After this when I entered epics-base and made the following change:
> >>
> >> epics-base/os/CONFIG_SITE.Common.RTEMS
> >> RTEMS_VERSION = 5
> >> RTEMS_BASE =
> /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
> >>
> >> As an experiment, I ran the make and as expected got the following error
> >>
> >> Error:
> >>
> >> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include 
> >> -
> c ../rtems_init.c
> >> ../rtems_init.c:21:10: fatal error: sys/ter

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

[Heinz Junkes]

Sorry for the long delay.

Yes, this Epics version still uses the rtems-libbsd. 
The bsp must be built with --enable-network.

I'm trying to create an Epics version over the weekend that recognizes from 
the configuration which libbsd version should be used.


Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.



> On 8. Jul 2020, at 21:44, Gedare Bloom  wrote:
> 
> On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
>  wrote:
>> 
>> [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's 
>> https://github.com/hjunkes/epicsBaseOwnPlayground
>> while switching to Branch "7". The previous errors are gone but I am facing 
>> the following error:
>> 
>> "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or 
>> directory
>> #include 
>>  ^
> 
> This error indicates it is looking for an installed rtems-libbsd. My
> guess is you need to build/install the rtems-libbsd to get this
> playground to work.
> 
>> compilation terminated.
>> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_BUILD:234:
>>  recipe for target 'rtems_init.o' failed
>> make[4]: *** [rtems_init.o] Error 1
>> make[4]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS/O.RTEMS-pc386'
>> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_ARCHS:58:
>>  recipe for target 'install.RTEMS-pc386' failed
>> make[3]: *** [install.RTEMS-pc386] Error 2
>> make[3]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS'
>> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_DIRS:84:
>>  recipe for target 'RTEMS.install' failed
>> make[2]: *** [RTEMS.install] Error 2
>> make[2]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom'
>> ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
>> make[1]: *** [libcom.install] Error 2
>> make[1]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
>> configure/RULES_DIRS:84: recipe for target 'modules.install' failed
>> make: *** [modules.install] Error 2"
>> 
>> Today's update is that I tried to fix the above error however I still have 
>> not been able to clear it.
>> If anyone has idea, please do tell what can be done.
>> 
>> Thanks
>> Mritunjay
>> 
>> On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma 
>>  wrote:
>>> 
>>> 
>>> 
>>> 
>>> From: Heinz Junkes 
>>> Sent: Wednesday, July 8, 2020 1:05 AM
>>> To: Mritunjay Sharma
>>> Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
>>> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>>> 
>>> I’m away from my keyboard. If you use the epics Adaption to rtems from my 
>>> github “playground?” and bsp’s with —enable-networks should compile.
>>> Heinz
>>> 
>>> FHI, Heinz Junkes
>>> 
>>> Thank you Heinz, I was doing the same. I went to your GitHub and am 
>>> experimenting with "playground" right now.
>>> 
>>> Thanks,
>>> Mritunjay
>>> 
>>> On 7. Jul 2020, at 18:14, Mritunjay Sharma  
>>> wrote:
>>> 
>>> 
>>> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
>>> Everything worked fine while building the pc-386 with  RTEMS5.
>>> 
>>> After this when I entered epics-base and made the following change:
>>> 
>>> epics-base/os/CONFIG_SITE.Common.RTEMS
>>> RTEMS_VERSION = 5
>>> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
>>> 
>>> As an experiment, I ran the make and as expected got the following error
>>> 
>>> Error:
>>> 
>>> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include  
>>>-c ../rtems_init.c
>>> ../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory
>>> #include 
>>>  ^~~
>>> compilation terminated.
>>> ../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o' 
>>> failed
>>> make[4]: *** [rtems_init.o] Error 1
>>> make[4]: Leaving directory 
>>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
>>> ../../../configure/RULES_ARCHS:58: recipe for target 'in

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

[Gedare Bloom]

On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma
 wrote:
>
> [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's 
> https://github.com/hjunkes/epicsBaseOwnPlayground
> while switching to Branch "7". The previous errors are gone but I am facing 
> the following error:
>
> "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or 
> directory
>  #include 
>   ^

This error indicates it is looking for an installed rtems-libbsd. My
guess is you need to build/install the rtems-libbsd to get this
playground to work.

> compilation terminated.
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_BUILD:234:
>  recipe for target 'rtems_init.o' failed
> make[4]: *** [rtems_init.o] Error 1
> make[4]: Leaving directory 
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS/O.RTEMS-pc386'
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_ARCHS:58:
>  recipe for target 'install.RTEMS-pc386' failed
> make[3]: *** [install.RTEMS-pc386] Error 2
> make[3]: Leaving directory 
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS'
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_DIRS:84:
>  recipe for target 'RTEMS.install' failed
> make[2]: *** [RTEMS.install] Error 2
> make[2]: Leaving directory 
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom'
> ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
> make[1]: *** [libcom.install] Error 2
> make[1]: Leaving directory 
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
> configure/RULES_DIRS:84: recipe for target 'modules.install' failed
> make: *** [modules.install] Error 2"
>
> Today's update is that I tried to fix the above error however I still have 
> not been able to clear it.
> If anyone has idea, please do tell what can be done.
>
> Thanks
> Mritunjay
>
> On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma 
>  wrote:
>>
>>
>>
>> ________
>> From: Heinz Junkes 
>> Sent: Wednesday, July 8, 2020 1:05 AM
>> To: Mritunjay Sharma
>> Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
>> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>>
>> I’m away from my keyboard. If you use the epics Adaption to rtems from my 
>> github “playground?” and bsp’s with —enable-networks should compile.
>> Heinz
>>
>> FHI, Heinz Junkes
>>
>> Thank you Heinz, I was doing the same. I went to your GitHub and am 
>> experimenting with "playground" right now.
>>
>> Thanks,
>> Mritunjay
>>
>> On 7. Jul 2020, at 18:14, Mritunjay Sharma  
>> wrote:
>>
>> 
>> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
>> Everything worked fine while building the pc-386 with  RTEMS5.
>>
>> After this when I entered epics-base and made the following change:
>>
>> epics-base/os/CONFIG_SITE.Common.RTEMS
>> RTEMS_VERSION = 5
>> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
>>
>> As an experiment, I ran the make and as expected got the following error
>>
>> Error:
>>
>> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include   
>>   -c ../rtems_init.c
>> ../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory
>>  #include 
>>   ^~~
>> compilation terminated.
>> ../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o' 
>> failed
>> make[4]: *** [rtems_init.o] Error 1
>> make[4]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
>> ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' 
>> failed
>> make[3]: *** [install.RTEMS-pc386] Error 2
>> make[3]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS'
>> ../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed
>> make[2]: *** [RTEMS.install] Error 2
>> make[2]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
>> ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
>> make[1]: *** [libcom.install] Error 2
>> make[1]: Leaving directory 
>> '/home/mritunjay/development/EPICS/epics-base/modules'
>> configure/RULES_DIRS:85: recipe for target 'modules.install' failed
>> make: *** [modules.install] Error 2
>> ```
>>
>> I am tr

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

[Mritunjay Sharma]

[Another Update]: I just commented the part of the codes that were causing
the errors just as an experiment and
ultimately got the following errors:

```86-rtems5/bin/ld: cannot find -lbsd
collect2: error: ld returned 1 exit status
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_BUILD:206:
recipe for target 'libComTestHarness' failed
make[4]: *** [libComTestHarness] Error 1
make[4]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/test/O.RTEMS-pc386'
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_ARCHS:58:
recipe for target 'install.RTEMS-pc386' failed
make[3]: *** [install.RTEMS-pc386] Error 2
make[3]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/test'
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_DIRS:84:
recipe for target 'test.install' failed
make[2]: *** [test.install] Error 2
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom'
../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
make[1]: *** [libcom.install] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
configure/RULES_DIRS:84: recipe for target 'modules.install' failed
make: *** [modules.install] Error 2```


This is what change i did:

```diff --git a/modules/libcom/RTEMS/posix/rtems_config.c
b/modules/libcom/RTEMS/posix/rtems_config.c
index b02c94a6b..ce1390cdc 100644
--- a/modules/libcom/RTEMS/posix/rtems_config.c
+++ b/modules/libcom/RTEMS/posix/rtems_config.c
@@ -89,7 +89,7 @@ extern void *POSIX_Init(void *argument);

 //#define RTEMS_BSD_CONFIG_SERVICE_TELNETD

-#include 
+//#include 

 #define RTEMS_PCI_CONFIG_LIB
 #define CONFIGURE_PCI_LIB PCI_LIB_AUTO
diff --git a/modules/libcom/RTEMS/posix/rtems_init.c
b/modules/libcom/RTEMS/posix/rtems_init.c
index efd0b4518..90faccf78 100644
--- a/modules/libcom/RTEMS/posix/rtems_init.c
+++ b/modules/libcom/RTEMS/posix/rtems_init.c
@@ -35,8 +35,8 @@
 #include 
 #include 
 #include 
-#include 
-#include 
+//#include 
+//#include 
 #include 
 #include 
 ```
Hope it can help with debugging errors.
Thanks,
Mritunjay

On Thu, Jul 9, 2020 at 12:03 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's
> https://github.com/hjunkes/epicsBaseOwnPlayground
> while switching to Branch "7". The previous errors are gone but I am
> facing the following error:
>
> "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file
> or directory
>  #include 
>   ^
> compilation terminated.
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_BUILD:234:
> recipe for target 'rtems_init.o' failed
> make[4]: *** [rtems_init.o] Error 1
> make[4]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS/O.RTEMS-pc386'
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_ARCHS:58:
> recipe for target 'install.RTEMS-pc386' failed
> make[3]: *** [install.RTEMS-pc386] Error 2
> make[3]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS'
> /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_DIRS:84:
> recipe for target 'RTEMS.install' failed
> make[2]: *** [RTEMS.install] Error 2
> make[2]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom'
> ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
> make[1]: *** [libcom.install] Error 2
> make[1]: Leaving directory
> '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
> configure/RULES_DIRS:84: recipe for target 'modules.install' failed
> make: *** [modules.install] Error 2"
>
> Today's update is that I tried to fix the above error however I still have
> not been able to clear it.
> If anyone has idea, please do tell what can be done.
>
> Thanks
> Mritunjay
>
> On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>>
>>
>> ------
>> *From:* Heinz Junkes 
>> *Sent:* Wednesday, July 8, 2020 1:05 AM
>> *To:* Mritunjay Sharma
>> *Cc:* Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
>> *Subject:* Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>>
>> I’m away from my keyboard. If you use the epics Adaption to rtems from my
>> github “playground?” and bsp’s with —enable-networks should compile.
>> Heinz
>>
>> FHI, Heinz Junkes
>>
>> Thank you Heinz, I was doing the same. I went to your GitHub and am
>> experimenting with "playgr

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

[Mritunjay Sharma]

[UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's
https://github.com/hjunkes/epicsBaseOwnPlayground
while switching to Branch "7". The previous errors are gone but I am facing
the following error:

"../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or
directory
 #include 
  ^
compilation terminated.
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_BUILD:234:
recipe for target 'rtems_init.o' failed
make[4]: *** [rtems_init.o] Error 1
make[4]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS/O.RTEMS-pc386'
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_ARCHS:58:
recipe for target 'install.RTEMS-pc386' failed
make[3]: *** [install.RTEMS-pc386] Error 2
make[3]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom/RTEMS'
/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/RULES_DIRS:84:
recipe for target 'RTEMS.install' failed
make[2]: *** [RTEMS.install] Error 2
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/libcom'
../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed
make[1]: *** [libcom.install] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'
configure/RULES_DIRS:84: recipe for target 'modules.install' failed
make: *** [modules.install] Error 2"

Today's update is that I tried to fix the above error however I still have
not been able to clear it.
If anyone has idea, please do tell what can be done.

Thanks
Mritunjay

On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> --
> *From:* Heinz Junkes 
> *Sent:* Wednesday, July 8, 2020 1:05 AM
> *To:* Mritunjay Sharma
> *Cc:* Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
> *Subject:* Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>
> I’m away from my keyboard. If you use the epics Adaption to rtems from my
> github “playground?” and bsp’s with —enable-networks should compile.
> Heinz
>
> FHI, Heinz Junkes
>
> Thank you Heinz, I was doing the same. I went to your GitHub and am
> experimenting with "playground" right now.
>
> Thanks,
> Mritunjay
>
> On 7. Jul 2020, at 18:14, Mritunjay Sharma 
> wrote:
>
> 
> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
> Everything worked fine while building the pc-386 with  RTEMS5.
>
> After this when I entered epics-base and made the following change:
>
> epics-base/os/CONFIG_SITE.Common.RTEMS
> RTEMS_VERSION = 5
> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
>
> As an experiment, I ran the make and as expected got the following error
>
> Error:
>
> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include
> -c ../rtems_init.c
> ../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or
> directory
>  #include 
>   ^~~
> compilation terminated.
> ../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o'
> failed
> make[4]: *** [rtems_init.o] Error 1
> make[4]: Leaving directory
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
> ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386'
> failed
> make[3]: *** [install.RTEMS-pc386] Error 2
> make[3]: Leaving directory
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS'
> ../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed
> make[2]: *** [RTEMS.install] Error 2
> make[2]: Leaving directory
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
> ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
> make[1]: *** [libcom.install] Error 2
> make[1]: Leaving directory
> '/home/mritunjay/development/EPICS/epics-base/modules'
> configure/RULES_DIRS:85: recipe for target 'modules.install' failed
> make: *** [modules.install] Error 2
> ```
>
> I am trying to figure out the error and making the changes in code to
> debug it.
> However, I will appreciate if Heinz and everyone else can help me a
> little, if they have an
> idea of this error.
>
> Thanks
> Mritunjay
>
> On Tue, Jul 7, 2020 at 7:30 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>>
>>
>> On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom  wrote:
>>
>>> On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill  wrote:
>>> >
>>> >
>>> >
>>> > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:
>>> >>

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

[Mritunjay Sharma]

From: Heinz Junkes 
Sent: Wednesday, July 8, 2020 1:05 AM
To: Mritunjay Sharma
Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel
Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

I’m away from my keyboard. If you use the epics Adaption to rtems from my 
github “playground?” and bsp’s with —enable-networks should compile.
Heinz

FHI, Heinz Junkes

Thank you Heinz, I was doing the same. I went to your GitHub and am 
experimenting with "playground" right now.

Thanks,
Mritunjay

On 7. Jul 2020, at 18:14, Mritunjay Sharma  wrote:


[UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
Everything worked fine while building the pc-386 with  RTEMS5.

After this when I entered epics-base and made the following change:

epics-base/os/CONFIG_SITE.Common.RTEMS
RTEMS_VERSION = 5
RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)

As an experiment, I ran the make and as expected got the following error

Error:

```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include  
   -c ../rtems_init.c
../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory
 #include 
  ^~~
compilation terminated.
../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o' failed
make[4]: *** [rtems_init.o] Error 1
make[4]: Leaving directory 
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' 
failed
make[3]: *** [install.RTEMS-pc386] Error 2
make[3]: Leaving directory 
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS'
../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed
make[2]: *** [RTEMS.install] Error 2
make[2]: Leaving directory 
'/home/mritunjay/development/EPICS/epics-base/modules/libcom'
../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
make[1]: *** [libcom.install] Error 2
make[1]: Leaving directory 
'/home/mritunjay/development/EPICS/epics-base/modules'
configure/RULES_DIRS:85: recipe for target 'modules.install' failed
make: *** [modules.install] Error 2
```

I am trying to figure out the error and making the changes in code to debug it.
However, I will appreciate if Heinz and everyone else can help me a little, if 
they have an
idea of this error.

Thanks
Mritunjay

On Tue, Jul 7, 2020 at 7:30 PM Mritunjay Sharma 
mailto:mritunjaysharma...@gmail.com>> wrote:


On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom 
mailto:ged...@rtems.org>> wrote:
On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill 
mailto:j...@rtems.org>> wrote:
>
>
>
> On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom 
> mailto:ged...@rtems.org>> wrote:
>>
>> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
>> mailto:mritunjaysharma...@gmail.com>> wrote:
>> >
>> > Hello everyone,
>> >
>> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
>> > If there are issues in making a buildset for 4.10
>> > then should I build EPICS with RTEMS 5 by hand first and note
>> > down the process and then proceed to make the buildset for it?
>> >
>>
>> Yes.
>
>
> +1
>
> And by 5, we definitely mean the 5 branch for all rtems repo and the 
> similarly named one for libbsd.

Excellent point. We want to add support for easy build (and eventually
test) of EPICS+RTEMS starting with 5.1 and moving forward, which means
also doing it for RTEMS 6, Mritunjay.

Sounds good, I have begun building it hand by today for RTEMS 5 branch and 
later on continue the
same for RTEMS6

Thank you so much Gedare and Joel.
Mritunjay
>>
>>
>> > Please suggest for the future steps.
>> >
>> > Thanks
>> > Mritunjay
>> >
>> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill 
>> > mailto:j...@rtems.org>> wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns 
>> >> mailto:chr...@rtems.org>> wrote:
>> >>>
>> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>> >>> > Thank you, this is exactly where I was unsure.
>> >>> > @Chris: Can you give a recommendation here?
>> >>> > Danke Heinz
>> >>> > --
>> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>> >>> > Faradayweg 4-6| VC: 
>> >>> > 102220181...@bjn.vc<mailto:102220181...@bjn.vc>
>> >>> > D - 14195 Berlin| E-Mail:
>> &g

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

[Heinz Junkes]

I’m away from my keyboard. If you use the epics Adaption to rtems from my 
github “playground?” and bsp’s with —enable-networks should compile.
Heinz 

FHI, Heinz Junkes

> On 7. Jul 2020, at 18:14, Mritunjay Sharma  
> wrote:
> 
> 
> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu. 
> Everything worked fine while building the pc-386 with  RTEMS5.
> 
> After this when I entered epics-base and made the following change:
> 
> epics-base/os/CONFIG_SITE.Common.RTEMS
> RTEMS_VERSION = 5
> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION) 
>  
> As an experiment, I ran the make and as expected got the following error
> 
> Error: 
> 
> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include
>  -c ../rtems_init.c
> ../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory
>  #include 
>   ^~~
> compilation terminated.
> ../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o' failed
> make[4]: *** [rtems_init.o] Error 1
> make[4]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
> ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' 
> failed
> make[3]: *** [install.RTEMS-pc386] Error 2
> make[3]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS'
> ../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed
> make[2]: *** [RTEMS.install] Error 2
> make[2]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
> ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
> make[1]: *** [libcom.install] Error 2
> make[1]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules'
> configure/RULES_DIRS:85: recipe for target 'modules.install' failed
> make: *** [modules.install] Error 2
> ```
> 
> I am trying to figure out the error and making the changes in code to debug 
> it. 
> However, I will appreciate if Heinz and everyone else can help me a little, 
> if they have an
> idea of this error. 
> 
> Thanks
> Mritunjay 
> 
>> On Tue, Jul 7, 2020 at 7:30 PM Mritunjay Sharma 
>>  wrote:
>> 
>> 
>>> On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom  wrote:
>>> On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill  wrote:
>>> >
>>> >
>>> >
>>> > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:
>>> >>
>>> >> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
>>> >>  wrote:
>>> >> >
>>> >> > Hello everyone,
>>> >> >
>>> >> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
>>> >> > If there are issues in making a buildset for 4.10
>>> >> > then should I build EPICS with RTEMS 5 by hand first and note
>>> >> > down the process and then proceed to make the buildset for it?
>>> >> >
>>> >>
>>> >> Yes.
>>> >
>>> >
>>> > +1
>>> >
>>> > And by 5, we definitely mean the 5 branch for all rtems repo and the 
>>> > similarly named one for libbsd.
>>> 
>>> Excellent point. We want to add support for easy build (and eventually
>>> test) of EPICS+RTEMS starting with 5.1 and moving forward, which means
>>> also doing it for RTEMS 6, Mritunjay.
>>> 
>> Sounds good, I have begun building it hand by today for RTEMS 5 branch and 
>> later on continue the 
>> same for RTEMS6
>> 
>> Thank you so much Gedare and Joel. 
>> Mritunjay 
>>> >>
>>> >>
>>> >> > Please suggest for the future steps.
>>> >> >
>>> >> > Thanks
>>> >> > Mritunjay
>>> >> >
>>> >> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
>>> >> >>>
>>> >> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>>> >> >>> > Thank you, this is exactly where I was unsure.
>>> >> >>> > @Chris: Can you give a recommendation here?
>>> >> >>> > Danke Heinz
>>> >> >>> > --
>>> >> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>>> >> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>>> >> >>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
>>> >> >>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
>>> >> >>> > --
>>> >> >>> >
>>> >> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
>>> >> >>> >>
>>> >> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>>> >> >>> >>  wrote:
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes 
>>> >> >>> >>>  wrote:
>>> >> >>> 
>>> >> >>>  Hello, Mritunjay,
>>> >> >>>  that's good news. Don't you want to try to develop a rsb-set 
>>> >> >>>  for exactly this combination of RTEMS4.10 and EPICS7?
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the 
>>> >> >>> >>> same way. Please tell how to begin or some existing similar
>>> >> >>> >>> work that 

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

[Mritunjay Sharma]

[UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.
Everything worked fine while building the pc-386 with  RTEMS5.

After this when I entered epics-base and made the following change:

epics-base/os/CONFIG_SITE.Common.RTEMS
RTEMS_VERSION = 5
RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)

As an experiment, I ran the make and as expected got the following error

Error:

```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include
-c ../rtems_init.c
../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory
 #include 
  ^~~
compilation terminated.
../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o'
failed
make[4]: *** [rtems_init.o] Error 1
make[4]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS/O.RTEMS-pc386'
../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386'
failed
make[3]: *** [install.RTEMS-pc386] Error 2
make[3]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/RTEMS'
../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed
make[2]: *** [RTEMS.install] Error 2
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom'
../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
make[1]: *** [libcom.install] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules'
configure/RULES_DIRS:85: recipe for target 'modules.install' failed
make: *** [modules.install] Error 2
```

I am trying to figure out the error and making the changes in code to debug
it.
However, I will appreciate if Heinz and everyone else can help me a little,
if they have an
idea of this error.

Thanks
Mritunjay

On Tue, Jul 7, 2020 at 7:30 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom  wrote:
>
>> On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill  wrote:
>> >
>> >
>> >
>> > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:
>> >>
>> >> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
>> >>  wrote:
>> >> >
>> >> > Hello everyone,
>> >> >
>> >> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
>> >> > If there are issues in making a buildset for 4.10
>> >> > then should I build EPICS with RTEMS 5 by hand first and note
>> >> > down the process and then proceed to make the buildset for it?
>> >> >
>> >>
>> >> Yes.
>> >
>> >
>> > +1
>> >
>> > And by 5, we definitely mean the 5 branch for all rtems repo and the
>> similarly named one for libbsd.
>>
>> Excellent point. We want to add support for easy build (and eventually
>> test) of EPICS+RTEMS starting with 5.1 and moving forward, which means
>> also doing it for RTEMS 6, Mritunjay.
>>
>> Sounds good, I have begun building it hand by today for RTEMS 5 branch
> and later on continue the
> same for RTEMS6
>
> Thank you so much Gedare and Joel.
> Mritunjay
>
>> >>
>> >>
>> >> > Please suggest for the future steps.
>> >> >
>> >> > Thanks
>> >> > Mritunjay
>> >> >
>> >> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
>> >> >>>
>> >> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>> >> >>> > Thank you, this is exactly where I was unsure.
>> >> >>> > @Chris: Can you give a recommendation here?
>> >> >>> > Danke Heinz
>> >> >>> >
>> --
>> >> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>> >> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>> >> >>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
>> >> >>> > D - 14195 Berlin| E-Mail:
>> jun...@fhi-berlin.mpg.de
>> >> >>> >
>> --
>> >> >>> >
>> >> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom 
>> wrote:
>> >> >>> >>
>> >> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>> >> >>> >>  wrote:
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes <
>> jun...@fhi-berlin.mpg.de> wrote:
>> >> >>> 
>> >> >>>  Hello, Mritunjay,
>> >> >>>  that's good news. Don't you want to try to develop a rsb-set
>> for exactly this combination of RTEMS4.10 and EPICS7?
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the
>> same way. Please tell how to begin or some existing similar
>> >> >>> >>> work that can guide me how to proceed further in relation to
>> rsb-set for  RTEMS4.10 and EPICS7.
>> >> >>> >>>
>> >> >>> >>
>> >> >>> >> I don't know if this is best. RSB didn't exist in 4.10. I
>> haven't
>> >> >>> >> looked to see how well the rtems-source-builder/4.10 would
>> support a
>> >> >>> >> package build. It should be discussed with Chris probably. A
>> couple of
>> >> >>> >> packages were added in the 4.11 

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

[Mritunjay Sharma]

On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom  wrote:

> On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill  wrote:
> >
> >
> >
> > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:
> >>
> >> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > Hello everyone,
> >> >
> >> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
> >> > If there are issues in making a buildset for 4.10
> >> > then should I build EPICS with RTEMS 5 by hand first and note
> >> > down the process and then proceed to make the buildset for it?
> >> >
> >>
> >> Yes.
> >
> >
> > +1
> >
> > And by 5, we definitely mean the 5 branch for all rtems repo and the
> similarly named one for libbsd.
>
> Excellent point. We want to add support for easy build (and eventually
> test) of EPICS+RTEMS starting with 5.1 and moving forward, which means
> also doing it for RTEMS 6, Mritunjay.
>
> Sounds good, I have begun building it hand by today for RTEMS 5 branch and
later on continue the
same for RTEMS6

Thank you so much Gedare and Joel.
Mritunjay

> >>
> >>
> >> > Please suggest for the future steps.
> >> >
> >> > Thanks
> >> > Mritunjay
> >> >
> >> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
> >> >>>
> >> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
> >> >>> > Thank you, this is exactly where I was unsure.
> >> >>> > @Chris: Can you give a recommendation here?
> >> >>> > Danke Heinz
> >> >>> >
> --
> >> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
> >> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
> >> >>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
> >> >>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
> >> >>> >
> --
> >> >>> >
> >> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
> >> >>> >>
> >> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
> >> >>> >>  wrote:
> >> >>> >>>
> >> >>> >>>
> >> >>> >>>
> >> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes <
> jun...@fhi-berlin.mpg.de> wrote:
> >> >>> 
> >> >>>  Hello, Mritunjay,
> >> >>>  that's good news. Don't you want to try to develop a rsb-set
> for exactly this combination of RTEMS4.10 and EPICS7?
> >> >>> >>>
> >> >>> >>>
> >> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the
> same way. Please tell how to begin or some existing similar
> >> >>> >>> work that can guide me how to proceed further in relation to
> rsb-set for  RTEMS4.10 and EPICS7.
> >> >>> >>>
> >> >>> >>
> >> >>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
> >> >>> >> looked to see how well the rtems-source-builder/4.10 would
> support a
> >> >>> >> package build. It should be discussed with Chris probably. A
> couple of
> >> >>> >> packages were added in the 4.11 branch.
> >> >>>
> >> >>> I would leave 4.10 and move on. It may work but these things can
> expose issues
> >> >>> that turn into distractions.
> >> >>>
> >> >>> Would making a script that does the build so we can document the
> steps be worth
> >> >>> while
> >> >>
> >> >>
> >> >> Yes. Emphatically yes. We need to make sure we know how it is best
> built by hand to automate it.
> >> >>
> >> >> I firmly believe you should not attempt to automate something until
> doing it manually is well understood and documented.
> >> >>
> >> >> After you have this down for one BSP, we need to ask questions like:
> >> >>
> >> >> + Is there any per BSP tailoring beyond the obviod architecture and
> compilation settings?
> >> >>
> >> >> + Any tweaks to settings users may want?
> >> >>
> >> >> The manual process should include testing. The RSB is a great way to
> automate and ease building but it doesn't address testing the packages yet.
> >> >>
> >> >> --joel
> >> >>
> >> >>>
> >> >>> Chris
> >> >>> ___
> >> >>> devel mailing list
> >> >>> devel@rtems.org
> >> >>> http://lists.rtems.org/mailman/listinfo/devel
> >> >>
> >> >> ___
> >> >> devel mailing list
> >> >> devel@rtems.org
> >> >> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill  wrote:
>
>
>
> On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:
>>
>> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
>>  wrote:
>> >
>> > Hello everyone,
>> >
>> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
>> > If there are issues in making a buildset for 4.10
>> > then should I build EPICS with RTEMS 5 by hand first and note
>> > down the process and then proceed to make the buildset for it?
>> >
>>
>> Yes.
>
>
> +1
>
> And by 5, we definitely mean the 5 branch for all rtems repo and the 
> similarly named one for libbsd.

Excellent point. We want to add support for easy build (and eventually
test) of EPICS+RTEMS starting with 5.1 and moving forward, which means
also doing it for RTEMS 6, Mritunjay.

>>
>>
>> > Please suggest for the future steps.
>> >
>> > Thanks
>> > Mritunjay
>> >
>> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
>> >>>
>> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>> >>> > Thank you, this is exactly where I was unsure.
>> >>> > @Chris: Can you give a recommendation here?
>> >>> > Danke Heinz
>> >>> > --
>> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>> >>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
>> >>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
>> >>> > --
>> >>> >
>> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
>> >>> >>
>> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>> >>> >>  wrote:
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes 
>> >>> >>>  wrote:
>> >>> 
>> >>>  Hello, Mritunjay,
>> >>>  that's good news. Don't you want to try to develop a rsb-set for 
>> >>>  exactly this combination of RTEMS4.10 and EPICS7?
>> >>> >>>
>> >>> >>>
>> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the same 
>> >>> >>> way. Please tell how to begin or some existing similar
>> >>> >>> work that can guide me how to proceed further in relation to rsb-set 
>> >>> >>> for  RTEMS4.10 and EPICS7.
>> >>> >>>
>> >>> >>
>> >>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
>> >>> >> looked to see how well the rtems-source-builder/4.10 would support a
>> >>> >> package build. It should be discussed with Chris probably. A couple of
>> >>> >> packages were added in the 4.11 branch.
>> >>>
>> >>> I would leave 4.10 and move on. It may work but these things can expose 
>> >>> issues
>> >>> that turn into distractions.
>> >>>
>> >>> Would making a script that does the build so we can document the steps 
>> >>> be worth
>> >>> while
>> >>
>> >>
>> >> Yes. Emphatically yes. We need to make sure we know how it is best built 
>> >> by hand to automate it.
>> >>
>> >> I firmly believe you should not attempt to automate something until doing 
>> >> it manually is well understood and documented.
>> >>
>> >> After you have this down for one BSP, we need to ask questions like:
>> >>
>> >> + Is there any per BSP tailoring beyond the obviod architecture and 
>> >> compilation settings?
>> >>
>> >> + Any tweaks to settings users may want?
>> >>
>> >> The manual process should include testing. The RSB is a great way to 
>> >> automate and ease building but it doesn't address testing the packages 
>> >> yet.
>> >>
>> >> --joel
>> >>
>> >>>
>> >>> Chris
>> >>> ___
>> >>> devel mailing list
>> >>> devel@rtems.org
>> >>> http://lists.rtems.org/mailman/listinfo/devel
>> >>
>> >> ___
>> >> devel mailing list
>> >> devel@rtems.org
>> >> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Joel Sherrill]

On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom  wrote:

> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
>  wrote:
> >
> > Hello everyone,
> >
> > Thank you, Heinz, Gedare, Chris and Joel for your advice.
> > If there are issues in making a buildset for 4.10
> > then should I build EPICS with RTEMS 5 by hand first and note
> > down the process and then proceed to make the buildset for it?
> >
>
> Yes.
>

+1

And by 5, we definitely mean the 5 branch for all rtems repo and the
similarly named one for libbsd.

>
> > Please suggest for the future steps.
> >
> > Thanks
> > Mritunjay
> >
> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
> >>
> >>
> >>
> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
> >>>
> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:
> >>> > Thank you, this is exactly where I was unsure.
> >>> > @Chris: Can you give a recommendation here?
> >>> > Danke Heinz
> >>> >
> --
> >>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
> >>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
> >>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
> >>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
> >>> >
> --
> >>> >
> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
> >>> >>
> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
> >>> >>  wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes <
> jun...@fhi-berlin.mpg.de> wrote:
> >>> 
> >>>  Hello, Mritunjay,
> >>>  that's good news. Don't you want to try to develop a rsb-set for
> exactly this combination of RTEMS4.10 and EPICS7?
> >>> >>>
> >>> >>>
> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the same
> way. Please tell how to begin or some existing similar
> >>> >>> work that can guide me how to proceed further in relation to
> rsb-set for  RTEMS4.10 and EPICS7.
> >>> >>>
> >>> >>
> >>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
> >>> >> looked to see how well the rtems-source-builder/4.10 would support a
> >>> >> package build. It should be discussed with Chris probably. A couple
> of
> >>> >> packages were added in the 4.11 branch.
> >>>
> >>> I would leave 4.10 and move on. It may work but these things can
> expose issues
> >>> that turn into distractions.
> >>>
> >>> Would making a script that does the build so we can document the steps
> be worth
> >>> while
> >>
> >>
> >> Yes. Emphatically yes. We need to make sure we know how it is best
> built by hand to automate it.
> >>
> >> I firmly believe you should not attempt to automate something until
> doing it manually is well understood and documented.
> >>
> >> After you have this down for one BSP, we need to ask questions like:
> >>
> >> + Is there any per BSP tailoring beyond the obviod architecture and
> compilation settings?
> >>
> >> + Any tweaks to settings users may want?
> >>
> >> The manual process should include testing. The RSB is a great way to
> automate and ease building but it doesn't address testing the packages yet.
> >>
> >> --joel
> >>
> >>>
> >>> Chris
> >>> ___
> >>> devel mailing list
> >>> devel@rtems.org
> >>> http://lists.rtems.org/mailman/listinfo/devel
> >>
> >> ___
> >> devel mailing list
> >> devel@rtems.org
> >> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma
 wrote:
>
> Hello everyone,
>
> Thank you, Heinz, Gedare, Chris and Joel for your advice.
> If there are issues in making a buildset for 4.10
> then should I build EPICS with RTEMS 5 by hand first and note
> down the process and then proceed to make the buildset for it?
>

Yes.

> Please suggest for the future steps.
>
> Thanks
> Mritunjay
>
> On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:
>>
>>
>>
>> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
>>>
>>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>>> > Thank you, this is exactly where I was unsure.
>>> > @Chris: Can you give a recommendation here?
>>> > Danke Heinz
>>> > --
>>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
>>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
>>> > --
>>> >
>>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
>>> >>
>>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>>> >>  wrote:
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes  
>>> >>> wrote:
>>> 
>>>  Hello, Mritunjay,
>>>  that's good news. Don't you want to try to develop a rsb-set for 
>>>  exactly this combination of RTEMS4.10 and EPICS7?
>>> >>>
>>> >>>
>>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the same way. 
>>> >>> Please tell how to begin or some existing similar
>>> >>> work that can guide me how to proceed further in relation to rsb-set 
>>> >>> for  RTEMS4.10 and EPICS7.
>>> >>>
>>> >>
>>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
>>> >> looked to see how well the rtems-source-builder/4.10 would support a
>>> >> package build. It should be discussed with Chris probably. A couple of
>>> >> packages were added in the 4.11 branch.
>>>
>>> I would leave 4.10 and move on. It may work but these things can expose 
>>> issues
>>> that turn into distractions.
>>>
>>> Would making a script that does the build so we can document the steps be 
>>> worth
>>> while
>>
>>
>> Yes. Emphatically yes. We need to make sure we know how it is best built by 
>> hand to automate it.
>>
>> I firmly believe you should not attempt to automate something until doing it 
>> manually is well understood and documented.
>>
>> After you have this down for one BSP, we need to ask questions like:
>>
>> + Is there any per BSP tailoring beyond the obviod architecture and 
>> compilation settings?
>>
>> + Any tweaks to settings users may want?
>>
>> The manual process should include testing. The RSB is a great way to 
>> automate and ease building but it doesn't address testing the packages yet.
>>
>> --joel
>>
>>>
>>> Chris
>>> ___
>>> devel mailing list
>>> devel@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

Hello everyone,

Thank you, Heinz, Gedare, Chris and Joel for your advice.
If there are issues in making a buildset for 4.10
then should I build EPICS with RTEMS 5 by hand first and note
down the process and then proceed to make the buildset for it?

Please suggest for the future steps.

Thanks
Mritunjay

On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill  wrote:

>
>
> On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:
>
>> On 6/7/20 12:47 am, Heinz Junkes wrote:
>> > Thank you, this is exactly where I was unsure.
>> > @Chris: Can you give a recommendation here?
>> > Danke Heinz
>> >
>> --
>> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
>> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
>> > Faradayweg 4-6| VC: 102220181...@bjn.vc
>> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
>> >
>> --
>> >
>> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
>> >>
>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>> >>  wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes <
>> jun...@fhi-berlin.mpg.de> wrote:
>> 
>>  Hello, Mritunjay,
>>  that's good news. Don't you want to try to develop a rsb-set for
>> exactly this combination of RTEMS4.10 and EPICS7?
>> >>>
>> >>>
>> >>> Sure, I am ready to do this and then do it with RTEMS5 in the same
>> way. Please tell how to begin or some existing similar
>> >>> work that can guide me how to proceed further in relation to rsb-set
>> for  RTEMS4.10 and EPICS7.
>> >>>
>> >>
>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
>> >> looked to see how well the rtems-source-builder/4.10 would support a
>> >> package build. It should be discussed with Chris probably. A couple of
>> >> packages were added in the 4.11 branch.
>>
>> I would leave 4.10 and move on. It may work but these things can expose
>> issues
>> that turn into distractions.
>>
>> Would making a script that does the build so we can document the steps be
>> worth
>> while
>
>
> Yes. Emphatically yes. We need to make sure we know how it is best built
> by hand to automate it.
>
> I firmly believe you should not attempt to automate something until doing
> it manually is well understood and documented.
>
> After you have this down for one BSP, we need to ask questions like:
>
> + Is there any per BSP tailoring beyond the obviod architecture and
> compilation settings?
>
> + Any tweaks to settings users may want?
>
> The manual process should include testing. The RSB is a great way to
> automate and ease building but it doesn't address testing the packages yet.
>
> --joel
>
>
>> Chris
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Joel Sherrill]

On Sun, Jul 5, 2020, 6:12 PM Chris Johns  wrote:

> On 6/7/20 12:47 am, Heinz Junkes wrote:
> > Thank you, this is exactly where I was unsure.
> > @Chris: Can you give a recommendation here?
> > Danke Heinz
> >
> --
> > Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
> > Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
> > Faradayweg 4-6| VC: 102220181...@bjn.vc
> > D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
> >
> --
> >
> >> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
> >>
> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
> >>  wrote:
> >>>
> >>>
> >>>
> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes 
> wrote:
> 
>  Hello, Mritunjay,
>  that's good news. Don't you want to try to develop a rsb-set for
> exactly this combination of RTEMS4.10 and EPICS7?
> >>>
> >>>
> >>> Sure, I am ready to do this and then do it with RTEMS5 in the same
> way. Please tell how to begin or some existing similar
> >>> work that can guide me how to proceed further in relation to rsb-set
> for  RTEMS4.10 and EPICS7.
> >>>
> >>
> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't
> >> looked to see how well the rtems-source-builder/4.10 would support a
> >> package build. It should be discussed with Chris probably. A couple of
> >> packages were added in the 4.11 branch.
>
> I would leave 4.10 and move on. It may work but these things can expose
> issues
> that turn into distractions.
>
> Would making a script that does the build so we can document the steps be
> worth
> while


Yes. Emphatically yes. We need to make sure we know how it is best built by
hand to automate it.

I firmly believe you should not attempt to automate something until doing
it manually is well understood and documented.

After you have this down for one BSP, we need to ask questions like:

+ Is there any per BSP tailoring beyond the obviod architecture and
compilation settings?

+ Any tweaks to settings users may want?

The manual process should include testing. The RSB is a great way to
automate and ease building but it doesn't address testing the packages yet.

--joel


> Chris
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Chris Johns]

On 6/7/20 12:47 am, Heinz Junkes wrote:
> Thank you, this is exactly where I was unsure.
> @Chris: Can you give a recommendation here?
> Danke Heinz
> --
> Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
> Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
> Faradayweg 4-6| VC: 102220181...@bjn.vc
> D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
> --
> 
>> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
>>
>> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>>  wrote:
>>>
>>>
>>>
>>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes  
>>> wrote:

 Hello, Mritunjay,
 that's good news. Don't you want to try to develop a rsb-set for exactly 
 this combination of RTEMS4.10 and EPICS7?
>>>
>>>
>>> Sure, I am ready to do this and then do it with RTEMS5 in the same way. 
>>> Please tell how to begin or some existing similar
>>> work that can guide me how to proceed further in relation to rsb-set for  
>>> RTEMS4.10 and EPICS7.
>>>
>>
>> I don't know if this is best. RSB didn't exist in 4.10. I haven't
>> looked to see how well the rtems-source-builder/4.10 would support a
>> package build. It should be discussed with Chris probably. A couple of
>> packages were added in the 4.11 branch.

I would leave 4.10 and move on. It may work but these things can expose issues
that turn into distractions.

Would making a script that does the build so we can document the steps be worth
while?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Heinz Junkes]

Thank you, this is exactly where I was unsure.
@Chris: Can you give a recommendation here?
Danke Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
Faradayweg 4-6| VC: 102220181...@bjn.vc
D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
--

> On 5. Jul 2020, at 16:20, Gedare Bloom  wrote:
> 
> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
>  wrote:
>> 
>> 
>> 
>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes  
>> wrote:
>>> 
>>> Hello, Mritunjay,
>>> that's good news. Don't you want to try to develop a rsb-set for exactly 
>>> this combination of RTEMS4.10 and EPICS7?
>> 
>> 
>> Sure, I am ready to do this and then do it with RTEMS5 in the same way. 
>> Please tell how to begin or some existing similar
>> work that can guide me how to proceed further in relation to rsb-set for  
>> RTEMS4.10 and EPICS7.
>> 
> 
> I don't know if this is best. RSB didn't exist in 4.10. I haven't
> looked to see how well the rtems-source-builder/4.10 would support a
> package build. It should be discussed with Chris probably. A couple of
> packages were added in the 4.11 branch.



smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma
 wrote:
>
>
>
> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes  wrote:
>>
>> Hello, Mritunjay,
>> that's good news. Don't you want to try to develop a rsb-set for exactly 
>> this combination of RTEMS4.10 and EPICS7?
>
>
> Sure, I am ready to do this and then do it with RTEMS5 in the same way. 
> Please tell how to begin or some existing similar
> work that can guide me how to proceed further in relation to rsb-set for  
> RTEMS4.10 and EPICS7.
>

I don't know if this is best. RSB didn't exist in 4.10. I haven't
looked to see how well the rtems-source-builder/4.10 would support a
package build. It should be discussed with Chris probably. A couple of
packages were added in the 4.11 branch.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

On Sun, Jul 5, 2020 at 12:48 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes 
> wrote:
>
>> Hello, Mritunjay,
>> that's good news. Don't you want to try to develop a rsb-set for exactly
>> this combination of RTEMS4.10 and EPICS7?
>>
>
> Sure, I am ready to do this and then do it with RTEMS5 in the same way.
> Please tell how to begin or some existing similar
> work that can guide me how to proceed further in relation to rsb-set for
> RTEMS4.10 and EPICS7.
>
> Then it should be no problem to do it with RTEMS5 in the same way.
>> Did you also run the tests on Epics and also tried the pc386-qemu?
>>
>
[UPDATE]: I just finished trying pc386-qemu. The 'make' in epics-base ran
successfully.
After which I ran the Ran the EPICS test suites for RTEMS in QEMU using the
following command:

```qemu-system-i386 -no-reboot -m 128 -boot n -serial stdio  -net nic -net
user,tftp=$PWD,bootfile=bin/RTEMS-pc386-qemu/dbTestHarness```

The QEMU emulator successfully opened then and it showed that all the tests
passed.
I am attaching the screenshot as well.

Please check and tell if I have done things correctly.

Thanks
Mritunjay





> I did the following steps after the build:
>
> i) Created a new directory to hold the application source and then `cd' to
> that directory.
> ii) Run the makeBaseApp.pl program to create the example application:
> iii) makeBaseApp.pl -t example test
> iv) makeBaseApp.pl -i -t example -a RTEMS-pc386 test
>
> I then Built the example application by running
> 'make'
>
> All the steps ran without error.
>
> I didn't test further after this. I haven't tried for pc396-qemu yet,
> I will try though today.
>
> Thanks
> Mritunjay.
>
> Greetings Heinz
>>
>> > On 3. Jul 2020, at 23:56, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >
>> > [UPDATE]: After using --enable-posix, the 'make' in epics-base worked
>> successfully.
>> > With all of yours support, there are no errors. Everything seems to be
>> in order.
>> >
>> > Heinz, as you suggested, now I have built EPICS with RTEMS 4.10 for
>> pc-386 and as advised that after this
>> > we can take care of RTEMS5 (or 6?) and libbsd as I have learnt now how
>> to build EPICS and I think we can develop
>> > a first rsb-set for it.
>> >
>> > Please advise on what to begin with next.
>> >
>> > Thanks
>> > Mritunjay
>>
>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes 
wrote:

> Hello, Mritunjay,
> that's good news. Don't you want to try to develop a rsb-set for exactly
> this combination of RTEMS4.10 and EPICS7?
>

Sure, I am ready to do this and then do it with RTEMS5 in the same way.
Please tell how to begin or some existing similar
work that can guide me how to proceed further in relation to rsb-set for
RTEMS4.10 and EPICS7.

Then it should be no problem to do it with RTEMS5 in the same way.
> Did you also run the tests on Epics and also tried the pc386-qemu?
>

I did the following steps after the build:

i) Created a new directory to hold the application source and then `cd' to
that directory.
ii) Run the makeBaseApp.pl program to create the example application:
iii) makeBaseApp.pl -t example test
iv) makeBaseApp.pl -i -t example -a RTEMS-pc386 test

I then Built the example application by running
'make'

All the steps ran without error.

I didn't test further after this. I haven't tried for pc396-qemu yet,
I will try though today.

Thanks
Mritunjay.

Greetings Heinz
>
> > On 3. Jul 2020, at 23:56, Mritunjay Sharma 
> wrote:
> >
> > [UPDATE]: After using --enable-posix, the 'make' in epics-base worked
> successfully.
> > With all of yours support, there are no errors. Everything seems to be
> in order.
> >
> > Heinz, as you suggested, now I have built EPICS with RTEMS 4.10 for
> pc-386 and as advised that after this
> > we can take care of RTEMS5 (or 6?) and libbsd as I have learnt now how
> to build EPICS and I think we can develop
> > a first rsb-set for it.
> >
> > Please advise on what to begin with next.
> >
> > Thanks
> > Mritunjay
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Heinz Junkes]

Hello, Mritunjay,
that's good news. Don't you want to try to develop a rsb-set for exactly this 
combination of RTEMS4.10 and EPICS7? 
Then it should be no problem to do it with RTEMS5 in the same way.
Did you also run the tests on Epics and also tried the pc386-qemu?
Greetings Heinz 

> On 3. Jul 2020, at 23:56, Mritunjay Sharma  
> wrote:
> 
> [UPDATE]: After using --enable-posix, the 'make' in epics-base worked 
> successfully.
> With all of yours support, there are no errors. Everything seems to be in 
> order.
> 
> Heinz, as you suggested, now I have built EPICS with RTEMS 4.10 for pc-386 
> and as advised that after this
> we can take care of RTEMS5 (or 6?) and libbsd as I have learnt now how to 
> build EPICS and I think we can develop 
> a first rsb-set for it. 
> 
> Please advise on what to begin with next. 
> 
> Thanks
> Mritunjay



smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

[UPDATE]: After using --enable-posix, the 'make' in epics-base worked
successfully.
With all of yours support, there are no errors. Everything seems to be
in order.

Heinz, as you suggested, now I have built EPICS with RTEMS 4.10 for pc-386
and as advised that after this
we can take care of RTEMS5 (or 6?) and libbsd as I have learnt now how to
build EPICS and I think we can develop
a first rsb-set for it.

Please advise on what to begin with next.

Thanks
Mritunjay

On Sat, Jul 4, 2020 at 3:02 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Thank you so much Gedare, I will do it and revert back to you.
>
> Thanks
> Mritunjay
>
> On Sat, Jul 4, 2020 at 3:01 AM Gedare Bloom  wrote:
>
>> On Fri, Jul 3, 2020 at 3:07 PM Mritunjay Sharma
>>  wrote:
>> >
>> >
>> >
>> > On Fri, Jul 3, 2020 at 10:53 PM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> 
>> >> From: Gedare Bloom 
>> >> Sent: Friday, July 3, 2020 9:42 PM
>> >> To: Mritunjay Sharma
>> >> Cc: Heinz Junkes; Chris Johns; RTEMS Devel
>> >> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>> >>
>> >> On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
>> >>  wrote:
>> >> >
>> >> > Hello Heinz and everyone,
>> >> >
>> >> > Thank you so much, with this email, I will try to clear all the
>> things, and what is the status for now.
>> >> >
>> >> > First. let me tell you the current status: Vijay helped me last
>> night in an offlist discussion to clear the confusions which
>> >> > I was having (I will mention them below) due to which I was able to
>> build and install RTEMS 4.10 for pc386 successfully.
>> >> > With that, all my previous errors were resolved. Below is the detail
>> of all the steps, I followed.
>> >> >
>> >> > Let me tell that my development environment was earlier set up for
>> RTEMS5. For building EPICS with RTEMS,
>> >> > I thought it will be right to first build RTEMS 4.10 for pc386.
>> >> >
>> >> > In order to do that, I made the directory
>> >> >
>> >> > i) $HOME/development/rtems_dev
>> >> > ii) I extracted rtems-4.10.2 from here
>> https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
>> >> > iii)I created another directory rtems_dev/src
>> >> > iv)Inside src, I cloned rsb and moved to 4.10 branch.
>> >> > v) After performing checks, I entered to rsb/rtems and used this
>> command:
>> >> > '../source-builder/sb-set-builder
>> --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
>> >> > Even though the build completed successfully, this was the point
>> where I made the error. I used the RTEMS source as the prefix which
>> >> > was causing all the problems.
>> >> > vi) After the discussion with Vijay and getting cleared, I deleted
>> everything except the RTEMS RSB and restarted the process with prefix and
>> source
>> >> > different this time and rebuilt the compiler tools using RSB.
>> >> > vii) Now the directory structure under $HOME/development/rtems_dev/
>> looked like:
>> >> >   | rtems-4.10.2
>> >> >   | 4.10
>> >> >   | src/rsb
>> >> >   | kernel/pc386
>> >> > I also used this command: "export
>> PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
>> >> > vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
>> >> > "./bootstrap -c &&
>> $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
>> >> > vi) After this I went insid directory
>> $HOME/development/rtems_dev/kernel/pc-386
>> >> > vii) Inside pc-386, I used the following command:
>> >> > ''$HOME/development/rtems_dev/rtems-4.10.2/configure
>> --target=i386-rtems4.10 --disable-posix  --enable-rtemsbsp=pc386
>> --enable-tests=samples --prefix=/home/development/rtems_dev/rtems-4.10.2
>> --enable-cxx"
>>
>> You need to --enable-posix
>>
>> >> > viii) Then I entered the make command which ran successfully and the
>> make install was also successful.
>> >> >
>> >> > So all the errors were resolved and I moved on to build EPICS now
>> for RTEMS 4.10.
>> >> > I

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

[Mritunjay Sharma]

Thank you so much Gedare, I will do it and revert back to you.

Thanks
Mritunjay

On Sat, Jul 4, 2020 at 3:01 AM Gedare Bloom  wrote:

> On Fri, Jul 3, 2020 at 3:07 PM Mritunjay Sharma
>  wrote:
> >
> >
> >
> > On Fri, Jul 3, 2020 at 10:53 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >>
> >>
> >> 
> >> From: Gedare Bloom 
> >> Sent: Friday, July 3, 2020 9:42 PM
> >> To: Mritunjay Sharma
> >> Cc: Heinz Junkes; Chris Johns; RTEMS Devel
> >> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
> >>
> >> On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > Hello Heinz and everyone,
> >> >
> >> > Thank you so much, with this email, I will try to clear all the
> things, and what is the status for now.
> >> >
> >> > First. let me tell you the current status: Vijay helped me last night
> in an offlist discussion to clear the confusions which
> >> > I was having (I will mention them below) due to which I was able to
> build and install RTEMS 4.10 for pc386 successfully.
> >> > With that, all my previous errors were resolved. Below is the detail
> of all the steps, I followed.
> >> >
> >> > Let me tell that my development environment was earlier set up for
> RTEMS5. For building EPICS with RTEMS,
> >> > I thought it will be right to first build RTEMS 4.10 for pc386.
> >> >
> >> > In order to do that, I made the directory
> >> >
> >> > i) $HOME/development/rtems_dev
> >> > ii) I extracted rtems-4.10.2 from here
> https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
> >> > iii)I created another directory rtems_dev/src
> >> > iv)Inside src, I cloned rsb and moved to 4.10 branch.
> >> > v) After performing checks, I entered to rsb/rtems and used this
> command:
> >> > '../source-builder/sb-set-builder
> --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
> >> > Even though the build completed successfully, this was the point
> where I made the error. I used the RTEMS source as the prefix which
> >> > was causing all the problems.
> >> > vi) After the discussion with Vijay and getting cleared, I deleted
> everything except the RTEMS RSB and restarted the process with prefix and
> source
> >> > different this time and rebuilt the compiler tools using RSB.
> >> > vii) Now the directory structure under $HOME/development/rtems_dev/
> looked like:
> >> >   | rtems-4.10.2
> >> >   | 4.10
> >> >   | src/rsb
> >> >   | kernel/pc386
> >> > I also used this command: "export
> PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
> >> > vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
> >> > "./bootstrap -c &&
> $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
> >> > vi) After this I went insid directory
> $HOME/development/rtems_dev/kernel/pc-386
> >> > vii) Inside pc-386, I used the following command:
> >> > ''$HOME/development/rtems_dev/rtems-4.10.2/configure
> --target=i386-rtems4.10 --disable-posix  --enable-rtemsbsp=pc386
> --enable-tests=samples --prefix=/home/development/rtems_dev/rtems-4.10.2
> --enable-cxx"
>
> You need to --enable-posix
>
> >> > viii) Then I entered the make command which ran successfully and the
> make install was also successful.
> >> >
> >> > So all the errors were resolved and I moved on to build EPICS now for
> RTEMS 4.10.
> >> > I also used this command:
> >> > '''export
> RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
> >> > Location of epics-base in my system is as follows:
> >> > "$HOME/development/EPICS/epics-base"
> >> >
> >> > After this, I followed the tutorial you sent to build EPICS for
> rterms-4.10 for pc-386 which is:
> >> >>
> >> >> Very roughly:
> >> >> git clone —recursive epics-base
> >> >>
> >> >> in epics-base/configure/CONFIG_SITE
> >> >> set
> >> >> CROSS_COMPILER_TARGET_ARCHS=
> >> >
> >> >What I entered:
> >> >CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386
> >> >>
> >> >> e.g. RTEMS-pc386
> >> >> or RTEMS-xilinx_zynq_a9_qemu

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

[Gedare Bloom]

On Fri, Jul 3, 2020 at 3:07 PM Mritunjay Sharma
 wrote:
>
>
>
> On Fri, Jul 3, 2020 at 10:53 PM Mritunjay Sharma 
>  wrote:
>>
>>
>>
>> 
>> From: Gedare Bloom 
>> Sent: Friday, July 3, 2020 9:42 PM
>> To: Mritunjay Sharma
>> Cc: Heinz Junkes; Chris Johns; RTEMS Devel
>> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>>
>> On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
>>  wrote:
>> >
>> > Hello Heinz and everyone,
>> >
>> > Thank you so much, with this email, I will try to clear all the things, 
>> > and what is the status for now.
>> >
>> > First. let me tell you the current status: Vijay helped me last night in 
>> > an offlist discussion to clear the confusions which
>> > I was having (I will mention them below) due to which I was able to build 
>> > and install RTEMS 4.10 for pc386 successfully.
>> > With that, all my previous errors were resolved. Below is the detail of 
>> > all the steps, I followed.
>> >
>> > Let me tell that my development environment was earlier set up for RTEMS5. 
>> > For building EPICS with RTEMS,
>> > I thought it will be right to first build RTEMS 4.10 for pc386.
>> >
>> > In order to do that, I made the directory
>> >
>> > i) $HOME/development/rtems_dev
>> > ii) I extracted rtems-4.10.2 from here 
>> > https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
>> > iii)I created another directory rtems_dev/src
>> > iv)Inside src, I cloned rsb and moved to 4.10 branch.
>> > v) After performing checks, I entered to rsb/rtems and used this command:
>> > '../source-builder/sb-set-builder 
>> > --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 
>> > 4.10/rtems-i386'
>> > Even though the build completed successfully, this was the point where I 
>> > made the error. I used the RTEMS source as the prefix which
>> > was causing all the problems.
>> > vi) After the discussion with Vijay and getting cleared, I deleted 
>> > everything except the RTEMS RSB and restarted the process with prefix and 
>> > source
>> > different this time and rebuilt the compiler tools using RSB.
>> > vii) Now the directory structure under $HOME/development/rtems_dev/ looked 
>> > like:
>> >   | rtems-4.10.2
>> >   | 4.10
>> >   | src/rsb
>> >   | kernel/pc386
>> > I also used this command: "export 
>> > PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
>> > vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
>> > "./bootstrap -c && 
>> > $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
>> > vi) After this I went insid directory 
>> > $HOME/development/rtems_dev/kernel/pc-386
>> > vii) Inside pc-386, I used the following command:
>> > ''$HOME/development/rtems_dev/rtems-4.10.2/configure 
>> > --target=i386-rtems4.10 --disable-posix  --enable-rtemsbsp=pc386 
>> > --enable-tests=samples --prefix=/home/development/rtems_dev/rtems-4.10.2 
>> > --enable-cxx"

You need to --enable-posix

>> > viii) Then I entered the make command which ran successfully and the make 
>> > install was also successful.
>> >
>> > So all the errors were resolved and I moved on to build EPICS now for 
>> > RTEMS 4.10.
>> > I also used this command:
>> > '''export 
>> > RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
>> > Location of epics-base in my system is as follows:
>> > "$HOME/development/EPICS/epics-base"
>> >
>> > After this, I followed the tutorial you sent to build EPICS for 
>> > rterms-4.10 for pc-386 which is:
>> >>
>> >> Very roughly:
>> >> git clone —recursive epics-base
>> >>
>> >> in epics-base/configure/CONFIG_SITE
>> >> set
>> >> CROSS_COMPILER_TARGET_ARCHS=
>> >
>> >What I entered:
>> >CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386
>> >>
>> >> e.g. RTEMS-pc386
>> >> or RTEMS-xilinx_zynq_a9_qemu
>> >>
>> >> in epics-base/configure/os there must be a file for the target used,
>> >> e.g.
>> >> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>> >> or
>> >> CONFIG.Common.RTEMS-pc386
>> >
>> > Checked.  CONFIG.Common.RTEMS-pc386 was ther

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

[Mritunjay Sharma]

On Fri, Jul 3, 2020 at 10:53 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> --
> *From:* Gedare Bloom 
> *Sent:* Friday, July 3, 2020 9:42 PM
> *To:* Mritunjay Sharma
> *Cc:* Heinz Junkes; Chris Johns; RTEMS Devel
> *Subject:* Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5
>
> On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
>  wrote:
> >
> > Hello Heinz and everyone,
> >
> > Thank you so much, with this email, I will try to clear all the things,
> and what is the status for now.
> >
> > First. let me tell you the current status: Vijay helped me last night in
> an offlist discussion to clear the confusions which
> > I was having (I will mention them below) due to which I was able to
> build and install RTEMS 4.10 for pc386 successfully.
> > With that, all my previous errors were resolved. Below is the detail of
> all the steps, I followed.
> >
> > Let me tell that my development environment was earlier set up for
> RTEMS5. For building EPICS with RTEMS,
> > I thought it will be right to first build RTEMS 4.10 for pc386.
> >
> > In order to do that, I made the directory
> >
> > i) $HOME/development/rtems_dev
> > ii) I extracted rtems-4.10.2 from here
> https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
> > iii)I created another directory rtems_dev/src
> > iv)Inside src, I cloned rsb and moved to 4.10 branch.
> > v) After performing checks, I entered to rsb/rtems and used this command:
> > '../source-builder/sb-set-builder
> --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
> > Even though the build completed successfully, this was the point where I
> made the error. I used the RTEMS source as the prefix which
> > was causing all the problems.
> > vi) After the discussion with Vijay and getting cleared, I deleted
> everything except the RTEMS RSB and restarted the process with prefix and
> source
> > different this time and rebuilt the compiler tools using RSB.
> > vii) Now the directory structure under $HOME/development/rtems_dev/
> looked like:
> >   | rtems-4.10.2
> >   | 4.10
> >   | src/rsb
> >   | kernel/pc386
> > I also used this command: "export
> PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
> > vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
> > "./bootstrap -c &&
> $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
> > vi) After this I went insid directory
> $HOME/development/rtems_dev/kernel/pc-386
> > vii) Inside pc-386, I used the following command:
> > ''$HOME/development/rtems_dev/rtems-4.10.2/configure
> --target=i386-rtems4.10 --disable-posix  --enable-rtemsbsp=pc386
> --enable-tests=samples --prefix=/home/development/rtems_dev/rtems-4.10.2
> --enable-cxx"
> > viii) Then I entered the make command which ran successfully and the
> make install was also successful.
> >
> > So all the errors were resolved and I moved on to build EPICS now for
> RTEMS 4.10.
> > I also used this command:
> > '''export
> RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
> > Location of epics-base in my system is as follows:
> > "$HOME/development/EPICS/epics-base"
> >
> > After this, I followed the tutorial you sent to build EPICS for
> rterms-4.10 for pc-386 which is:
> >>
> >> Very roughly:
> >> git clone —recursive epics-base
> >>
> >> in epics-base/configure/CONFIG_SITE
> >> set
> >> CROSS_COMPILER_TARGET_ARCHS=
> >
> >What I entered:
> >CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386
> >>
> >> e.g. RTEMS-pc386
> >> or RTEMS-xilinx_zynq_a9_qemu
> >>
> >> in epics-base/configure/os there must be a file for the target used,
> >> e.g.
> >> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
> >> or
> >> CONFIG.Common.RTEMS-pc386
> >
> > Checked.  CONFIG.Common.RTEMS-pc386 was there
> >>
> >>
> >> Then you have to set in configure/os/CONFIG_SITE.Common.RTEMS
> >> where to find RTEMS:
> >>
> >> # Where to find RTEMS
> >> #
> >> # APS:
> >> #RTEMS_VERSION = 4.10.2
> >> #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
> >
> >
> > In my system, I entered this:
> > #APS
> > RTEMS_VERSION = 4.10
> > RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
> >
> > I followed the above instructions and used the 'make' command.
> >
&

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

[Mritunjay Sharma]

From: Gedare Bloom 
Sent: Friday, July 3, 2020 9:42 PM
To: Mritunjay Sharma
Cc: Heinz Junkes; Chris Johns; RTEMS Devel
Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5

On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
 wrote:
>
> Hello Heinz and everyone,
>
> Thank you so much, with this email, I will try to clear all the things, and 
> what is the status for now.
>
> First. let me tell you the current status: Vijay helped me last night in an 
> offlist discussion to clear the confusions which
> I was having (I will mention them below) due to which I was able to build and 
> install RTEMS 4.10 for pc386 successfully.
> With that, all my previous errors were resolved. Below is the detail of all 
> the steps, I followed.
>
> Let me tell that my development environment was earlier set up for RTEMS5. 
> For building EPICS with RTEMS,
> I thought it will be right to first build RTEMS 4.10 for pc386.
>
> In order to do that, I made the directory
>
> i) $HOME/development/rtems_dev
> ii) I extracted rtems-4.10.2 from here 
> https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
> iii)I created another directory rtems_dev/src
> iv)Inside src, I cloned rsb and moved to 4.10 branch.
> v) After performing checks, I entered to rsb/rtems and used this command:
> '../source-builder/sb-set-builder 
> --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
> Even though the build completed successfully, this was the point where I made 
> the error. I used the RTEMS source as the prefix which
> was causing all the problems.
> vi) After the discussion with Vijay and getting cleared, I deleted everything 
> except the RTEMS RSB and restarted the process with prefix and source
> different this time and rebuilt the compiler tools using RSB.
> vii) Now the directory structure under $HOME/development/rtems_dev/ looked 
> like:
>   | rtems-4.10.2
>   | 4.10
>   | src/rsb
>   | kernel/pc386
> I also used this command: "export 
> PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
> vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
> "./bootstrap -c && 
> $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
> vi) After this I went insid directory 
> $HOME/development/rtems_dev/kernel/pc-386
> vii) Inside pc-386, I used the following command:
> ''$HOME/development/rtems_dev/rtems-4.10.2/configure --target=i386-rtems4.10 
> --disable-posix  --enable-rtemsbsp=pc386 --enable-tests=samples 
> --prefix=/home/development/rtems_dev/rtems-4.10.2 --enable-cxx"
> viii) Then I entered the make command which ran successfully and the make 
> install was also successful.
>
> So all the errors were resolved and I moved on to build EPICS now for RTEMS 
> 4.10.
> I also used this command:
> '''export 
> RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
> Location of epics-base in my system is as follows:
> "$HOME/development/EPICS/epics-base"
>
> After this, I followed the tutorial you sent to build EPICS for rterms-4.10 
> for pc-386 which is:
>>
>> Very roughly:
>> git clone —recursive epics-base
>>
>> in epics-base/configure/CONFIG_SITE
>> set
>> CROSS_COMPILER_TARGET_ARCHS=
>
>What I entered:
>CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386
>>
>> e.g. RTEMS-pc386
>> or RTEMS-xilinx_zynq_a9_qemu
>>
>> in epics-base/configure/os there must be a file for the target used,
>> e.g.
>> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>> or
>> CONFIG.Common.RTEMS-pc386
>
> Checked.  CONFIG.Common.RTEMS-pc386 was there
>>
>>
>> Then you have to set in configure/os/CONFIG_SITE.Common.RTEMS
>> where to find RTEMS:
>>
>> # Where to find RTEMS
>> #
>> # APS:
>> #RTEMS_VERSION = 4.10.2
>> #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>
>
> In my system, I entered this:
> #APS
> RTEMS_VERSION = 4.10
> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
>
> I followed the above instructions and used the 'make' command.
>
>
> While the earlier errors are resolved, The latest error that I have 
> encountered is this after using make command.:
>
> "...Info':
> /home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.RTEMS-pc386/../osi/os/RTEMS/osdThread.c:747:
>  undefined reference to `pthread_getschedparam'
> collect2: ld returned 1 exit status
> ../../../../configure/RULES_BUILD:212: recipe for target 'libComTestHarness' 
> failed
> make[4]: *** [libComTestHarness] Error 1
> make[4]: Leaving directory 
> '/home/mritunjay/deve

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

[Gedare Bloom]

On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma
 wrote:
>
> Hello Heinz and everyone,
>
> Thank you so much, with this email, I will try to clear all the things, and 
> what is the status for now.
>
> First. let me tell you the current status: Vijay helped me last night in an 
> offlist discussion to clear the confusions which
> I was having (I will mention them below) due to which I was able to build and 
> install RTEMS 4.10 for pc386 successfully.
> With that, all my previous errors were resolved. Below is the detail of all 
> the steps, I followed.
>
> Let me tell that my development environment was earlier set up for RTEMS5. 
> For building EPICS with RTEMS,
> I thought it will be right to first build RTEMS 4.10 for pc386.
>
> In order to do that, I made the directory
>
> i) $HOME/development/rtems_dev
> ii) I extracted rtems-4.10.2 from here 
> https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
> iii)I created another directory rtems_dev/src
> iv)Inside src, I cloned rsb and moved to 4.10 branch.
> v) After performing checks, I entered to rsb/rtems and used this command:
> '../source-builder/sb-set-builder 
> --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
> Even though the build completed successfully, this was the point where I made 
> the error. I used the RTEMS source as the prefix which
> was causing all the problems.
> vi) After the discussion with Vijay and getting cleared, I deleted everything 
> except the RTEMS RSB and restarted the process with prefix and source
> different this time and rebuilt the compiler tools using RSB.
> vii) Now the directory structure under $HOME/development/rtems_dev/ looked 
> like:
>   | rtems-4.10.2
>   | 4.10
>   | src/rsb
>   | kernel/pc386
> I also used this command: "export 
> PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
> vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
> "./bootstrap -c && 
> $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
> vi) After this I went insid directory 
> $HOME/development/rtems_dev/kernel/pc-386
> vii) Inside pc-386, I used the following command:
> ''$HOME/development/rtems_dev/rtems-4.10.2/configure --target=i386-rtems4.10 
> --disable-posix  --enable-rtemsbsp=pc386 --enable-tests=samples 
> --prefix=/home/development/rtems_dev/rtems-4.10.2 --enable-cxx"
> viii) Then I entered the make command which ran successfully and the make 
> install was also successful.
>
> So all the errors were resolved and I moved on to build EPICS now for RTEMS 
> 4.10.
> I also used this command:
> '''export 
> RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
> Location of epics-base in my system is as follows:
> "$HOME/development/EPICS/epics-base"
>
> After this, I followed the tutorial you sent to build EPICS for rterms-4.10 
> for pc-386 which is:
>>
>> Very roughly:
>> git clone —recursive epics-base
>>
>> in epics-base/configure/CONFIG_SITE
>> set
>> CROSS_COMPILER_TARGET_ARCHS=
>
>What I entered:
>CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386
>>
>> e.g. RTEMS-pc386
>> or RTEMS-xilinx_zynq_a9_qemu
>>
>> in epics-base/configure/os there must be a file for the target used,
>> e.g.
>> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>> or
>> CONFIG.Common.RTEMS-pc386
>
> Checked.  CONFIG.Common.RTEMS-pc386 was there
>>
>>
>> Then you have to set in configure/os/CONFIG_SITE.Common.RTEMS
>> where to find RTEMS:
>>
>> # Where to find RTEMS
>> #
>> # APS:
>> #RTEMS_VERSION = 4.10.2
>> #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>
>
> In my system, I entered this:
> #APS
> RTEMS_VERSION = 4.10
> RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)
>
> I followed the above instructions and used the 'make' command.
>
>
> While the earlier errors are resolved, The latest error that I have 
> encountered is this after using make command.:
>
> "...Info':
> /home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.RTEMS-pc386/../osi/os/RTEMS/osdThread.c:747:
>  undefined reference to `pthread_getschedparam'
> collect2: ld returned 1 exit status
> ../../../../configure/RULES_BUILD:212: recipe for target 'libComTestHarness' 
> failed
> make[4]: *** [libComTestHarness] Error 1
> make[4]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/test/O.RTEMS-pc386'
> ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' 
> failed
> make[3]: *** [install.RTEMS-pc386] Error 2
> make[3]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/test'
> ../../configure/RULES_DIRS:85: recipe for target 'test.install' failed
> make[2]: *** [test.install] Error 2
> make[2]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
> ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
> make[1]: *** [libcom.install] Error 2
> make[1]: Leaving directory 
> '/home/mritunjay/development/EPICS/epics-base/modules'
> 

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

[Mritunjay Sharma]

Hello Heinz and everyone,

Thank you so much, with this email, I will try to clear all the things, and
what is the status for now.

First. let me tell you the current status: Vijay helped me last night in an
offlist discussion to clear the confusions which
I was having (I will mention them below) due to which I was able to build
and install RTEMS 4.10 for pc386 successfully.
With that, all my previous errors were resolved. Below is the detail of all
the steps, I followed.

Let me tell that my development environment was earlier set up for RTEMS5.
For building EPICS with RTEMS,
I thought it will be right to first build RTEMS 4.10 for pc386.

In order to do that, I made the directory

i) $HOME/development/rtems_dev
ii) I extracted rtems-4.10.2 from here
https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/
iii)I created another directory rtems_dev/src
iv)Inside src, I cloned rsb and moved to 4.10 branch.
v) After performing checks, I entered to rsb/rtems and used this command:
'../source-builder/sb-set-builder
--prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'
Even though the build completed successfully, this was the point where I
made the error. I used the RTEMS source as the prefix which
was causing all the problems.
vi) After the discussion with Vijay and getting cleared, I deleted
everything except the RTEMS RSB and restarted the process with prefix and
source
different this time and rebuilt the compiler tools using RSB.
vii) Now the directory structure under $HOME/development/rtems_dev/ looked
like:
  | rtems-4.10.2
  | 4.10
  | src/rsb
  | kernel/pc386
I also used this command: "export
PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"
vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:
"./bootstrap -c &&
$HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"
vi) After this I went
insid directory $HOME/development/rtems_dev/kernel/pc-386
vii) Inside pc-386, I used the following command:
''$HOME/development/rtems_dev/rtems-4.10.2/configure
--target=i386-rtems4.10 --disable-posix  --enable-rtemsbsp=pc386
--enable-tests=samples --prefix=/home/development/rtems_dev/rtems-4.10.2
--enable-cxx"
viii) Then I entered the make command which ran successfully and the make
install was also successful.

So all the errors were resolved and I moved on to build EPICS now for RTEMS
4.10.
I also used this command:
'''export
RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''
Location of epics-base in my system is as follows:
"$HOME/development/EPICS/epics-base"

After this, I followed the tutorial you sent to build EPICS for rterms-4.10
for pc-386 which is:

> Very roughly:
> git clone —recursive epics-base
>
> in epics-base/configure/CONFIG_SITE
> set
> CROSS_COMPILER_TARGET_ARCHS=
>
   What I entered:
   CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386

> e.g. RTEMS-pc386
> or RTEMS-xilinx_zynq_a9_qemu
>
> in epics-base/configure/os there must be a file for the target used,
> e.g.
> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
> or
> CONFIG.Common.RTEMS-pc386
>
Checked.  CONFIG.Common.RTEMS-pc386 was there

>
> Then you have to set in configure/os/CONFIG_SITE.Common.RTEMS
> where to find RTEMS:
>
> # Where to find RTEMS
> #
> # APS:
> #RTEMS_VERSION = 4.10.2
> #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)


In my system, I entered this:
#APS
RTEMS_VERSION = 4.10
RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)

I followed the above instructions and used the 'make' command.


While the earlier errors are resolved, The latest error that I have
encountered is this after using make command.:

"...Info':
/home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.RTEMS-pc386/../osi/os/RTEMS/osdThread.c:747:
undefined reference to `pthread_getschedparam'
collect2: ld returned 1 exit status
../../../../configure/RULES_BUILD:212: recipe for target
'libComTestHarness' failed
make[4]: *** [libComTestHarness] Error 1
make[4]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/test/O.RTEMS-pc386'
../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386'
failed
make[3]: *** [install.RTEMS-pc386] Error 2
make[3]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom/test'
../../configure/RULES_DIRS:85: recipe for target 'test.install' failed
make[2]: *** [test.install] Error 2
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules/libcom'
../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
make[1]: *** [libcom.install] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/modules'
configure/RULES_DIRS:85: recipe for target 'modules.install' failed
make: *** [modules.install] Error 2"

I hope this time I was explicit in writing what I did and what error I am
facing as of now. It would be kind
of you to guide where I am going wrong.

Thanks,
Mritunjay





On Fri, Jul 3, 2020 at 

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

[Chris Johns]

On 3/7/20 9:01 am, Mritunjay Sharma wrote:
> Thank you so much Gedare, I think the problem was with confusion related to 
> prefix and source being the same which created a lot of problems. 
> 
> I just had an offlist discussion with Vijay and he has cleared all my doubts 
> and
> the mistakes I was making. The problem as of now seems to be resolved. 

Vijay, thanks for helping and Mritunjay thank you for letting us know.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Mritunjay Sharma]

Thank you so much Gedare, I think the problem was with confusion related to
prefix and source being the same which created a lot of problems.

I just had an offlist discussion with Vijay and he has cleared all my
doubts and
the mistakes I was making. The problem as of now seems to be resolved.

I will continue the updates later today.

Thanks,
Mritunjay
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Gedare Bloom]

On Thu, Jul 2, 2020 at 2:52 PM Mritunjay Sharma
 wrote:
>
>
>
> On Fri, Jul 3, 2020 at 1:59 AM Vijay Kumar Banerjee  wrote:
>>
>> On Fri, Jul 3, 2020 at 1:41 AM Mritunjay Sharma
>>  wrote:
>> >
>> >
>> >
>> > On Fri, Jul 3, 2020 at 12:21 AM Vijay Kumar Banerjee  
>> > wrote:
>> >>
>> >> On Fri, Jul 3, 2020 at 12:15 AM Mritunjay Sharma
>> >>  wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee  
>> >> > wrote:
>> >> >>
>> >> >> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
>> >> >>  wrote:
>> >> >> >
>> >> >> > I guess the problem can be with my using 'sudo' here
>> >> >> > but without using sudo and directly using 'make install',
>> >> >> > the process stops all the more early with the following error:
>> >> >> >
>> >> >>
>> >> >> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
>> >> >
>> >> >
>> >> > Thank you so much, I tried this but again got the earlier error.
>> >> I should have written it explicitly, sorry for the confusion.
>> >>
>> >> After doing chmod, you have to run `make install` without sudo. The
>> >> error you're facing with sudo is because the PATH variable for the
>> >> root user does not include  the rtems toolchain bin directory hence
>> >> it's returning "command not found".
>> >>
>> >> In the next try you got "permission denied" errors because there's no
>> >> executing permission for the tools directory. By doing chmod, you
>> >> added the execute permission (+x) and now you can run make without
>> >> sudo.
>> >>
>> >> Best regards,
>> >> Vijay
>> >
>> >
>> > Thank you so much for this really nice explanation. As explained by you, I 
>> > tried again by first doing
>> > 'sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/' and then using 
>> > 'make install'  without 'sudo',
>> > however, I am still getting the 'permission denied error'.
>>
>> Seems like you were not able to delete either. You'll have to add
>> write permission as well
>> `chmod +w /YOUR_FOLDER`
>>
>> > Do I need to have rebuild the tools as well using RSB and then try again?
>> No, that won't be needed. You probably built all the tools as a
>> superuser, that's why the permissions are restrictive, chmod will fix
>> that.
>
>
> I tried 'sudo chmod +w /home/development/rtems_dev/rtems-4.10.2/ ' but 
> unfortunately the 'permission denied' error
> still remains after using 'make install' :(
>
I see several problems here.

Your username appears to be mritunjay

/home/development is not correct, that place probably doesn't exist

I think you mean /home/mritunjay/development?

You shouldn't need to use sudo if your build and install paths are in
directories owned by your user. That is preferred anyway, since sudo
can mess things up badly for you.

> Thanks,
> Mritunjay
> '
>>
>> >>
>> >> >>
>> >> >>
>> >> >> > "Making install in make
>> >> >> > make[1]: Entering directory 
>> >> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> >> > make[2]: Entering directory 
>> >> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> >> > make[2]: Nothing to be done for 'install-exec-am'.
>> >> >> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
>> >> >> >  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg 
>> >> >> > '/home/development/rtems_dev/rtems-4.10.2/make'
>> >> >> > /usr/bin/install: cannot remove 
>> >> >> > '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission 
>> >> >> > denied
>> >> >> > /usr/bin/install: cannot remove 
>> >> >> > '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission 
>> >> >> > denied
>> >> >> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
>> >> >> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
>> >> >> > make[2]: Leaving directory 
>> >> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> >> > Makefile:379: recipe for target 'install-am' failed
>> >> >> > make[1]: *** [install-am] Error 2
>> >> >> > make[1]: Leaving directory 
>> >> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> >> > Makefile:304: recipe for target 'install-recursive' failed
>> >> >> > make: *** [install-recursive] Error 1"
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma 
>> >> >> >  wrote:
>> >> >> >>
>> >> >> >> Hello Heinz and everyone,
>> >> >> >>
>> >> >> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot 
>> >> >> >> and saved a lot of time.
>> >> >> >> Though in all this it was a good learning experience for how to 
>> >> >> >> build the compiler
>> >> >> >> tools manually too :-)
>> >> >> >>
>> >> >> >> The make was successful this time and the previous error was 
>> >> >> >> resolved but after the make while using 'sudo make install', I have 
>> >> >> >> got another error as following:
>> >> >> >> " ...( cd 
>> >> >> >> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' 
>> >> >> >> && 

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

[Mritunjay Sharma]

On Fri, Jul 3, 2020 at 1:59 AM Vijay Kumar Banerjee  wrote:

> On Fri, Jul 3, 2020 at 1:41 AM Mritunjay Sharma
>  wrote:
> >
> >
> >
> > On Fri, Jul 3, 2020 at 12:21 AM Vijay Kumar Banerjee 
> wrote:
> >>
> >> On Fri, Jul 3, 2020 at 12:15 AM Mritunjay Sharma
> >>  wrote:
> >> >
> >> >
> >> >
> >> > On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee 
> wrote:
> >> >>
> >> >> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
> >> >>  wrote:
> >> >> >
> >> >> > I guess the problem can be with my using 'sudo' here
> >> >> > but without using sudo and directly using 'make install',
> >> >> > the process stops all the more early with the following error:
> >> >> >
> >> >>
> >> >> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
> >> >
> >> >
> >> > Thank you so much, I tried this but again got the earlier error.
> >> I should have written it explicitly, sorry for the confusion.
> >>
> >> After doing chmod, you have to run `make install` without sudo. The
> >> error you're facing with sudo is because the PATH variable for the
> >> root user does not include  the rtems toolchain bin directory hence
> >> it's returning "command not found".
> >>
> >> In the next try you got "permission denied" errors because there's no
> >> executing permission for the tools directory. By doing chmod, you
> >> added the execute permission (+x) and now you can run make without
> >> sudo.
> >>
> >> Best regards,
> >> Vijay
> >
> >
> > Thank you so much for this really nice explanation. As explained by you,
> I tried again by first doing
> > 'sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/' and then using
> 'make install'  without 'sudo',
> > however, I am still getting the 'permission denied error'.
>
> Seems like you were not able to delete either. You'll have to add
> write permission as well
> `chmod +w /YOUR_FOLDER`
>
> > Do I need to have rebuild the tools as well using RSB and then try again?
> No, that won't be needed. You probably built all the tools as a
> superuser, that's why the permissions are restrictive, chmod will fix
> that.
>

I tried 'sudo chmod +w /home/development/rtems_dev/rtems-4.10.2/ ' but
unfortunately the 'permission denied' error
still remains after using 'make install' :(

Thanks,
Mritunjay
'

> >>
> >> >>
> >> >>
> >> >> > "Making install in make
> >> >> > make[1]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> >> > make[2]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> >> > make[2]: Nothing to be done for 'install-exec-am'.
> >> >> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
> >> >> >  /usr/bin/install -c -m 644 ../../make/main.cfg
> ../../make/leaf.cfg '/home/development/rtems_dev/rtems-4.10.2/make'
> >> >> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
> >> >> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
> >> >> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA'
> failed
> >> >> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
> >> >> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> >> > Makefile:379: recipe for target 'install-am' failed
> >> >> > make[1]: *** [install-am] Error 2
> >> >> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> >> > Makefile:304: recipe for target 'install-recursive' failed
> >> >> > make: *** [install-recursive] Error 1"
> >> >> >
> >> >> >
> >> >> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >> >> >>
> >> >> >> Hello Heinz and everyone,
> >> >> >>
> >> >> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a
> lot and saved a lot of time.
> >> >> >> Though in all this it was a good learning experience for how to
> build the compiler
> >> >> >> tools manually too :-)
> >> >> >>
> >> >> >> The make was successful this time and the previous error was
> resolved but after the make while using 'sudo make install', I have got
> another error as following:
> >> >> >> " ...( cd
> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' &&
> i386-rtems4.10-ranlib libsapi.a )
> >> >> >> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
> >> >> >> Makefile:366: recipe for target 'install-project_libLIBRARIES'
> failed
> >> >> >> make[5]: *** [install-project_libLIBRARIES] Error 127
> >> >> >> make[5]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> >> >> Makefile:952: recipe for target 'install-am' failed
> >> >> >> make[4]: *** [install-am] Error 2
> >> >> >> make[4]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> >> >> Makefile:785: recipe for target 'install-recursive' 

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

[Vijay Kumar Banerjee]

On Fri, Jul 3, 2020 at 1:41 AM Mritunjay Sharma
 wrote:
>
>
>
> On Fri, Jul 3, 2020 at 12:21 AM Vijay Kumar Banerjee  wrote:
>>
>> On Fri, Jul 3, 2020 at 12:15 AM Mritunjay Sharma
>>  wrote:
>> >
>> >
>> >
>> > On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee  
>> > wrote:
>> >>
>> >> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
>> >>  wrote:
>> >> >
>> >> > I guess the problem can be with my using 'sudo' here
>> >> > but without using sudo and directly using 'make install',
>> >> > the process stops all the more early with the following error:
>> >> >
>> >>
>> >> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
>> >
>> >
>> > Thank you so much, I tried this but again got the earlier error.
>> I should have written it explicitly, sorry for the confusion.
>>
>> After doing chmod, you have to run `make install` without sudo. The
>> error you're facing with sudo is because the PATH variable for the
>> root user does not include  the rtems toolchain bin directory hence
>> it's returning "command not found".
>>
>> In the next try you got "permission denied" errors because there's no
>> executing permission for the tools directory. By doing chmod, you
>> added the execute permission (+x) and now you can run make without
>> sudo.
>>
>> Best regards,
>> Vijay
>
>
> Thank you so much for this really nice explanation. As explained by you, I 
> tried again by first doing
> 'sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/' and then using 
> 'make install'  without 'sudo',
> however, I am still getting the 'permission denied error'.

Seems like you were not able to delete either. You'll have to add
write permission as well
`chmod +w /YOUR_FOLDER`

> Do I need to have rebuild the tools as well using RSB and then try again?
No, that won't be needed. You probably built all the tools as a
superuser, that's why the permissions are restrictive, chmod will fix
that.
>>
>> >>
>> >>
>> >> > "Making install in make
>> >> > make[1]: Entering directory 
>> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> > make[2]: Entering directory 
>> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> > make[2]: Nothing to be done for 'install-exec-am'.
>> >> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
>> >> >  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg 
>> >> > '/home/development/rtems_dev/rtems-4.10.2/make'
>> >> > /usr/bin/install: cannot remove 
>> >> > '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission 
>> >> > denied
>> >> > /usr/bin/install: cannot remove 
>> >> > '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission 
>> >> > denied
>> >> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
>> >> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
>> >> > make[2]: Leaving directory 
>> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> > Makefile:379: recipe for target 'install-am' failed
>> >> > make[1]: *** [install-am] Error 2
>> >> > make[1]: Leaving directory 
>> >> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> >> > Makefile:304: recipe for target 'install-recursive' failed
>> >> > make: *** [install-recursive] Error 1"
>> >> >
>> >> >
>> >> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma 
>> >> >  wrote:
>> >> >>
>> >> >> Hello Heinz and everyone,
>> >> >>
>> >> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and 
>> >> >> saved a lot of time.
>> >> >> Though in all this it was a good learning experience for how to build 
>> >> >> the compiler
>> >> >> tools manually too :-)
>> >> >>
>> >> >> The make was successful this time and the previous error was resolved 
>> >> >> but after the make while using 'sudo make install', I have got another 
>> >> >> error as following:
>> >> >> " ...( cd 
>> >> >> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' && 
>> >> >> i386-rtems4.10-ranlib libsapi.a )
>> >> >> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
>> >> >> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
>> >> >> make[5]: *** [install-project_libLIBRARIES] Error 127
>> >> >> make[5]: Leaving directory 
>> >> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> >> >> Makefile:952: recipe for target 'install-am' failed
>> >> >> make[4]: *** [install-am] Error 2
>> >> >> make[4]: Leaving directory 
>> >> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> >> >> Makefile:785: recipe for target 'install-recursive' failed
>> >> >> make[3]: *** [install-recursive] Error 1
>> >> >> make[3]: Leaving directory 
>> >> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
>> >> >> Makefile:425: recipe for target 'install-recursive' failed
>> >> >> make[2]: *** [install-recursive] Error 1
>> >> >> 

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

[Mritunjay Sharma]

On Fri, Jul 3, 2020 at 12:21 AM Vijay Kumar Banerjee 
wrote:

> On Fri, Jul 3, 2020 at 12:15 AM Mritunjay Sharma
>  wrote:
> >
> >
> >
> > On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee 
> wrote:
> >>
> >> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > I guess the problem can be with my using 'sudo' here
> >> > but without using sudo and directly using 'make install',
> >> > the process stops all the more early with the following error:
> >> >
> >>
> >> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
> >
> >
> > Thank you so much, I tried this but again got the earlier error.
> I should have written it explicitly, sorry for the confusion.
>
> After doing chmod, you have to run `make install` without sudo. The
> error you're facing with sudo is because the PATH variable for the
> root user does not include  the rtems toolchain bin directory hence
> it's returning "command not found".
>
> In the next try you got "permission denied" errors because there's no
> executing permission for the tools directory. By doing chmod, you
> added the execute permission (+x) and now you can run make without
> sudo.
>
> Best regards,
> Vijay
>

Thank you so much for this really nice explanation. As explained by you, I
tried again by first doing
'sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/' and then using
'make install'  without 'sudo',
however, I am still getting the 'permission denied error'.
Do I need to have rebuild the tools as well using RSB and then try again?

> >>
> >>
> >> > "Making install in make
> >> > make[1]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> > make[2]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> > make[2]: Nothing to be done for 'install-exec-am'.
> >> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
> >> >  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg
> '/home/development/rtems_dev/rtems-4.10.2/make'
> >> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
> >> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
> >> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
> >> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
> >> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> > Makefile:379: recipe for target 'install-am' failed
> >> > make[1]: *** [install-am] Error 2
> >> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> >> > Makefile:304: recipe for target 'install-recursive' failed
> >> > make: *** [install-recursive] Error 1"
> >> >
> >> >
> >> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >> >>
> >> >> Hello Heinz and everyone,
> >> >>
> >> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot
> and saved a lot of time.
> >> >> Though in all this it was a good learning experience for how to
> build the compiler
> >> >> tools manually too :-)
> >> >>
> >> >> The make was successful this time and the previous error was
> resolved but after the make while using 'sudo make install', I have got
> another error as following:
> >> >> " ...( cd
> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' &&
> i386-rtems4.10-ranlib libsapi.a )
> >> >> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
> >> >> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
> >> >> make[5]: *** [install-project_libLIBRARIES] Error 127
> >> >> make[5]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> >> Makefile:952: recipe for target 'install-am' failed
> >> >> make[4]: *** [install-am] Error 2
> >> >> make[4]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> >> Makefile:785: recipe for target 'install-recursive' failed
> >> >> make[3]: *** [install-recursive] Error 1
> >> >> make[3]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
> >> >> Makefile:425: recipe for target 'install-recursive' failed
> >> >> make[2]: *** [install-recursive] Error 1
> >> >> make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
> >> >> Makefile:286: recipe for target 'install-recursive' failed
> >> >> make[1]: *** [install-recursive] Error 1
> >> >> make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> >> >> Makefile:304: recipe for target 'install-recursive' failed
> >> >> make: *** [install-recursive] Error 1"
> >> >>
> >> >> I am trying to figure out on what can be the reason behind this, it
> 

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

[Vijay Kumar Banerjee]

On Fri, Jul 3, 2020 at 12:15 AM Mritunjay Sharma
 wrote:
>
>
>
> On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee  wrote:
>>
>> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
>>  wrote:
>> >
>> > I guess the problem can be with my using 'sudo' here
>> > but without using sudo and directly using 'make install',
>> > the process stops all the more early with the following error:
>> >
>>
>> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
>
>
> Thank you so much, I tried this but again got the earlier error.
I should have written it explicitly, sorry for the confusion.

After doing chmod, you have to run `make install` without sudo. The
error you're facing with sudo is because the PATH variable for the
root user does not include  the rtems toolchain bin directory hence
it's returning "command not found".

In the next try you got "permission denied" errors because there's no
executing permission for the tools directory. By doing chmod, you
added the execute permission (+x) and now you can run make without
sudo.

Best regards,
Vijay
>>
>>
>> > "Making install in make
>> > make[1]: Entering directory 
>> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> > make[2]: Entering directory 
>> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> > make[2]: Nothing to be done for 'install-exec-am'.
>> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
>> >  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg 
>> > '/home/development/rtems_dev/rtems-4.10.2/make'
>> > /usr/bin/install: cannot remove 
>> > '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
>> > /usr/bin/install: cannot remove 
>> > '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
>> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
>> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
>> > make[2]: Leaving directory 
>> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> > Makefile:379: recipe for target 'install-am' failed
>> > make[1]: *** [install-am] Error 2
>> > make[1]: Leaving directory 
>> > '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
>> > Makefile:304: recipe for target 'install-recursive' failed
>> > make: *** [install-recursive] Error 1"
>> >
>> >
>> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma 
>> >  wrote:
>> >>
>> >> Hello Heinz and everyone,
>> >>
>> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and 
>> >> saved a lot of time.
>> >> Though in all this it was a good learning experience for how to build the 
>> >> compiler
>> >> tools manually too :-)
>> >>
>> >> The make was successful this time and the previous error was resolved but 
>> >> after the make while using 'sudo make install', I have got another error 
>> >> as following:
>> >> " ...( cd 
>> >> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' && 
>> >> i386-rtems4.10-ranlib libsapi.a )
>> >> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
>> >> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
>> >> make[5]: *** [install-project_libLIBRARIES] Error 127
>> >> make[5]: Leaving directory 
>> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> >> Makefile:952: recipe for target 'install-am' failed
>> >> make[4]: *** [install-am] Error 2
>> >> make[4]: Leaving directory 
>> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> >> Makefile:785: recipe for target 'install-recursive' failed
>> >> make[3]: *** [install-recursive] Error 1
>> >> make[3]: Leaving directory 
>> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
>> >> Makefile:425: recipe for target 'install-recursive' failed
>> >> make[2]: *** [install-recursive] Error 1
>> >> make[2]: Leaving directory 
>> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
>> >> Makefile:286: recipe for target 'install-recursive' failed
>> >> make[1]: *** [install-recursive] Error 1
>> >> make[1]: Leaving directory 
>> >> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
>> >> Makefile:304: recipe for target 'install-recursive' failed
>> >> make: *** [install-recursive] Error 1"
>> >>
>> >> I am trying to figure out on what can be the reason behind this, it will 
>> >> be kind of
>> >> you all to guide help this fix.
>> >>
>> >> Thanks,
>> >> Mritunjay
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Jul 2, 2020 at 9:59 AM Heinz Junkes  
>> >> wrote:
>> >>>
>> >>> Hello, Mritunjay,
>> >>>
>> >>> why not use the RTEMS Resource builder for 4.10 ?
>> >>> Heinz
>> >>>
>> >>>
>> >>> > On 1. Jul 2020, at 20:03, Mritunjay Sharma 
>> >>> >  wrote:
>> >>> >
>> >>> > Hi Gedare,
>> >>> >
>> >>> > Thank you so much, since I had the experience of RSB toolchain till 
>> >>> > now,
>> >>> 

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

[Mritunjay Sharma]

On Fri, Jul 3, 2020 at 12:10 AM Vijay Kumar Banerjee 
wrote:

> On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
>  wrote:
> >
> > I guess the problem can be with my using 'sudo' here
> > but without using sudo and directly using 'make install',
> > the process stops all the more early with the following error:
> >
>
> Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`
>

Thank you so much, I tried this but again got the earlier error.

>
> > "Making install in make
> > make[1]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> > make[2]: Entering directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> > make[2]: Nothing to be done for 'install-exec-am'.
> >  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
> >  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg
> '/home/development/rtems_dev/rtems-4.10.2/make'
> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
> > /usr/bin/install: cannot remove
> '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
> > Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
> > make[2]: *** [install-dist_rtems_makeDATA] Error 1
> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> > Makefile:379: recipe for target 'install-am' failed
> > make[1]: *** [install-am] Error 2
> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> > Makefile:304: recipe for target 'install-recursive' failed
> > make: *** [install-recursive] Error 1"
> >
> >
> > On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >> Hello Heinz and everyone,
> >>
> >> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and
> saved a lot of time.
> >> Though in all this it was a good learning experience for how to build
> the compiler
> >> tools manually too :-)
> >>
> >> The make was successful this time and the previous error was resolved
> but after the make while using 'sudo make install', I have got another
> error as following:
> >> " ...( cd
> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' &&
> i386-rtems4.10-ranlib libsapi.a )
> >> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
> >> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
> >> make[5]: *** [install-project_libLIBRARIES] Error 127
> >> make[5]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> Makefile:952: recipe for target 'install-am' failed
> >> make[4]: *** [install-am] Error 2
> >> make[4]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> >> Makefile:785: recipe for target 'install-recursive' failed
> >> make[3]: *** [install-recursive] Error 1
> >> make[3]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
> >> Makefile:425: recipe for target 'install-recursive' failed
> >> make[2]: *** [install-recursive] Error 1
> >> make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
> >> Makefile:286: recipe for target 'install-recursive' failed
> >> make[1]: *** [install-recursive] Error 1
> >> make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> >> Makefile:304: recipe for target 'install-recursive' failed
> >> make: *** [install-recursive] Error 1"
> >>
> >> I am trying to figure out on what can be the reason behind this, it
> will be kind of
> >> you all to guide help this fix.
> >>
> >> Thanks,
> >> Mritunjay
> >>
> >>
> >>
> >>
> >> On Thu, Jul 2, 2020 at 9:59 AM Heinz Junkes 
> wrote:
> >>>
> >>> Hello, Mritunjay,
> >>>
> >>> why not use the RTEMS Resource builder for 4.10 ?
> >>> Heinz
> >>>
> >>>
> >>> > On 1. Jul 2020, at 20:03, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>> >
> >>> > Hi Gedare,
> >>> >
> >>> > Thank you so much, since I had the experience of RSB toolchain till
> now,
> >>> > I forgot to build the RTEMS compiler toolchain.
> >>> >
> >>> > Today's update is also this that I spent the day figuring out how
> >>> > to build it manually and got some really amazing blogs
> >>> > which have helped me (though they were a bit difficult to find
> because most pages have been
> >>> > relocated).
> >>> > Sharing the resources which I have used today and that are helping
> me build RTEMS compiler toolchain for 4.10.
> >>> >
> >>> >
> http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
> >>> >
> https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
> >>> > https://ftp.rtems.org/pub/rtems/releases/4.10/tools/
> >>> >
> >>> > I am now 

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

[Vijay Kumar Banerjee]

On Fri, Jul 3, 2020 at 12:00 AM Mritunjay Sharma
 wrote:
>
> I guess the problem can be with my using 'sudo' here
> but without using sudo and directly using 'make install',
> the process stops all the more early with the following error:
>

Please try `sudo chmod +x $HOME/development/rtems_dev/rtems-4.10.2/`

> "Making install in make
> make[1]: Entering directory 
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> make[2]: Entering directory 
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> make[2]: Nothing to be done for 'install-exec-am'.
>  /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
>  /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg 
> '/home/development/rtems_dev/rtems-4.10.2/make'
> /usr/bin/install: cannot remove 
> '/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
> /usr/bin/install: cannot remove 
> '/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
> Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
> make[2]: *** [install-dist_rtems_makeDATA] Error 1
> make[2]: Leaving directory 
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> Makefile:379: recipe for target 'install-am' failed
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory 
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
> Makefile:304: recipe for target 'install-recursive' failed
> make: *** [install-recursive] Error 1"
>
>
> On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma 
>  wrote:
>>
>> Hello Heinz and everyone,
>>
>> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and saved 
>> a lot of time.
>> Though in all this it was a good learning experience for how to build the 
>> compiler
>> tools manually too :-)
>>
>> The make was successful this time and the previous error was resolved but 
>> after the make while using 'sudo make install', I have got another error as 
>> following:
>> " ...( cd 
>> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' && 
>> i386-rtems4.10-ranlib libsapi.a )
>> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
>> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
>> make[5]: *** [install-project_libLIBRARIES] Error 127
>> make[5]: Leaving directory 
>> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> Makefile:952: recipe for target 'install-am' failed
>> make[4]: *** [install-am] Error 2
>> make[4]: Leaving directory 
>> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
>> Makefile:785: recipe for target 'install-recursive' failed
>> make[3]: *** [install-recursive] Error 1
>> make[3]: Leaving directory 
>> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
>> Makefile:425: recipe for target 'install-recursive' failed
>> make[2]: *** [install-recursive] Error 1
>> make[2]: Leaving directory 
>> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
>> Makefile:286: recipe for target 'install-recursive' failed
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory 
>> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
>> Makefile:304: recipe for target 'install-recursive' failed
>> make: *** [install-recursive] Error 1"
>>
>> I am trying to figure out on what can be the reason behind this, it will be 
>> kind of
>> you all to guide help this fix.
>>
>> Thanks,
>> Mritunjay
>>
>>
>>
>>
>> On Thu, Jul 2, 2020 at 9:59 AM Heinz Junkes  wrote:
>>>
>>> Hello, Mritunjay,
>>>
>>> why not use the RTEMS Resource builder for 4.10 ?
>>> Heinz
>>>
>>>
>>> > On 1. Jul 2020, at 20:03, Mritunjay Sharma  
>>> > wrote:
>>> >
>>> > Hi Gedare,
>>> >
>>> > Thank you so much, since I had the experience of RSB toolchain till now,
>>> > I forgot to build the RTEMS compiler toolchain.
>>> >
>>> > Today's update is also this that I spent the day figuring out how
>>> > to build it manually and got some really amazing blogs
>>> > which have helped me (though they were a bit difficult to find because 
>>> > most pages have been
>>> > relocated).
>>> > Sharing the resources which I have used today and that are helping me 
>>> > build RTEMS compiler toolchain for 4.10.
>>> >
>>> > http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
>>> > https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
>>> > https://ftp.rtems.org/pub/rtems/releases/4.10/tools/
>>> >
>>> > I am now applying patches for gdb, gcc, binutils and most
>>> > probably hope that the build will be successful.
>>> >
>>> > As suggested by Heinz, I am improving the blog as well and will post the 
>>> > updated and better
>>> > version of blog by Friday.
>>> >
>>> > Thanks,
>>> > Mritunjay
>>> >
>>> > On Wed, Jul 1, 2020 at 9:25 AM Gedare Bloom  

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

[Mritunjay Sharma]

I guess the problem can be with my using 'sudo' here
but without using sudo and directly using 'make install',
the process stops all the more early with the following error:

"Making install in make
make[1]: Entering directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
make[2]: Entering directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
make[2]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/home/development/rtems_dev/rtems-4.10.2/make'
 /usr/bin/install -c -m 644 ../../make/main.cfg ../../make/leaf.cfg
'/home/development/rtems_dev/rtems-4.10.2/make'
/usr/bin/install: cannot remove
'/home/development/rtems_dev/rtems-4.10.2/make/main.cfg': Permission denied
/usr/bin/install: cannot remove
'/home/development/rtems_dev/rtems-4.10.2/make/leaf.cfg': Permission denied
Makefile:265: recipe for target 'install-dist_rtems_makeDATA' failed
make[2]: *** [install-dist_rtems_makeDATA] Error 1
make[2]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
Makefile:379: recipe for target 'install-am' failed
make[1]: *** [install-am] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/make'
Makefile:304: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1"


On Thu, Jul 2, 2020 at 11:47 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Hello Heinz and everyone,
>
> Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and
> saved a lot of time.
> Though in all this it was a good learning experience for how to build the
> compiler
> tools manually too :-)
>
> The make was successful this time and the previous error was resolved but
> after the make while using 'sudo make install', I have got another error as
> following:
> " ...( cd
> '/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' &&
> i386-rtems4.10-ranlib libsapi.a )
> /bin/bash: line 5: i386-rtems4.10-ranlib: command not found
> Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
> make[5]: *** [install-project_libLIBRARIES] Error 127
> make[5]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> Makefile:952: recipe for target 'install-am' failed
> make[4]: *** [install-am] Error 2
> make[4]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
> Makefile:785: recipe for target 'install-recursive' failed
> make[3]: *** [install-recursive] Error 1
> make[3]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
> Makefile:425: recipe for target 'install-recursive' failed
> make[2]: *** [install-recursive] Error 1
> make[2]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
> Makefile:286: recipe for target 'install-recursive' failed
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> '/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> Makefile:304: recipe for target 'install-recursive' failed
> make: *** [install-recursive] Error 1"
>
> I am trying to figure out on what can be the reason behind this, it will
> be kind of
> you all to guide help this fix.
>
> Thanks,
> Mritunjay
>
>
>
>
> On Thu, Jul 2, 2020 at 9:59 AM Heinz Junkes 
> wrote:
>
>> Hello, Mritunjay,
>>
>> why not use the RTEMS Resource builder for 4.10 ?
>> Heinz
>>
>>
>> > On 1. Jul 2020, at 20:03, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >
>> > Hi Gedare,
>> >
>> > Thank you so much, since I had the experience of RSB toolchain till
>> now,
>> > I forgot to build the RTEMS compiler toolchain.
>> >
>> > Today's update is also this that I spent the day figuring out how
>> > to build it manually and got some really amazing blogs
>> > which have helped me (though they were a bit difficult to find because
>> most pages have been
>> > relocated).
>> > Sharing the resources which I have used today and that are helping me
>> build RTEMS compiler toolchain for 4.10.
>> >
>> >
>> http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
>> >
>> https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
>> > https://ftp.rtems.org/pub/rtems/releases/4.10/tools/
>> >
>> > I am now applying patches for gdb, gcc, binutils and most
>> > probably hope that the build will be successful.
>> >
>> > As suggested by Heinz, I am improving the blog as well and will post
>> the updated and better
>> > version of blog by Friday.
>> >
>> > Thanks,
>> > Mritunjay
>> >
>> > On Wed, Jul 1, 2020 at 9:25 AM Gedare Bloom  wrote:
>> > On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
>> >  wrote:
>> > >
>> > > Hi Gedare,
>> > >
>> > > Thank you for the quick response, I tried using
>> --target=i386-rtems4.10, which again
>> > > gave me the same error.
>> > 

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

[Mritunjay Sharma]

Hello Heinz and everyone,

Thank you so much, using RTEMS RSB for 4.10 really helped me a lot and
saved a lot of time.
Though in all this it was a good learning experience for how to build the
compiler
tools manually too :-)

The make was successful this time and the previous error was resolved but
after the make while using 'sudo make install', I have got another error as
following:
" ...( cd
'/home/development/rtems_dev/rtems-4.10.2/i386-rtems4.10/pc386/lib' &&
i386-rtems4.10-ranlib libsapi.a )
/bin/bash: line 5: i386-rtems4.10-ranlib: command not found
Makefile:366: recipe for target 'install-project_libLIBRARIES' failed
make[5]: *** [install-project_libLIBRARIES] Error 127
make[5]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
Makefile:952: recipe for target 'install-am' failed
make[4]: *** [install-am] Error 2
make[4]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit/sapi'
Makefile:785: recipe for target 'install-recursive' failed
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386/cpukit'
Makefile:425: recipe for target 'install-recursive' failed
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c/pc386'
Makefile:286: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
'/home/mritunjay/development/rtems_dev/rtems-4.10.2/pc-386/i386-rtems4.10/c'
Makefile:304: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1"

I am trying to figure out on what can be the reason behind this, it will be
kind of
you all to guide help this fix.

Thanks,
Mritunjay




On Thu, Jul 2, 2020 at 9:59 AM Heinz Junkes 
wrote:

> Hello, Mritunjay,
>
> why not use the RTEMS Resource builder for 4.10 ?
> Heinz
>
>
> > On 1. Jul 2020, at 20:03, Mritunjay Sharma 
> wrote:
> >
> > Hi Gedare,
> >
> > Thank you so much, since I had the experience of RSB toolchain till now,
> > I forgot to build the RTEMS compiler toolchain.
> >
> > Today's update is also this that I spent the day figuring out how
> > to build it manually and got some really amazing blogs
> > which have helped me (though they were a bit difficult to find because
> most pages have been
> > relocated).
> > Sharing the resources which I have used today and that are helping me
> build RTEMS compiler toolchain for 4.10.
> >
> >
> http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
> >
> https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
> > https://ftp.rtems.org/pub/rtems/releases/4.10/tools/
> >
> > I am now applying patches for gdb, gcc, binutils and most
> > probably hope that the build will be successful.
> >
> > As suggested by Heinz, I am improving the blog as well and will post the
> updated and better
> > version of blog by Friday.
> >
> > Thanks,
> > Mritunjay
> >
> > On Wed, Jul 1, 2020 at 9:25 AM Gedare Bloom  wrote:
> > On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
> >  wrote:
> > >
> > > Hi Gedare,
> > >
> > > Thank you for the quick response, I tried using
> --target=i386-rtems4.10, which again
> > > gave me the same error.
> > >
> > Did you build an RTEMS compiler toolchain for 4.10? and install it to
> > a prefix in your $PATH?
> >
> > > "checking for RTEMS_CPU_MODEL... i386_fp
> > > checking for RTEMS_BSP_FAMILY... pc386
> > > checking for CPU_CFLAGS... (cached) -mtune=i386
> > > checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
> > > checking for style of include used by make... GNU
> > > checking for i386-rtems4.10-gcc... no
> > > configure: error: no acceptable cc found in $PATH
> > > Makefile:712: recipe for target 'pc386' failed
> > > make[2]: *** [pc386] Error 1
> > > make[2]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > > Makefile:257: recipe for target 'all-recursive' failed
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > > Makefile:275: recipe for target 'all-recursive' failed
> > > make: *** [all-recursive] Error 1"
> > >
> > > Mritunjay
> > >
> > > On Wed, Jul 1, 2020 at 3:48 AM Gedare Bloom  wrote:
> > >>
> > >>  Use --target=i386-rtems4.10 instead of  --target=i386-rtems
> > >>
> > >> Does this work with 4.10.3/4.10 HEAD?
> > >>
> > >> On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
> > >>  wrote:
> > >> >
> > >> > Hello everyone,
> > >> >
> > >> > I followed the documentation here
> https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
> and
> > >> > started building RTEMS (4.10.2) for target architecture: i386 and
> BSP: pc386. The configure seemed to be fine
> > >> > after entering the following 

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

[Heinz Junkes]

Hello, Mritunjay,

why not use the RTEMS Resource builder for 4.10 ?
Heinz


> On 1. Jul 2020, at 20:03, Mritunjay Sharma  
> wrote:
> 
> Hi Gedare, 
> 
> Thank you so much, since I had the experience of RSB toolchain till now, 
> I forgot to build the RTEMS compiler toolchain.
> 
> Today's update is also this that I spent the day figuring out how
> to build it manually and got some really amazing blogs
> which have helped me (though they were a bit difficult to find because most 
> pages have been
> relocated).
> Sharing the resources which I have used today and that are helping me build 
> RTEMS compiler toolchain for 4.10.
> 
> http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
> https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
> https://ftp.rtems.org/pub/rtems/releases/4.10/tools/
> 
> I am now applying patches for gdb, gcc, binutils and most
> probably hope that the build will be successful. 
> 
> As suggested by Heinz, I am improving the blog as well and will post the 
> updated and better
> version of blog by Friday. 
> 
> Thanks,
> Mritunjay
> 
> On Wed, Jul 1, 2020 at 9:25 AM Gedare Bloom  wrote:
> On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
>  wrote:
> >
> > Hi Gedare,
> >
> > Thank you for the quick response, I tried using --target=i386-rtems4.10, 
> > which again
> > gave me the same error.
> >
> Did you build an RTEMS compiler toolchain for 4.10? and install it to
> a prefix in your $PATH?
> 
> > "checking for RTEMS_CPU_MODEL... i386_fp
> > checking for RTEMS_BSP_FAMILY... pc386
> > checking for CPU_CFLAGS... (cached) -mtune=i386
> > checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
> > checking for style of include used by make... GNU
> > checking for i386-rtems4.10-gcc... no
> > configure: error: no acceptable cc found in $PATH
> > Makefile:712: recipe for target 'pc386' failed
> > make[2]: *** [pc386] Error 1
> > make[2]: Leaving directory 
> > '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > Makefile:257: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory 
> > '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > Makefile:275: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 1"
> >
> > Mritunjay
> >
> > On Wed, Jul 1, 2020 at 3:48 AM Gedare Bloom  wrote:
> >>
> >>  Use --target=i386-rtems4.10 instead of  --target=i386-rtems
> >>
> >> Does this work with 4.10.3/4.10 HEAD?
> >>
> >> On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > Hello everyone,
> >> >
> >> > I followed the documentation here 
> >> > https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
> >> >  and
> >> > started building RTEMS (4.10.2) for target architecture: i386 and BSP: 
> >> > pc386. The configure seemed to be fine
> >> > after entering the following command:
> >> > "../configure --target=i386-rtems --disable-posix --enable-cxx 
> >> > --enable-rtemsbsp=pc386 --enable-tests=samples 
> >> > --prefix=/home/development/rtems-4.10.2"
> >> >
> >> > However, the make failed with the following error: checking for 
> >> > i386-rtems-gcc... no
> >> > "configure: error: no acceptable cc found in $PATH
> >> > Makefile:712: recipe for target 'pc386' failed
> >> > make[2]: *** [pc386] Error 1
> >> > make[2]: Leaving directory 
> >> > '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> >> > Makefile:257: recipe for target 'all-recursive' failed
> >> > make[1]: *** [all-recursive] Error 1
> >> > make[1]: Leaving directory 
> >> > '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> >> > Makefile:275: recipe for target 'all-recursive' failed
> >> > make: *** [all-recursive] Error 1"
> >> >
> >> > I checked that gcc is already installed in /usr/bin/gcc.
> >> > So I am not able to figure out what exactly is causing the error.
> >> > Please help to figure out what is causing this and how it can be 
> >> > resolved.
> >> > I have attached the config log as well.
> >> >
> >> > Thanks
> >> > Mritunjay
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma 
> >> >  wrote:
> >> >>
> >> >>
> >> >> I mistakenly forgot to cc my other mentors.
> >> >>
> >> >> This is what I responded :
> >> >>
> >> >>> Hello Heinz,
> >> >>>
> >> >>> Pardon the mistake I did in haste,
> >> >>> as I advised by you I am now building it for RTEMS 4.10 and then I will
> >> >>> be reporting here shortly as the build completes.
> >> >>>
> >> >>> Thanks
> >> >>> Mritunjay.
> >> >>
> >> >>
> >> >> I am shortly sending the email for the progress I made after working on 
> >> >> above.
> >> >> Thanks
> >> >> Mritunjay
> >> >>
> >> >>
> >> >>
> >> >> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes  
> >> >> wrote:
> >> >>>
> >> >>> Hello, Mritunjay,
> >> >>>
> >> >>> the epics-base version in github does not work with RTEMS5 It needs my 
> >> >>> 

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

[Mritunjay Sharma]

Hi Gedare,

Thank you so much, since I had the experience of RSB toolchain till now,
I forgot to build the RTEMS compiler toolchain.

Today's update is also this that I spent the day figuring out how
to build it manually and got some really amazing blogs
which have helped me (though they were a bit difficult to find because most
pages have been
relocated).
Sharing the resources which I have used today and that are helping me build
RTEMS compiler toolchain for 4.10.

http://heshamelmatary.blogspot.com/2014/06/howto-build-rtems-tool-chain-for.html
https://docs.rtems.org/releases/4.5.0/rtemsdoc-4.5.0/share/rtemsdoc/html/started/started00040.html
https://ftp.rtems.org/pub/rtems/releases/4.10/tools/

I am now applying patches for gdb, gcc, binutils and most
probably hope that the build will be successful.

As suggested by Heinz, I am improving the blog as well and will post the
updated and better
version of blog by Friday.

Thanks,
Mritunjay

On Wed, Jul 1, 2020 at 9:25 AM Gedare Bloom  wrote:

> On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
>  wrote:
> >
> > Hi Gedare,
> >
> > Thank you for the quick response, I tried using --target=i386-rtems4.10,
> which again
> > gave me the same error.
> >
> Did you build an RTEMS compiler toolchain for 4.10? and install it to
> a prefix in your $PATH?
>
> > "checking for RTEMS_CPU_MODEL... i386_fp
> > checking for RTEMS_BSP_FAMILY... pc386
> > checking for CPU_CFLAGS... (cached) -mtune=i386
> > checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
> > checking for style of include used by make... GNU
> > checking for i386-rtems4.10-gcc... no
> > configure: error: no acceptable cc found in $PATH
> > Makefile:712: recipe for target 'pc386' failed
> > make[2]: *** [pc386] Error 1
> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > Makefile:257: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> > Makefile:275: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 1"
> >
> > Mritunjay
> >
> > On Wed, Jul 1, 2020 at 3:48 AM Gedare Bloom  wrote:
> >>
> >>  Use --target=i386-rtems4.10 instead of  --target=i386-rtems
> >>
> >> Does this work with 4.10.3/4.10 HEAD?
> >>
> >> On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > Hello everyone,
> >> >
> >> > I followed the documentation here
> https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
> and
> >> > started building RTEMS (4.10.2) for target architecture: i386 and
> BSP: pc386. The configure seemed to be fine
> >> > after entering the following command:
> >> > "../configure --target=i386-rtems --disable-posix --enable-cxx
> --enable-rtemsbsp=pc386 --enable-tests=samples
> --prefix=/home/development/rtems-4.10.2"
> >> >
> >> > However, the make failed with the following error: checking for
> i386-rtems-gcc... no
> >> > "configure: error: no acceptable cc found in $PATH
> >> > Makefile:712: recipe for target 'pc386' failed
> >> > make[2]: *** [pc386] Error 1
> >> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> >> > Makefile:257: recipe for target 'all-recursive' failed
> >> > make[1]: *** [all-recursive] Error 1
> >> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> >> > Makefile:275: recipe for target 'all-recursive' failed
> >> > make: *** [all-recursive] Error 1"
> >> >
> >> > I checked that gcc is already installed in /usr/bin/gcc.
> >> > So I am not able to figure out what exactly is causing the error.
> >> > Please help to figure out what is causing this and how it can be
> resolved.
> >> > I have attached the config log as well.
> >> >
> >> > Thanks
> >> > Mritunjay
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> I mistakenly forgot to cc my other mentors.
> >> >>
> >> >> This is what I responded :
> >> >>
> >> >>> Hello Heinz,
> >> >>>
> >> >>> Pardon the mistake I did in haste,
> >> >>> as I advised by you I am now building it for RTEMS 4.10 and then I
> will
> >> >>> be reporting here shortly as the build completes.
> >> >>>
> >> >>> Thanks
> >> >>> Mritunjay.
> >> >>
> >> >>
> >> >> I am shortly sending the email for the progress I made after working
> on above.
> >> >> Thanks
> >> >> Mritunjay
> >> >>
> >> >>
> >> >>
> >> >> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes <
> jun...@fhi-berlin.mpg.de> wrote:
> >> >>>
> >> >>> Hello, Mritunjay,
> >> >>>
> >> >>> the epics-base version in github does not work with RTEMS5 It needs
> my extensions for this.
> >> >>> Therefore I suggested that you first build epics7 for e.g. RTEMS
> 4.10.
> >> >>> Then the easiest way is to build epics7 for RTEMS-pc386-qemu. This
> is fully supported.
> >> >>> So you learn how to build 

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

[Gedare Bloom]

On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
 wrote:
>
> Hi Gedare,
>
> Thank you for the quick response, I tried using --target=i386-rtems4.10, 
> which again
> gave me the same error.
>
Did you build an RTEMS compiler toolchain for 4.10? and install it to
a prefix in your $PATH?

> "checking for RTEMS_CPU_MODEL... i386_fp
> checking for RTEMS_BSP_FAMILY... pc386
> checking for CPU_CFLAGS... (cached) -mtune=i386
> checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
> checking for style of include used by make... GNU
> checking for i386-rtems4.10-gcc... no
> configure: error: no acceptable cc found in $PATH
> Makefile:712: recipe for target 'pc386' failed
> make[2]: *** [pc386] Error 1
> make[2]: Leaving directory 
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> Makefile:257: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> '/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
> Makefile:275: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1"
>
> Mritunjay
>
> On Wed, Jul 1, 2020 at 3:48 AM Gedare Bloom  wrote:
>>
>>  Use --target=i386-rtems4.10 instead of  --target=i386-rtems
>>
>> Does this work with 4.10.3/4.10 HEAD?
>>
>> On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
>>  wrote:
>> >
>> > Hello everyone,
>> >
>> > I followed the documentation here 
>> > https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
>> >  and
>> > started building RTEMS (4.10.2) for target architecture: i386 and BSP: 
>> > pc386. The configure seemed to be fine
>> > after entering the following command:
>> > "../configure --target=i386-rtems --disable-posix --enable-cxx 
>> > --enable-rtemsbsp=pc386 --enable-tests=samples 
>> > --prefix=/home/development/rtems-4.10.2"
>> >
>> > However, the make failed with the following error: checking for 
>> > i386-rtems-gcc... no
>> > "configure: error: no acceptable cc found in $PATH
>> > Makefile:712: recipe for target 'pc386' failed
>> > make[2]: *** [pc386] Error 1
>> > make[2]: Leaving directory 
>> > '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
>> > Makefile:257: recipe for target 'all-recursive' failed
>> > make[1]: *** [all-recursive] Error 1
>> > make[1]: Leaving directory 
>> > '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
>> > Makefile:275: recipe for target 'all-recursive' failed
>> > make: *** [all-recursive] Error 1"
>> >
>> > I checked that gcc is already installed in /usr/bin/gcc.
>> > So I am not able to figure out what exactly is causing the error.
>> > Please help to figure out what is causing this and how it can be resolved.
>> > I have attached the config log as well.
>> >
>> > Thanks
>> > Mritunjay
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma 
>> >  wrote:
>> >>
>> >>
>> >> I mistakenly forgot to cc my other mentors.
>> >>
>> >> This is what I responded :
>> >>
>> >>> Hello Heinz,
>> >>>
>> >>> Pardon the mistake I did in haste,
>> >>> as I advised by you I am now building it for RTEMS 4.10 and then I will
>> >>> be reporting here shortly as the build completes.
>> >>>
>> >>> Thanks
>> >>> Mritunjay.
>> >>
>> >>
>> >> I am shortly sending the email for the progress I made after working on 
>> >> above.
>> >> Thanks
>> >> Mritunjay
>> >>
>> >>
>> >>
>> >> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes  
>> >> wrote:
>> >>>
>> >>> Hello, Mritunjay,
>> >>>
>> >>> the epics-base version in github does not work with RTEMS5 It needs my 
>> >>> extensions for this.
>> >>> Therefore I suggested that you first build epics7 for e.g. RTEMS 4.10.
>> >>> Then the easiest way is to build epics7 for RTEMS-pc386-qemu. This is 
>> >>> fully supported.
>> >>> So you learn how to build EPics and then you can develop a first rsb-set 
>> >>> for it.
>> >>> If this works, we will work on RTEMS5 and xilinx-Zynq.
>> >>> Heinz
>> >>>
>> >>> > On 30. Jun 2020, at 20:10, Mritunjay Sharma 
>> >>> >  wrote:
>> >>> >
>> >>> >
>> >>> > Hello everyone,
>> >>> >
>> >>> > While yesterday, I completed the blog for the progress
>> >>> > till date, today I started the coding part.
>> >>> >
>> >>> > The tutorial that Heinz sent me yesterday guided
>> >>> > me to make the following changes:
>> >>> >
>> >>> > 1) epics-base/configure/CONFIG_SITE:
>> >>> > # Which target architectures to cross-compile for.
>> >>> > #  Definitions in configure/os/CONFIG_SITE..Common
>> >>> > #  may override this setting.
>> >>> > -CROSS_COMPILER_TARGET_ARCHS=
>> >>> > - #CROSS_COMPILER_TARGET_ARCHS=vxWorks-ppc32
>> >>> > + CROSS_COMPILER_TARGET_ARCHS=pc386
>> >>> > +#CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
>> >>> >
>> >>> > I did not use xilinx_zynq_a9_qemu for now because I could
>> >>> > not locate CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>> >>> > as of now in epics-base/configure/os.
>> >>> >
>> >>> > 2) configure/os/CONFIG_SITE.Common.RTEMS :
>> >>> >
>> >>> > # Where to find RTEMS
>> >>> > #

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

[Mritunjay Sharma]

Hi Gedare,

Thank you for the quick response, I tried using --target=i386-rtems4.10,
which again
gave me the same error.

"checking for RTEMS_CPU_MODEL... i386_fp
checking for RTEMS_BSP_FAMILY... pc386
checking for CPU_CFLAGS... (cached) -mtune=i386
checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
checking for style of include used by make... GNU
checking for i386-rtems4.10-gcc... no
configure: error: no acceptable cc found in $PATH
Makefile:712: recipe for target 'pc386' failed
make[2]: *** [pc386] Error 1
make[2]: Leaving directory
'/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
Makefile:257: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
'/home/mritunjay/development/rtems-4.10.2/pc-386/i386-rtems4.10/c'
Makefile:275: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1"

Mritunjay

On Wed, Jul 1, 2020 at 3:48 AM Gedare Bloom  wrote:

>  Use --target=i386-rtems4.10 instead of  --target=i386-rtems
>
> Does this work with 4.10.3/4.10 HEAD?
>
> On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
>  wrote:
> >
> > Hello everyone,
> >
> > I followed the documentation here
> https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
> and
> > started building RTEMS (4.10.2) for target architecture: i386 and BSP:
> pc386. The configure seemed to be fine
> > after entering the following command:
> > "../configure --target=i386-rtems --disable-posix --enable-cxx
> --enable-rtemsbsp=pc386 --enable-tests=samples
> --prefix=/home/development/rtems-4.10.2"
> >
> > However, the make failed with the following error: checking for
> i386-rtems-gcc... no
> > "configure: error: no acceptable cc found in $PATH
> > Makefile:712: recipe for target 'pc386' failed
> > make[2]: *** [pc386] Error 1
> > make[2]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> > Makefile:257: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> > Makefile:275: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 1"
> >
> > I checked that gcc is already installed in /usr/bin/gcc.
> > So I am not able to figure out what exactly is causing the error.
> > Please help to figure out what is causing this and how it can be
> resolved.
> > I have attached the config log as well.
> >
> > Thanks
> > Mritunjay
> >
> >
> >
> >
> >
> >
> > On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >>
> >> I mistakenly forgot to cc my other mentors.
> >>
> >> This is what I responded :
> >>
> >>> Hello Heinz,
> >>>
> >>> Pardon the mistake I did in haste,
> >>> as I advised by you I am now building it for RTEMS 4.10 and then I will
> >>> be reporting here shortly as the build completes.
> >>>
> >>> Thanks
> >>> Mritunjay.
> >>
> >>
> >> I am shortly sending the email for the progress I made after working on
> above.
> >> Thanks
> >> Mritunjay
> >>
> >>
> >>
> >> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes 
> wrote:
> >>>
> >>> Hello, Mritunjay,
> >>>
> >>> the epics-base version in github does not work with RTEMS5 It needs my
> extensions for this.
> >>> Therefore I suggested that you first build epics7 for e.g. RTEMS 4.10.
> >>> Then the easiest way is to build epics7 for RTEMS-pc386-qemu. This is
> fully supported.
> >>> So you learn how to build EPics and then you can develop a first
> rsb-set for it.
> >>> If this works, we will work on RTEMS5 and xilinx-Zynq.
> >>> Heinz
> >>>
> >>> > On 30. Jun 2020, at 20:10, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>> >
> >>> >
> >>> > Hello everyone,
> >>> >
> >>> > While yesterday, I completed the blog for the progress
> >>> > till date, today I started the coding part.
> >>> >
> >>> > The tutorial that Heinz sent me yesterday guided
> >>> > me to make the following changes:
> >>> >
> >>> > 1) epics-base/configure/CONFIG_SITE:
> >>> > # Which target architectures to cross-compile for.
> >>> > #  Definitions in configure/os/CONFIG_SITE..Common
> >>> > #  may override this setting.
> >>> > -CROSS_COMPILER_TARGET_ARCHS=
> >>> > - #CROSS_COMPILER_TARGET_ARCHS=vxWorks-ppc32
> >>> > + CROSS_COMPILER_TARGET_ARCHS=pc386
> >>> > +#CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
> >>> >
> >>> > I did not use xilinx_zynq_a9_qemu for now because I could
> >>> > not locate CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
> >>> > as of now in epics-base/configure/os.
> >>> >
> >>> > 2) configure/os/CONFIG_SITE.Common.RTEMS :
> >>> >
> >>> > # Where to find RTEMS
> >>> > #
> >>> > # APS:
> >>> > -RTEMS_VERSION = 4.10.2
> >>> > -RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
> >>> > #RTEMS_VERSION = 4.10.2
> >>> > #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
> >>> >
> >>> > +# FHI:
> >>> > +RTEMS_SERIES = 5
> >>> > +RTEMS_VERSION = 5
> >>> > +RTEMS_BASE = 

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

[Gedare Bloom]

 Use --target=i386-rtems4.10 instead of  --target=i386-rtems

Does this work with 4.10.3/4.10 HEAD?

On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
 wrote:
>
> Hello everyone,
>
> I followed the documentation here 
> https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf 
> and
> started building RTEMS (4.10.2) for target architecture: i386 and BSP: pc386. 
> The configure seemed to be fine
> after entering the following command:
> "../configure --target=i386-rtems --disable-posix --enable-cxx 
> --enable-rtemsbsp=pc386 --enable-tests=samples 
> --prefix=/home/development/rtems-4.10.2"
>
> However, the make failed with the following error: checking for 
> i386-rtems-gcc... no
> "configure: error: no acceptable cc found in $PATH
> Makefile:712: recipe for target 'pc386' failed
> make[2]: *** [pc386] Error 1
> make[2]: Leaving directory 
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> Makefile:257: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> '/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
> Makefile:275: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1"
>
> I checked that gcc is already installed in /usr/bin/gcc.
> So I am not able to figure out what exactly is causing the error.
> Please help to figure out what is causing this and how it can be resolved.
> I have attached the config log as well.
>
> Thanks
> Mritunjay
>
>
>
>
>
>
> On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma 
>  wrote:
>>
>>
>> I mistakenly forgot to cc my other mentors.
>>
>> This is what I responded :
>>
>>> Hello Heinz,
>>>
>>> Pardon the mistake I did in haste,
>>> as I advised by you I am now building it for RTEMS 4.10 and then I will
>>> be reporting here shortly as the build completes.
>>>
>>> Thanks
>>> Mritunjay.
>>
>>
>> I am shortly sending the email for the progress I made after working on 
>> above.
>> Thanks
>> Mritunjay
>>
>>
>>
>> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes  
>> wrote:
>>>
>>> Hello, Mritunjay,
>>>
>>> the epics-base version in github does not work with RTEMS5 It needs my 
>>> extensions for this.
>>> Therefore I suggested that you first build epics7 for e.g. RTEMS 4.10.
>>> Then the easiest way is to build epics7 for RTEMS-pc386-qemu. This is fully 
>>> supported.
>>> So you learn how to build EPics and then you can develop a first rsb-set 
>>> for it.
>>> If this works, we will work on RTEMS5 and xilinx-Zynq.
>>> Heinz
>>>
>>> > On 30. Jun 2020, at 20:10, Mritunjay Sharma 
>>> >  wrote:
>>> >
>>> >
>>> > Hello everyone,
>>> >
>>> > While yesterday, I completed the blog for the progress
>>> > till date, today I started the coding part.
>>> >
>>> > The tutorial that Heinz sent me yesterday guided
>>> > me to make the following changes:
>>> >
>>> > 1) epics-base/configure/CONFIG_SITE:
>>> > # Which target architectures to cross-compile for.
>>> > #  Definitions in configure/os/CONFIG_SITE..Common
>>> > #  may override this setting.
>>> > -CROSS_COMPILER_TARGET_ARCHS=
>>> > - #CROSS_COMPILER_TARGET_ARCHS=vxWorks-ppc32
>>> > + CROSS_COMPILER_TARGET_ARCHS=pc386
>>> > +#CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
>>> >
>>> > I did not use xilinx_zynq_a9_qemu for now because I could
>>> > not locate CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>>> > as of now in epics-base/configure/os.
>>> >
>>> > 2) configure/os/CONFIG_SITE.Common.RTEMS :
>>> >
>>> > # Where to find RTEMS
>>> > #
>>> > # APS:
>>> > -RTEMS_VERSION = 4.10.2
>>> > -RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>>> > #RTEMS_VERSION = 4.10.2
>>> > #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>>> >
>>> > +# FHI:
>>> > +RTEMS_SERIES = 5
>>> > +RTEMS_VERSION = 5
>>> > +RTEMS_BASE = /home/mritunjay/development/rtems/5
>>> >
>>> > I thought to straightaway move with building it with RTEMS 5
>>> > because I have done it earlier for beatnik.
>>> >
>>> > After this as an experiment, I tried the make command which,
>>> > as expected, generated the following error:
>>> >
>>> > "make[4]: *** No rule to make target '../O.Common/osiFileName.h', needed 
>>> > by 'inc'.  Stop.
>>> > make[4]: Leaving directory 
>>> > '/home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.pc386'
>>> > ../../../configure/RULES_ARCHS:58: recipe for target 'install.pc386' 
>>> > failed
>>> > make[3]: *** [install.pc386] Error 2
>>> > make[3]: Leaving directory 
>>> > '/home/mritunjay/development/EPICS/epics-base/modules/libcom/src'
>>> > ../../configure/RULES_DIRS:85: recipe for target 'src.install' failed
>>> > make[2]: *** [src.install] Error 2
>>> > make[2]: Leaving directory 
>>> > '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
>>> > ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
>>> > make[1]: *** [libcom.install] Error 2
>>> > make[1]: Leaving directory 
>>> > '/home/mritunjay/development/EPICS/epics-base/modules'
>>> > configure/RULES_DIRS:85: 

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

[Mritunjay Sharma]

Hello everyone,

I followed the documentation here
https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
 and
started building RTEMS (4.10.2) for target architecture: i386 and BSP:
pc386. The configure seemed to be fine
after entering the following command:
"../configure --target=i386-rtems --disable-posix --enable-cxx
--enable-rtemsbsp=pc386 --enable-tests=samples
--prefix=/home/development/rtems-4.10.2"

However, the make failed with the following error: checking for
i386-rtems-gcc... no
"configure: error: no acceptable cc found in $PATH
Makefile:712: recipe for target 'pc386' failed
make[2]: *** [pc386] Error 1
make[2]: Leaving directory
'/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
Makefile:257: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
'/home/mritunjay/development/rtems-4.10.2/pc386/i386-rtems/c'
Makefile:275: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1"

I checked that gcc is already installed in /usr/bin/gcc.
So I am not able to figure out what exactly is causing the error.
Please help to figure out what is causing this and how it can be resolved.
I have attached the config log as well.

Thanks
Mritunjay






On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
> I mistakenly forgot to cc my other mentors.
>
> This is what I responded :
>
> Hello Heinz,
>>
>> Pardon the mistake I did in haste,
>> as I advised by you I am now building it for RTEMS 4.10 and then I will
>> be reporting here shortly as the build completes.
>>
>> Thanks
>> Mritunjay.
>>
>
> I am shortly sending the email for the progress I made after working on
> above.
> Thanks
> Mritunjay
>
>
>
> On Wed, Jul 1, 2020 at 12:11 AM Heinz Junkes 
> wrote:
>
>> Hello, Mritunjay,
>>
>> the epics-base version in github does not work with RTEMS5 It needs my
>> extensions for this.
>> Therefore I suggested that you first build epics7 for e.g. RTEMS 4.10.
>> Then the easiest way is to build epics7 for RTEMS-pc386-qemu. This is
>> fully supported.
>> So you learn how to build EPics and then you can develop a first rsb-set
>> for it.
>> If this works, we will work on RTEMS5 and xilinx-Zynq.
>> Heinz
>>
>> > On 30. Jun 2020, at 20:10, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >
>> >
>> > Hello everyone,
>> >
>> > While yesterday, I completed the blog for the progress
>> > till date, today I started the coding part.
>> >
>> > The tutorial that Heinz sent me yesterday guided
>> > me to make the following changes:
>> >
>> > 1) epics-base/configure/CONFIG_SITE:
>> > # Which target architectures to cross-compile for.
>> > #  Definitions in configure/os/CONFIG_SITE..Common
>> > #  may override this setting.
>> > -CROSS_COMPILER_TARGET_ARCHS=
>> > - #CROSS_COMPILER_TARGET_ARCHS=vxWorks-ppc32
>> > + CROSS_COMPILER_TARGET_ARCHS=pc386
>> > +#CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
>> >
>> > I did not use xilinx_zynq_a9_qemu for now because I could
>> > not locate CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
>> > as of now in epics-base/configure/os.
>> >
>> > 2) configure/os/CONFIG_SITE.Common.RTEMS :
>> >
>> > # Where to find RTEMS
>> > #
>> > # APS:
>> > -RTEMS_VERSION = 4.10.2
>> > -RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>> > #RTEMS_VERSION = 4.10.2
>> > #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)
>> >
>> > +# FHI:
>> > +RTEMS_SERIES = 5
>> > +RTEMS_VERSION = 5
>> > +RTEMS_BASE = /home/mritunjay/development/rtems/5
>> >
>> > I thought to straightaway move with building it with RTEMS 5
>> > because I have done it earlier for beatnik.
>> >
>> > After this as an experiment, I tried the make command which,
>> > as expected, generated the following error:
>> >
>> > "make[4]: *** No rule to make target '../O.Common/osiFileName.h',
>> needed by 'inc'.  Stop.
>> > make[4]: Leaving directory
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.pc386'
>> > ../../../configure/RULES_ARCHS:58: recipe for target 'install.pc386'
>> failed
>> > make[3]: *** [install.pc386] Error 2
>> > make[3]: Leaving directory
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom/src'
>> > ../../configure/RULES_DIRS:85: recipe for target 'src.install' failed
>> > make[2]: *** [src.install] Error 2
>> > make[2]: Leaving directory
>> '/home/mritunjay/development/EPICS/epics-base/modules/libcom'
>> > ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed
>> > make[1]: *** [libcom.install] Error 2
>> > make[1]: Leaving directory
>> '/home/mritunjay/development/EPICS/epics-base/modules'
>> > configure/RULES_DIRS:85: recipe for target 'modules.install' failed
>> > make: *** [modules.install] Error 2
>> > "
>> > I then re-visited to what I did with beatnik and made the following
>> changes to
>> > start with adding support for RTEMS 5:
>> >
>> > diff --git a/configure/CONFIG_COMMON b/configure/CONFIG_COMMON
>> > index