Re: [GSoC 2020]: Weekly thread update

2020-07-19 Thread Chris Johns 
On 20/7/20 2:08 am, Mritunjay Sharma wrote:
> Thank you, Heinz, for telling that. 
> I have started writing recipes and will update about it in the new thread.

Sorry for not responding before now, I have been occupied else where.

Please follow Gedare's recommendation and document the steps.

Do you have a script to perform an EPICS build?

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

Re: [GSoC 2020]: Weekly thread update

2020-07-19 Thread Mritunjay Sharma 
Thank you, Heinz, for telling that.
I have started writing recipes and will update about it in the new thread.

Thanks
Mritunjay


On Sun, Jul 19, 2020 at 8:49 PM Heinz Junkes 
wrote:

> It uses the legacy-stack.
> When I am back I will adapt rtems_init to use libbsd.
> You should proceed to write rsb recipes.
> Heinz
>
> FHI, Heinz Junkes
>
> On 19. Jul 2020, at 16:03, Mritunjay Sharma 
> wrote:
>
> 
>
>
> On Sun, Jul 19, 2020 at 4:28 AM Gedare Bloom  wrote:
>
>> On Sat, Jul 18, 2020 at 2:02 PM Mritunjay Sharma
>>  wrote:
>> >
>> > [UPDATE]: Thank you so much Heinz, with commit
>> `3afec267ab08568ea454789e562450b00feea5c0`v
>> > I was able to successfully built EPICS7 with RTEMS5 for pc-386 and
>> pc-386 qemu both.
>> >
>>
>> Great. Is this with --enable-networking?
>>
>
> Yes.
>
>>
>> Is libbsd still not yet working?
>>
>
> Not sure. Can you tell me the way it can be checked here?
>
>>
>> > As advised, should I begin writing RSB recipe now for RTEMS5?
>> > What can be the next steps?
>> >
>>
>> I think so. You might try to write some simple script first for
>> yourself, to help think through the logic of automation.
>>
>
> Sure, I will be starting a new thread for the next week and I will post it
> there.
>
>>
>> > Please advise and also guide on what will be the best way to begin with
>> writing RSB recipe?
>> >
>>
>> Now that you know how to build by hand, you want to document what you
>> need to do and then you can try to script it. I'm not really sure, but
>> I guess it would be a new kind of "rtems-package" to build, since it
>> is done after rtems is successfully installed? We'll eventually want
>> this to be a vertically integrated package with the RTEMS
>> configuration combined with EPICS for some BSPs that are known to
>> work. Get started, and ask questions as you go.
>>
>> work from doco at
>> https://docs.rtems.org/branches/master/user/rsb/index.html
>> and submit changes as needed to improve it
>>
>
> Thank you so much, Gedare. I will work and update on a new thread soon.
>
>>
>> > Thanks
>> > Mritunjay
>> >
>> > On Sat, Jul 18, 2020 at 10:48 PM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >>
>> >>
>> >> Thank you so much, I am trying and reverting soon.
>> >>
>> >> On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes <
>> jun...@fhi-berlin.mpg.de> wrote:
>> >>>
>> >>> Mritunjay,
>> >>> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
>> >>> Dated 25.9. 2019
>> >>>
>> >>> From Heinz
>> >>>
>> >>> On 17.07.2020, at 20:23, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes <
>> jun...@fhi-berlin.mpg.de> wrote:
>> 
>>  You are right. I was not aware of that the dhcpcd stuff is already
>> included into the source of the epicsPlayground repo. Will have a look into
>> it.
>>  Heinz
>> 
>>  FHI, Heinz Junkes
>> >>>
>> >>>
>> >>> Thank you so much, Heinz! It will be kind of you to advice for now to
>> how to proceed ahead like whether we have to either
>> >>> use and build the old legacy stack using `--enable-networking` or the
>> libbsd stack?
>> >>> Also, should I start writing the recipe for RSB based on the existing
>> notes of how the process went for building
>> >>> EPICS7 for RTEMS5 for pc-386?
>> >>>
>> >>> Also, I have written another blog on what I learnt recently (using
>> mutt). Here's the link:
>> >>>
>> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
>> >>>
>> >>> I also learnt about Networking Drivers from
>> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Mritunjay.
>> >>>
>> >>>
>> 
>>  On 15. Jul 2020, at 22:05, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> 
>>  
>>  Apologies as I mistakenly sent this as a private mail.
>>  I missed to tag Chris, Gedare and RTEMS Devel and that's why sending
>> this again on what
>>  I responded.
>> 
>>  On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >
>> >
>> >
>> > On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes <
>> jun...@fhi-berlin.mpg.de> wrote:
>> >>
>> >> Hello, Mritunjay,
>> >>
>> >> I'm afraid I've lost track of the situation. I am also still on
>> holiday in Norway for 2 weeks and
>> >> I don't always have perfect internet access.
>> >
>> >
>> 
>>  This:->
>> 
>> >
>> > I am extremely sorry to disturb you on a holiday. I will try to
>> bring back to you where we currently are:
>> > As advised by you I already have Built EPICS 7 with RTEMS 4.10 and
>> tested it as well.
>> > I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise
>> that I forgot to update the thread that the suggestion
>> > presented by Gedare to change to  `#include ` from
>> existing `#include ` helped me
>> > fixed the error mentioned in

Re: [GSoC 2020]: Weekly thread update

2020-07-19 Thread Heinz Junkes 
It uses the legacy-stack. 
When I am back I will adapt rtems_init to use libbsd. 
You should proceed to write rsb recipes.
Heinz

FHI, Heinz Junkes

> On 19. Jul 2020, at 16:03, Mritunjay Sharma  
> wrote:
> 
> 
> 
> 
>> On Sun, Jul 19, 2020 at 4:28 AM Gedare Bloom  wrote:
>> On Sat, Jul 18, 2020 at 2:02 PM Mritunjay Sharma
>>  wrote:
>> >
>> > [UPDATE]: Thank you so much Heinz, with commit 
>> > `3afec267ab08568ea454789e562450b00feea5c0`v
>> > I was able to successfully built EPICS7 with RTEMS5 for pc-386 and pc-386 
>> > qemu both.
>> >
>> 
>> Great. Is this with --enable-networking?
> 
> Yes.  
>> 
>> Is libbsd still not yet working?
> 
> Not sure. Can you tell me the way it can be checked here?  
>> 
>> > As advised, should I begin writing RSB recipe now for RTEMS5?
>> > What can be the next steps?
>> >
>> 
>> I think so. You might try to write some simple script first for
>> yourself, to help think through the logic of automation.
> 
> Sure, I will be starting a new thread for the next week and I will post it 
> there. 
>> 
>> > Please advise and also guide on what will be the best way to begin with 
>> > writing RSB recipe?
>> >
>> 
>> Now that you know how to build by hand, you want to document what you
>> need to do and then you can try to script it. I'm not really sure, but
>> I guess it would be a new kind of "rtems-package" to build, since it
>> is done after rtems is successfully installed? We'll eventually want
>> this to be a vertically integrated package with the RTEMS
>> configuration combined with EPICS for some BSPs that are known to
>> work. Get started, and ask questions as you go.
>> 
>> work from doco at https://docs.rtems.org/branches/master/user/rsb/index.html
>> and submit changes as needed to improve it
> 
> Thank you so much, Gedare. I will work and update on a new thread soon.  
>> 
>> > Thanks
>> > Mritunjay
>> >
>> > On Sat, Jul 18, 2020 at 10:48 PM Mritunjay Sharma 
>> >  wrote:
>> >>
>> >>
>> >> Thank you so much, I am trying and reverting soon.
>> >>
>> >> On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes  
>> >> wrote:
>> >>>
>> >>> Mritunjay,
>> >>> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
>> >>> Dated 25.9. 2019
>> >>>
>> >>> From Heinz
>> >>>
>> >>> On 17.07.2020, at 20:23, Mritunjay Sharma  
>> >>> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes  
>> >>> wrote:
>> 
>>  You are right. I was not aware of that the dhcpcd stuff is already 
>>  included into the source of the epicsPlayground repo. Will have a look 
>>  into it.
>>  Heinz
>> 
>>  FHI, Heinz Junkes
>> >>>
>> >>>
>> >>> Thank you so much, Heinz! It will be kind of you to advice for now to 
>> >>> how to proceed ahead like whether we have to either
>> >>> use and build the old legacy stack using `--enable-networking` or the 
>> >>> libbsd stack?
>> >>> Also, should I start writing the recipe for RSB based on the existing 
>> >>> notes of how the process went for building
>> >>> EPICS7 for RTEMS5 for pc-386?
>> >>>
>> >>> Also, I have written another blog on what I learnt recently (using 
>> >>> mutt). Here's the link:
>> >>> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
>> >>>
>> >>> I also learnt about Networking Drivers from 
>> >>> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Mritunjay.
>> >>>
>> >>>
>> 
>>  On 15. Jul 2020, at 22:05, Mritunjay Sharma 
>>   wrote:
>> 
>>  
>>  Apologies as I mistakenly sent this as a private mail.
>>  I missed to tag Chris, Gedare and RTEMS Devel and that's why sending 
>>  this again on what
>>  I responded.
>> 
>>  On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma 
>>   wrote:
>> >
>> >
>> >
>> > On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes 
>> >  wrote:
>> >>
>> >> Hello, Mritunjay,
>> >>
>> >> I'm afraid I've lost track of the situation. I am also still on 
>> >> holiday in Norway for 2 weeks and
>> >> I don't always have perfect internet access.
>> >
>> >
>> 
>>  This:->
>> 
>> >
>> > I am extremely sorry to disturb you on a holiday. I will try to bring 
>> > back to you where we currently are:
>> > As advised by you I already have Built EPICS 7 with RTEMS 4.10 and 
>> > tested it as well.
>> > I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise 
>> > that I forgot to update the thread that the suggestion
>> > presented by Gedare to change to  `#include ` from 
>> > existing `#include ` helped me
>> > fixed the error mentioned in the start of the thread 
>> > ("../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such 
>> > file or directory
>> >  #include ").
>> >
>> > I used the 'make' command again then inside `epics-base` (Downloaded 
>> > from your GitHub's

Re: [GSoC 2020]: Weekly thread update

2020-07-19 Thread Mritunjay Sharma 
On Sun, Jul 19, 2020 at 4:28 AM Gedare Bloom  wrote:

> On Sat, Jul 18, 2020 at 2:02 PM Mritunjay Sharma
>  wrote:
> >
> > [UPDATE]: Thank you so much Heinz, with commit
> `3afec267ab08568ea454789e562450b00feea5c0`v
> > I was able to successfully built EPICS7 with RTEMS5 for pc-386 and
> pc-386 qemu both.
> >
>
> Great. Is this with --enable-networking?
>

Yes.

>
> Is libbsd still not yet working?
>

Not sure. Can you tell me the way it can be checked here?

>
> > As advised, should I begin writing RSB recipe now for RTEMS5?
> > What can be the next steps?
> >
>
> I think so. You might try to write some simple script first for
> yourself, to help think through the logic of automation.
>

Sure, I will be starting a new thread for the next week and I will post it
there.

>
> > Please advise and also guide on what will be the best way to begin with
> writing RSB recipe?
> >
>
> Now that you know how to build by hand, you want to document what you
> need to do and then you can try to script it. I'm not really sure, but
> I guess it would be a new kind of "rtems-package" to build, since it
> is done after rtems is successfully installed? We'll eventually want
> this to be a vertically integrated package with the RTEMS
> configuration combined with EPICS for some BSPs that are known to
> work. Get started, and ask questions as you go.
>
> work from doco at
> https://docs.rtems.org/branches/master/user/rsb/index.html
> and submit changes as needed to improve it
>

Thank you so much, Gedare. I will work and update on a new thread soon.

>
> > Thanks
> > Mritunjay
> >
> > On Sat, Jul 18, 2020 at 10:48 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >>
> >> Thank you so much, I am trying and reverting soon.
> >>
> >> On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes 
> wrote:
> >>>
> >>> Mritunjay,
> >>> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
> >>> Dated 25.9. 2019
> >>>
> >>> From Heinz
> >>>
> >>> On 17.07.2020, at 20:23, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>>
> >>>
> >>>
> >>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes <
> jun...@fhi-berlin.mpg.de> wrote:
> 
>  You are right. I was not aware of that the dhcpcd stuff is already
> included into the source of the epicsPlayground repo. Will have a look into
> it.
>  Heinz
> 
>  FHI, Heinz Junkes
> >>>
> >>>
> >>> Thank you so much, Heinz! It will be kind of you to advice for now to
> how to proceed ahead like whether we have to either
> >>> use and build the old legacy stack using `--enable-networking` or the
> libbsd stack?
> >>> Also, should I start writing the recipe for RSB based on the existing
> notes of how the process went for building
> >>> EPICS7 for RTEMS5 for pc-386?
> >>>
> >>> Also, I have written another blog on what I learnt recently (using
> mutt). Here's the link:
> >>>
> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
> >>>
> >>> I also learnt about Networking Drivers from
> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
> >>>
> >>>
> >>> Thanks,
> >>> Mritunjay.
> >>>
> >>>
> 
>  On 15. Jul 2020, at 22:05, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> 
>  
>  Apologies as I mistakenly sent this as a private mail.
>  I missed to tag Chris, Gedare and RTEMS Devel and that's why sending
> this again on what
>  I responded.
> 
>  On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >
> >
> >
> > On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes <
> jun...@fhi-berlin.mpg.de> wrote:
> >>
> >> Hello, Mritunjay,
> >>
> >> I'm afraid I've lost track of the situation. I am also still on
> holiday in Norway for 2 weeks and
> >> I don't always have perfect internet access.
> >
> >
> 
>  This:->
> 
> >
> > I am extremely sorry to disturb you on a holiday. I will try to
> bring back to you where we currently are:
> > As advised by you I already have Built EPICS 7 with RTEMS 4.10 and
> tested it as well.
> > I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise
> that I forgot to update the thread that the suggestion
> > presented by Gedare to change to  `#include ` from
> existing `#include ` helped me
> > fixed the error mentioned in the start of the thread
> ("../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file
> or directory
> >  #include ").
> >
> > I used the 'make' command again then inside `epics-base` (Downloaded
> from your GitHub's playground) and then got the
> > following error:
> >
> > `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such
> file or directory
> >  #include 
> > `
> > I discussed this with Gedare on the IRC channel and we concluded
> that it is there because we have to either
> > use and build the old legacy stack

Re: [GSoC 2020]: Weekly thread update

2020-07-18 Thread Gedare Bloom 
On Sat, Jul 18, 2020 at 2:02 PM Mritunjay Sharma
 wrote:
>
> [UPDATE]: Thank you so much Heinz, with commit 
> `3afec267ab08568ea454789e562450b00feea5c0`v
> I was able to successfully built EPICS7 with RTEMS5 for pc-386 and pc-386 
> qemu both.
>

Great. Is this with --enable-networking?

Is libbsd still not yet working?

> As advised, should I begin writing RSB recipe now for RTEMS5?
> What can be the next steps?
>

I think so. You might try to write some simple script first for
yourself, to help think through the logic of automation.

> Please advise and also guide on what will be the best way to begin with 
> writing RSB recipe?
>

Now that you know how to build by hand, you want to document what you
need to do and then you can try to script it. I'm not really sure, but
I guess it would be a new kind of "rtems-package" to build, since it
is done after rtems is successfully installed? We'll eventually want
this to be a vertically integrated package with the RTEMS
configuration combined with EPICS for some BSPs that are known to
work. Get started, and ask questions as you go.

work from doco at https://docs.rtems.org/branches/master/user/rsb/index.html
and submit changes as needed to improve it

> Thanks
> Mritunjay
>
> On Sat, Jul 18, 2020 at 10:48 PM Mritunjay Sharma 
>  wrote:
>>
>>
>> Thank you so much, I am trying and reverting soon.
>>
>> On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes  
>> wrote:
>>>
>>> Mritunjay,
>>> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
>>> Dated 25.9. 2019
>>>
>>> From Heinz
>>>
>>> On 17.07.2020, at 20:23, Mritunjay Sharma  
>>> wrote:
>>>
>>>
>>>
>>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes  
>>> wrote:

 You are right. I was not aware of that the dhcpcd stuff is already 
 included into the source of the epicsPlayground repo. Will have a look 
 into it.
 Heinz

 FHI, Heinz Junkes
>>>
>>>
>>> Thank you so much, Heinz! It will be kind of you to advice for now to how 
>>> to proceed ahead like whether we have to either
>>> use and build the old legacy stack using `--enable-networking` or the 
>>> libbsd stack?
>>> Also, should I start writing the recipe for RSB based on the existing notes 
>>> of how the process went for building
>>> EPICS7 for RTEMS5 for pc-386?
>>>
>>> Also, I have written another blog on what I learnt recently (using mutt). 
>>> Here's the link:
>>> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
>>>
>>> I also learnt about Networking Drivers from 
>>> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
>>>
>>>
>>> Thanks,
>>> Mritunjay.
>>>
>>>

 On 15. Jul 2020, at 22:05, Mritunjay Sharma  
 wrote:

 
 Apologies as I mistakenly sent this as a private mail.
 I missed to tag Chris, Gedare and RTEMS Devel and that's why sending this 
 again on what
 I responded.

 On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma 
  wrote:
>
>
>
> On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes  
> wrote:
>>
>> Hello, Mritunjay,
>>
>> I'm afraid I've lost track of the situation. I am also still on holiday 
>> in Norway for 2 weeks and
>> I don't always have perfect internet access.
>
>

 This:->

>
> I am extremely sorry to disturb you on a holiday. I will try to bring 
> back to you where we currently are:
> As advised by you I already have Built EPICS 7 with RTEMS 4.10 and tested 
> it as well.
> I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise that 
> I forgot to update the thread that the suggestion
> presented by Gedare to change to  `#include ` from existing 
> `#include ` helped me
> fixed the error mentioned in the start of the thread 
> ("../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file 
> or directory
>  #include ").
>
> I used the 'make' command again then inside `epics-base` (Downloaded from 
> your GitHub's playground) and then got the
> following error:
>
> `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file 
> or directory
>  #include 
> `
> I discussed this with Gedare on the IRC channel and we concluded that it 
> is there because we have to either
> use and build the old legacy stack using `--enable-networking` or the 
> libbsd stack.
>
> I would like your advice on what should work here and how to approach 
> doing each of these builds?
> Also, I again apologise that I am disturbing you on a holiday. Please 
> enjoy and take care!
>
> Thanks
> Mritunjay
>
>>
>> Where can I find your blog. I only found something from June 9th. What 
>> is the current location of the blog?


 This:->
>
> I have made another blog which as of now deals with building BSPs and I 
> have to update the draft

Re: [GSoC 2020]: Weekly thread update

2020-07-18 Thread Mritunjay Sharma 
[UPDATE]: Thank you so much Heinz, with commit `
3afec267ab08568ea454789e562450b00feea5c0`v
I was able to successfully built EPICS7 with RTEMS5 for pc-386 and pc-386
qemu both.

As advised, should I begin writing RSB recipe now for RTEMS5?
What can be the next steps?

Please advise and also guide on what will be the best way to begin with
writing RSB recipe?

Thanks
Mritunjay

On Sat, Jul 18, 2020 at 10:48 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
> Thank you so much, I am trying and reverting soon.
>
> On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes 
> wrote:
>
>> Mritunjay,
>> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
>> Dated 25.9. 2019
>>
>> From Heinz
>>
>> On 17.07.2020, at 20:23, Mritunjay Sharma 
>> wrote:
>>
>>
>>
>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes 
>> wrote:
>>
>>> You are right. I was not aware of that the dhcpcd stuff is already
>>> included into the source of the epicsPlayground repo. Will have a look into
>>> it.
>>> Heinz
>>>
>>> FHI, Heinz Junkes
>>>
>>
>> Thank you so much, Heinz! It will be kind of you to advice for now to how
>> to proceed ahead like whether we have to either
>> use and build the old legacy stack using `--enable-networking` or the
>> libbsd stack?
>> Also, should I start writing the recipe for RSB based on the existing
>> notes of how the process went for building
>> EPICS7 for RTEMS5 for pc-386?
>>
>> Also, I have written another blog on what I learnt recently (using mutt).
>> Here's the link:
>>
>> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
>>
>> I also learnt about Networking Drivers from
>> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
>>
>>
>> Thanks,
>> Mritunjay.
>>
>>
>>
>>> On 15. Jul 2020, at 22:05, Mritunjay Sharma <
>>> mritunjaysharma...@gmail.com> wrote:
>>>
>>> 
>>> Apologies as I mistakenly sent this as a private mail.
>>> I missed to tag Chris, Gedare and RTEMS Devel and that's why sending
>>> this again on what
>>> I responded.
>>>
>>> On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
>>> mritunjaysharma...@gmail.com> wrote:
>>>


 On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes 
 wrote:

> Hello, Mritunjay,
>
> I'm afraid I've lost track of the situation. I am also still on
> holiday in Norway for 2 weeks and
> I don't always have perfect internet access.
>


>>> This:->
>>>
>>>
 I am extremely sorry to disturb you on a holiday. I will try to bring
 back to you where we currently are:
 As advised by you I already have Built EPICS 7 with RTEMS 4.10 and
 tested it as well.
 I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise
 that I forgot to update the thread that the suggestion
 presented by Gedare to change to  `#include ` from
 existing `#include ` helped me
 fixed the error mentioned in the start of the thread 
 ("../posix/rtems_init.c:38:10:
 fatal error: rtems/bsd/bsd.h: No such file or directory
  #include ").

 I used the 'make' command again then inside `epics-base` (Downloaded
 from your GitHub's playground) and then got the
 following error:

 `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file
 or directory
  #include 
 `
 I discussed this with Gedare on the IRC channel and we concluded that
 it is there because we have to either
 use and build the old legacy stack using `--enable-networking` or the
 libbsd stack.

 I would like your advice on what should work here and how to approach
 doing each of these builds?
 Also, I again apologise that I am disturbing you on a holiday. Please
 enjoy and take care!

 Thanks
 Mritunjay


> Where can I find your blog. I only found something from June 9th. What
> is the current location of the blog?


>>> This:->
>>>
 I have made another blog which as of now deals with building BSPs and I
 have to update the draft of another one
 which will further demonstrate on how to Build EPICS.
 The link to the blog is:
 https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902

>
> I'm afraid you've made a mess of things here.
>

 This:-
>>>
 I am sorry if I have and I accept that I am a beginner but am really
 enjoying the learning I am making this summer.
 Thank you so much for the support everyone in helping me grow and
 learn.

 Thanks
 Mritunjay

>
> In the "official" epics repo, you can read
>
>
> https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
> :
>
> …
>
> #include 
> #include 
> #include 
> #include 
> #include 
> …
> Here the definition of the legacy stack will be included
>
> #include 
>

Re: [GSoC 2020]: Weekly thread update

2020-07-18 Thread Mritunjay Sharma 
Thank you so much, I am trying and reverting soon.

On Sat, Jul 18, 2020 at 10:45 PM Heinz Junkes 
wrote:

> Mritunjay,
> can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
> Dated 25.9. 2019
>
> From Heinz
>
> On 17.07.2020, at 20:23, Mritunjay Sharma 
> wrote:
>
>
>
> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes 
> wrote:
>
>> You are right. I was not aware of that the dhcpcd stuff is already
>> included into the source of the epicsPlayground repo. Will have a look into
>> it.
>> Heinz
>>
>> FHI, Heinz Junkes
>>
>
> Thank you so much, Heinz! It will be kind of you to advice for now to how
> to proceed ahead like whether we have to either
> use and build the old legacy stack using `--enable-networking` or the
> libbsd stack?
> Also, should I start writing the recipe for RSB based on the existing
> notes of how the process went for building
> EPICS7 for RTEMS5 for pc-386?
>
> Also, I have written another blog on what I learnt recently (using mutt).
> Here's the link:
>
> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
>
> I also learnt about Networking Drivers from
> https://docs.rtems.org/branches/master/bsp-howto/networking.html.
>
>
> Thanks,
> Mritunjay.
>
>
>
>> On 15. Jul 2020, at 22:05, Mritunjay Sharma 
>> wrote:
>>
>> 
>> Apologies as I mistakenly sent this as a private mail.
>> I missed to tag Chris, Gedare and RTEMS Devel and that's why sending this
>> again on what
>> I responded.
>>
>> On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes 
>>> wrote:
>>>
 Hello, Mritunjay,

 I'm afraid I've lost track of the situation. I am also still on holiday
 in Norway for 2 weeks and
 I don't always have perfect internet access.

>>>
>>>
>> This:->
>>
>>
>>> I am extremely sorry to disturb you on a holiday. I will try to bring
>>> back to you where we currently are:
>>> As advised by you I already have Built EPICS 7 with RTEMS 4.10 and
>>> tested it as well.
>>> I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise that
>>> I forgot to update the thread that the suggestion
>>> presented by Gedare to change to  `#include ` from existing
>>> `#include ` helped me
>>> fixed the error mentioned in the start of the thread 
>>> ("../posix/rtems_init.c:38:10:
>>> fatal error: rtems/bsd/bsd.h: No such file or directory
>>>  #include ").
>>>
>>> I used the 'make' command again then inside `epics-base` (Downloaded
>>> from your GitHub's playground) and then got the
>>> following error:
>>>
>>> `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file
>>> or directory
>>>  #include 
>>> `
>>> I discussed this with Gedare on the IRC channel and we concluded that it
>>> is there because we have to either
>>> use and build the old legacy stack using `--enable-networking` or the
>>> libbsd stack.
>>>
>>> I would like your advice on what should work here and how to approach
>>> doing each of these builds?
>>> Also, I again apologise that I am disturbing you on a holiday. Please
>>> enjoy and take care!
>>>
>>> Thanks
>>> Mritunjay
>>>
>>>
 Where can I find your blog. I only found something from June 9th. What
 is the current location of the blog?
>>>
>>>
>> This:->
>>
>>> I have made another blog which as of now deals with building BSPs and I
>>> have to update the draft of another one
>>> which will further demonstrate on how to Build EPICS.
>>> The link to the blog is:
>>> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>>>

 I'm afraid you've made a mess of things here.

>>>
>>> This:-
>>
>>> I am sorry if I have and I accept that I am a beginner but am really
>>> enjoying the learning I am making this summer.
>>> Thank you so much for the support everyone in helping me grow and learn.
>>>
>>> Thanks
>>> Mritunjay
>>>

 In the "official" epics repo, you can read


 https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
 :

 …

 #include 
 #include 
 #include 
 #include 
 #include 
 …
 Here the definition of the legacy stack will be included

 #include 



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



 > On 15. Jul 2020, at 05:57, Mritunjay Sharma <
 mritunjaysharma...@gmail.com> wrote:
 >
 >
 >
 > On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
 > On 15/7/20 4:30 am, Mritunjay Sharma wrote:
 > > Hello everyone,
 > >
 > > Pardon my mistake for that long thread. From now on the daily
 updates will be
 > > given on a thread that will end every week.
 >
 > Thank you :)
 >
 > > 1) I studied about https://github.com/RTEMS/rtems-libbsd
 > > 2) Tried to fix the error that I

Re: [GSoC 2020]: Weekly thread update

2020-07-18 Thread Heinz Junkes 
Mritunjay,
can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
Dated 25.9. 2019

From Heinz

> On 17.07.2020, at 20:23, Mritunjay Sharma  
> wrote:
> 
> 
> 
>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes  
>> wrote:
>> You are right. I was not aware of that the dhcpcd stuff is already included 
>> into the source of the epicsPlayground repo. Will have a look into it. 
>> Heinz
>> 
>> FHI, Heinz Junkes
> 
> Thank you so much, Heinz! It will be kind of you to advice for now to how to 
> proceed ahead like whether we have to either 
> use and build the old legacy stack using `--enable-networking` or the libbsd 
> stack? 
> Also, should I start writing the recipe for RSB based on the existing notes 
> of how the process went for building 
> EPICS7 for RTEMS5 for pc-386? 
> 
> Also, I have written another blog on what I learnt recently (using mutt). 
> Here's the link: 
> https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003
> 
> I also learnt about Networking Drivers from 
> https://docs.rtems.org/branches/master/bsp-howto/networking.html. 
> 
> 
> Thanks,
> Mritunjay. 
> 
> 
>> 
>>> On 15. Jul 2020, at 22:05, Mritunjay Sharma  
>>> wrote:
>>> 
>>> 
>>> Apologies as I mistakenly sent this as a private mail. 
>>> I missed to tag Chris, Gedare and RTEMS Devel and that's why sending this 
>>> again on what 
>>> I responded.
>>> 
 On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma 
  wrote:
 
 
> On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes  
> wrote:
> Hello, Mritunjay,
> 
> I'm afraid I've lost track of the situation. I am also still on holiday 
> in Norway for 2 weeks and 
> I don't always have perfect internet access.
 
>>>  
>>> This:->
>>>  
 I am extremely sorry to disturb you on a holiday. I will try to bring back 
 to you where we currently are: 
 As advised by you I already have Built EPICS 7 with RTEMS 4.10 and tested 
 it as well. 
 I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise that I 
 forgot to update the thread that the suggestion 
 presented by Gedare to change to  `#include ` from existing 
 `#include ` helped me 
 fixed the error mentioned in the start of the thread 
 ("../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file 
 or directory
  #include ").
 
 I used the 'make' command again then inside `epics-base` (Downloaded from 
 your GitHub's playground) and then got the 
 following error:
 
 `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file or 
 directory
  #include 
 `
 I discussed this with Gedare on the IRC channel and we concluded that it 
 is there because we have to either 
 use and build the old legacy stack using `--enable-networking` or the 
 libbsd stack. 
 
 I would like your advice on what should work here and how to approach 
 doing each of these builds? 
 Also, I again apologise that I am disturbing you on a holiday. Please 
 enjoy and take care! 
 
 Thanks
 Mritunjay 
  
> Where can I find your blog. I only found something from June 9th. What is 
> the current location of the blog?
>>> 
>>> This:-> 
 I have made another blog which as of now deals with building BSPs and I 
 have to update the draft of another one 
 which will further demonstrate on how to Build EPICS. 
 The link to the blog is:  
 https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
> 
> I'm afraid you've made a mess of things here.
 
>>> This:- 
 I am sorry if I have and I accept that I am a beginner but am really 
 enjoying the learning I am making this summer. 
 Thank you so much for the support everyone in helping me grow and learn. 
 
 Thanks
 Mritunjay
> 
> In the "official" epics repo, you can read
> 
> https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
>  :
> 
> …
> 
> #include 
> #include 
> #include 
> #include 
> #include 
> …
> Here the definition of the legacy stack will be included
> 
> #include 
> 
> 
> 
> Viele Grüße
> Heinz Junkes
> --
> Experience directly varies with equipment ruined.
> 
> 
> 
> > On 15. Jul 2020, at 05:57, Mritunjay Sharma 
> >  wrote:
> > 
> > 
> > 
> > On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
> > On 15/7/20 4:30 am, Mritunjay Sharma wrote:
> > > Hello everyone,
> > > 
> > > Pardon my mistake for that long thread. From now on the daily updates 
> > > will be
> > > given on a thread that will end every week. 
> > 
> > Thank you :)
> > 
> > > 1) I studied about https://github.com/RTEMS/rtems-libbsd
> > > 2) Tried to fix the error that

Re: [GSoC 2020]: Weekly thread update

2020-07-17 Thread Mritunjay Sharma 
On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes 
wrote:

> You are right. I was not aware of that the dhcpcd stuff is already
> included into the source of the epicsPlayground repo. Will have a look into
> it.
> Heinz
>
> FHI, Heinz Junkes
>

Thank you so much, Heinz! It will be kind of you to advice for now to how
to proceed ahead like whether we have to either
use and build the old legacy stack using `--enable-networking` or the
libbsd stack?
Also, should I start writing the recipe for RSB based on the existing notes
of how the process went for building
EPICS7 for RTEMS5 for pc-386?

Also, I have written another blog on what I learnt recently (using mutt).
Here's the link:
https://medium.com/@mritunjaysharma394/how-to-set-up-mutt-text-based-mail-client-with-gmail-993ae40b0003

I also learnt about Networking Drivers from
https://docs.rtems.org/branches/master/bsp-howto/networking.html.


Thanks,
Mritunjay.



> On 15. Jul 2020, at 22:05, Mritunjay Sharma 
> wrote:
>
> 
> Apologies as I mistakenly sent this as a private mail.
> I missed to tag Chris, Gedare and RTEMS Devel and that's why sending this
> again on what
> I responded.
>
> On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>>
>>
>> On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes 
>> wrote:
>>
>>> Hello, Mritunjay,
>>>
>>> I'm afraid I've lost track of the situation. I am also still on holiday
>>> in Norway for 2 weeks and
>>> I don't always have perfect internet access.
>>>
>>
>>
> This:->
>
>
>> I am extremely sorry to disturb you on a holiday. I will try to bring
>> back to you where we currently are:
>> As advised by you I already have Built EPICS 7 with RTEMS 4.10 and tested
>> it as well.
>> I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise that
>> I forgot to update the thread that the suggestion
>> presented by Gedare to change to  `#include ` from existing 
>> `#include
>> ` helped me
>> fixed the error mentioned in the start of the thread 
>> ("../posix/rtems_init.c:38:10:
>> fatal error: rtems/bsd/bsd.h: No such file or directory
>>  #include ").
>>
>> I used the 'make' command again then inside `epics-base` (Downloaded from
>> your GitHub's playground) and then got the
>> following error:
>>
>> `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file
>> or directory
>>  #include 
>> `
>> I discussed this with Gedare on the IRC channel and we concluded that it
>> is there because we have to either
>> use and build the old legacy stack using `--enable-networking` or the
>> libbsd stack.
>>
>> I would like your advice on what should work here and how to approach
>> doing each of these builds?
>> Also, I again apologise that I am disturbing you on a holiday. Please
>> enjoy and take care!
>>
>> Thanks
>> Mritunjay
>>
>>
>>> Where can I find your blog. I only found something from June 9th. What
>>> is the current location of the blog?
>>
>>
> This:->
>
>> I have made another blog which as of now deals with building BSPs and I
>> have to update the draft of another one
>> which will further demonstrate on how to Build EPICS.
>> The link to the blog is:
>> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>>
>>>
>>> I'm afraid you've made a mess of things here.
>>>
>>
>> This:-
>
>> I am sorry if I have and I accept that I am a beginner but am really
>> enjoying the learning I am making this summer.
>> Thank you so much for the support everyone in helping me grow and learn.
>>
>> Thanks
>> Mritunjay
>>
>>>
>>> In the "official" epics repo, you can read
>>>
>>>
>>> https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
>>> :
>>>
>>> …
>>>
>>> #include 
>>> #include 
>>> #include 
>>> #include 
>>> #include 
>>> …
>>> Here the definition of the legacy stack will be included
>>>
>>> #include 
>>>
>>>
>>>
>>> Viele Grüße
>>> Heinz Junkes
>>> --
>>> Experience directly varies with equipment ruined.
>>>
>>>
>>>
>>> > On 15. Jul 2020, at 05:57, Mritunjay Sharma <
>>> mritunjaysharma...@gmail.com> wrote:
>>> >
>>> >
>>> >
>>> > On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
>>> > On 15/7/20 4:30 am, Mritunjay Sharma wrote:
>>> > > Hello everyone,
>>> > >
>>> > > Pardon my mistake for that long thread. From now on the daily
>>> updates will be
>>> > > given on a thread that will end every week.
>>> >
>>> > Thank you :)
>>> >
>>> > > 1) I studied about https://github.com/RTEMS/rtems-libbsd
>>> > > 2) Tried to fix the error that I reported yesterday:
>>> > >
>>> > > ```
>>> >
>>> > Why cut the compile command line used to build this file out of the
>>> message? The
>>> > compiler command is important because it lets us see what paths are
>>> being used
>>> > and I think there may be a problem with them.
>>> >
>>> > > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
>>> file or directory
>>> > >  #include 
>>> > >   ^
>>> >
>>> > I cannot duplicate

Re: [GSoC 2020]: Weekly thread update

2020-07-15 Thread Mritunjay Sharma 
Apologies as I mistakenly sent this as a private mail.
I missed to tag Chris, Gedare and RTEMS Devel and that's why sending this
again on what
I responded.

On Wed, Jul 15, 2020 at 10:35 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> On Wed, Jul 15, 2020 at 7:48 PM Heinz Junkes 
> wrote:
>
>> Hello, Mritunjay,
>>
>> I'm afraid I've lost track of the situation. I am also still on holiday
>> in Norway for 2 weeks and
>> I don't always have perfect internet access.
>>
>
>
This:->


> I am extremely sorry to disturb you on a holiday. I will try to bring back
> to you where we currently are:
> As advised by you I already have Built EPICS 7 with RTEMS 4.10 and tested
> it as well.
> I was doing the same for EPICS7 with RTEMS5 for pc-386. I apologise that I
> forgot to update the thread that the suggestion
> presented by Gedare to change to  `#include ` from existing 
> `#include
> ` helped me
> fixed the error mentioned in the start of the thread 
> ("../posix/rtems_init.c:38:10:
> fatal error: rtems/bsd/bsd.h: No such file or directory
>  #include ").
>
> I used the 'make' command again then inside `epics-base` (Downloaded from
> your GitHub's playground) and then got the
> following error:
>
> `../posix/rtems_init.c:39:10: fatal error: rtems/dhcpcd.h: No such file or
> directory
>  #include 
> `
> I discussed this with Gedare on the IRC channel and we concluded that it
> is there because we have to either
> use and build the old legacy stack using `--enable-networking` or the
> libbsd stack.
>
> I would like your advice on what should work here and how to approach
> doing each of these builds?
> Also, I again apologise that I am disturbing you on a holiday. Please
> enjoy and take care!
>
> Thanks
> Mritunjay
>
>
>> Where can I find your blog. I only found something from June 9th. What is
>> the current location of the blog?
>
>
This:->

> I have made another blog which as of now deals with building BSPs and I
> have to update the draft of another one
> which will further demonstrate on how to Build EPICS.
> The link to the blog is:
> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
>
>>
>> I'm afraid you've made a mess of things here.
>>
>
> This:-

> I am sorry if I have and I accept that I am a beginner but am really
> enjoying the learning I am making this summer.
> Thank you so much for the support everyone in helping me grow and learn.
>
> Thanks
> Mritunjay
>
>>
>> In the "official" epics repo, you can read
>>
>>
>> https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
>> :
>>
>> …
>>
>> #include 
>> #include 
>> #include 
>> #include 
>> #include 
>> …
>> Here the definition of the legacy stack will be included
>>
>> #include 
>>
>>
>>
>> Viele Grüße
>> Heinz Junkes
>> --
>> Experience directly varies with equipment ruined.
>>
>>
>>
>> > On 15. Jul 2020, at 05:57, Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>> >
>> >
>> >
>> > On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
>> > On 15/7/20 4:30 am, Mritunjay Sharma wrote:
>> > > Hello everyone,
>> > >
>> > > Pardon my mistake for that long thread. From now on the daily updates
>> will be
>> > > given on a thread that will end every week.
>> >
>> > Thank you :)
>> >
>> > > 1) I studied about https://github.com/RTEMS/rtems-libbsd
>> > > 2) Tried to fix the error that I reported yesterday:
>> > >
>> > > ```
>> >
>> > Why cut the compile command line used to build this file out of the
>> message? The
>> > compiler command is important because it lets us see what paths are
>> being used
>> > and I think there may be a problem with them.
>> >
>> > > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such
>> file or directory
>> > >  #include 
>> > >   ^
>> >
>> > I cannot duplicate this because I am not sure what the sequence of
>> commands are
>> > you used to get to here. I am sorry if I missed it in a previous post.
>> >
>> > The error indicates a set up issue. It normally means the networking
>> software
>> > (rtems-libbsd) has not been installed into a prefix path EPICS looks in.
>> >
>> > I am posting the entire command set further ahead in the email which
>> will make things
>> > easier to understand.
>> >
>>
>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2020]: Weekly thread update

2020-07-15 Thread Heinz Junkes 
Hello, Mritunjay,

I'm afraid I've lost track of the situation. I am also still on holiday in 
Norway for 2 weeks and 
I don't always have perfect internet access.
Where can I find your blog. I only found something from June 9th. What is the 
current location of the blog?

I'm afraid you've made a mess of things here.

In the "official" epics repo, you can read

https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
 :

…

#include 
#include 
#include 
#include 
#include 
…
Here the definition of the legacy stack will be included

#include 



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



> On 15. Jul 2020, at 05:57, Mritunjay Sharma  
> wrote:
> 
> 
> 
> On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
> On 15/7/20 4:30 am, Mritunjay Sharma wrote:
> > Hello everyone,
> > 
> > Pardon my mistake for that long thread. From now on the daily updates will 
> > be
> > given on a thread that will end every week. 
> 
> Thank you :)
> 
> > 1) I studied about https://github.com/RTEMS/rtems-libbsd
> > 2) Tried to fix the error that I reported yesterday: 
> > 
> > ```
> 
> Why cut the compile command line used to build this file out of the message? 
> The
> compiler command is important because it lets us see what paths are being used
> and I think there may be a problem with them.
> 
> > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or 
> > directory
> >  #include 
> >   ^
> 
> I cannot duplicate this because I am not sure what the sequence of commands 
> are
> you used to get to here. I am sorry if I missed it in a previous post.
> 
> The error indicates a set up issue. It normally means the networking software
> (rtems-libbsd) has not been installed into a prefix path EPICS looks in.
> 
> I am posting the entire command set further ahead in the email which will 
> make things
> easier to understand.  
> 



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

Re: [GSoC 2020]: Weekly thread update

2020-07-14 Thread Chris Johns 
On 15/7/20 1:57 pm, Mritunjay Sharma wrote:
> On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  > wrote:
> 
> On 15/7/20 4:30 am, Mritunjay Sharma wrote:
> > Hello everyone,
> >
> > Pardon my mistake for that long thread. From now on the daily updates 
> will be
> > given on a thread that will end every week.
> 
> Thank you :)
> 
> > 1) I studied about https://github.com/RTEMS/rtems-libbsd
> > 2) Tried to fix the error that I reported yesterday: 
> >
> > ```
> 
> Why cut the compile command line used to build this file out of the 
> message? The
> compiler command is important because it lets us see what paths are being 
> used
> and I think there may be a problem with them.
> 
> > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file 
> or
> directory
> >  #include 
> >           ^
> 
> I cannot duplicate this because I am not sure what the sequence of 
> commands are
> you used to get to here. I am sorry if I missed it in a previous post.
> 
> The error indicates a set up issue. It normally means the networking 
> software
> (rtems-libbsd) has not been installed into a prefix path EPICS looks in.
> 
> 
> I am posting the entire command set further ahead in the email which will make
> things
> easier to understand.  

Thanks.

> > 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
> >
> > ```
> >
> > I am still not successful even though I tried to search for it.
> 
> I doubt there will be anything to search for. You are solving the problem 
> and
> creating the first info to be searched. We need to debug the problem.
> 
> > On the advice of Heinz, I have already built EPICS 7 with RTEMS4.10
> > by hand and am on the verge of doing the same for EPICS7 with RTEMS5 
> > for pc-386.
> 
> I am sorry I do not understand what "on the verge of doing the same" 
> means.
> 
> 
> I am sorry for the misunderstanding. It means that after these bugs are 
> resolved
> with this 
> discussion I will successfully be able to build EPICS7 with RTEMS5  
> 

OK

> 
> > However, I will like to request all my mentors to help me set the goals
> > for this week and where should I begin next?
> 
> Could you please update your blog with the exact command sequences you 
> are using
> to build EPICS7 for RTEMS 4.10 and EPICS7 for RTEMS 5 for a PC? 
> 
> 
> While I will be updating the commands in the blog, I am posting the same here
> for easier reference: 
> 
> Building EPICS7 for RTEMS4.10 with pc-386: 
> 
> In order to do that, I made the directory
> 
> i) $HOME/development/rtems/
> ii) I extracted rtems-4.10 from
> here https://ftp.rtems.org/pub/rtems/releases/4.10/
> 
> iii)I created another directory rtems/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/4.10 4.10/rtems-i386'.
> vi) Now the directory structure under $HOME/development/rtems/ looked like: 
>       | rtems-4.10
>       | 4.10
>       | src/rsb
>       | kernel/pc386
> I also used this command: "export PATH=$HOME/development/rtems/4.10/bin:$PATH"
> vi) Then I went to rtems/rtems-4.10 and used this command: 
> "./bootstrap -c && 
> $HOME/development/rtems/src/rsb/source-builder/sb-bootstrap"
> vi) After this I went insid directory $HOME/development/rtems/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
> --enable-posix  --enable-rtemsbsp=pc386 --enable-tests=samples
> --prefix=$HOME/development/rtems/4.10 --enable-cxx"
> viii) Then I entered the make command which ran successfully and the make
> install was also successful.
> 
> So all the errors were

Re: [GSoC 2020]: Weekly thread update

2020-07-14 Thread Gedare Bloom 
On Tue, Jul 14, 2020 at 9:57 PM Mritunjay Sharma
 wrote:
>
>
>
> On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:
>>
>> On 15/7/20 4:30 am, Mritunjay Sharma wrote:
>> > Hello everyone,
>> >
>> > Pardon my mistake for that long thread. From now on the daily updates will 
>> > be
>> > given on a thread that will end every week.
>>
>> Thank you :)
>>
>> > 1) I studied about https://github.com/RTEMS/rtems-libbsd
>> > 2) Tried to fix the error that I reported yesterday:
>> >
>> > ```
>>
>> Why cut the compile command line used to build this file out of the message? 
>> The
>> compiler command is important because it lets us see what paths are being 
>> used
>> and I think there may be a problem with them.
>>
>> > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or 
>> > directory
>> >  #include 
>> >   ^
>>

Try #include 

>> I cannot duplicate this because I am not sure what the sequence of commands 
>> are
>> you used to get to here. I am sorry if I missed it in a previous post.
>>
>> The error indicates a set up issue. It normally means the networking software
>> (rtems-libbsd) has not been installed into a prefix path EPICS looks in.
>
>
> I am posting the entire command set further ahead in the email which will 
> make things
> easier to understand.
>>
>>
>> > 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
>> >
>> > ```
>> >
>> > I am still not successful even though I tried to search for it.
>>
>> I doubt there will be anything to search for. You are solving the problem and
>> creating the first info to be searched. We need to debug the problem.
>>
>> > On the advice of Heinz, I have already built EPICS 7 with RTEMS4.10
>> > by hand and am on the verge of doing the same for EPICS7 with RTEMS5
>> > for pc-386.
>>
>> I am sorry I do not understand what "on the verge of doing the same" means.
>
>
> I am sorry for the misunderstanding. It means that after these bugs are 
> resolved with this
> discussion I will successfully be able to build EPICS7 with RTEMS5
>>
>>
>> > However, I will like to request all my mentors to help me set the goals
>> > for this week and where should I begin next?
>>
>> Could you please update your blog with the exact command sequences you are 
>> using
>> to build EPICS7 for RTEMS 4.10 and EPICS7 for RTEMS 5 for a PC?
>
>
> While I will be updating the commands in the blog, I am posting the same here 
> for easier reference:
>
> Building EPICS7 for RTEMS4.10 with pc-386:
>
> In order to do that, I made the directory
>
> i) $HOME/development/rtems/
> ii) I extracted rtems-4.10 from here 
> https://ftp.rtems.org/pub/rtems/releases/4.10/
> iii)I created another directory rtems/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/4.10 4.10/rtems-i386'.
> vi) Now the directory structure under $HOME/development/rtems/ looked like:
>   | rtems-4.10
>   | 4.10
>   | src/rsb
>   | kernel/pc386
> I also used this command: "export PATH=$HOME/development/rtems/4.10/bin:$PATH"
> vi) Then I went to rtems/rtems-4.10 and used this command:
> "./bootstrap -c && 
> $HOME/development/rtems/src/rsb/source-builder/sb-bootstrap"
> vi) After this I went insid directory $HOME/development/rtems/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 
> --enable-posix  --enable-rtemsbsp=pc386 --enable-tests=samples 
> --prefix=$HOME/development/rtems/4.10 --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/4.10/i386-rtems4.10/pc386''
> Location of epics-base in my system is as follows:
> "$HOME/development/EPICS/epics-base"
>

Re: [GSoC 2020]: Weekly thread update

2020-07-14 Thread Mritunjay Sharma 
On Wed, Jul 15, 2020 at 5:33 AM Chris Johns  wrote:

> On 15/7/20 4:30 am, Mritunjay Sharma wrote:
> > Hello everyone,
> >
> > Pardon my mistake for that long thread. From now on the daily updates
> will be
> > given on a thread that will end every week.
>
> Thank you :)
>
> > 1) I studied about https://github.com/RTEMS/rtems-libbsd
> > 2) Tried to fix the error that I reported yesterday:
> >
> > ```
>
> Why cut the compile command line used to build this file out of the
> message? The
> compiler command is important because it lets us see what paths are being
> used
> and I think there may be a problem with them.
>
> > ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file
> or directory
> >  #include 
> >   ^
>
> I cannot duplicate this because I am not sure what the sequence of
> commands are
> you used to get to here. I am sorry if I missed it in a previous post.
>
> The error indicates a set up issue. It normally means the networking
> software
> (rtems-libbsd) has not been installed into a prefix path EPICS looks in.
>

I am posting the entire command set further ahead in the email which will
make things
easier to understand.

>
> > 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
> >
> > ```
> >
> > I am still not successful even though I tried to search for it.
>
> I doubt there will be anything to search for. You are solving the problem
> and
> creating the first info to be searched. We need to debug the problem.
>
> > On the advice of Heinz, I have already built EPICS 7 with RTEMS4.10
> > by hand and am on the verge of doing the same for EPICS7 with RTEMS5
> > for pc-386.
>
> I am sorry I do not understand what "on the verge of doing the same" means.
>

I am sorry for the misunderstanding. It means that after these bugs are
resolved with this
discussion I will successfully be able to build EPICS7 with RTEMS5

>
> > However, I will like to request all my mentors to help me set the goals
> > for this week and where should I begin next?
>
> Could you please update your blog with the exact command sequences you are
> using
> to build EPICS7 for RTEMS 4.10 and EPICS7 for RTEMS 5 for a PC?
>

While I will be updating the commands in the blog, I am posting the same
here for easier reference:

Building EPICS7 for RTEMS4.10 with pc-386:

In order to do that, I made the directory

i) $HOME/development/rtems/
ii) I extracted rtems-4.10 from here
https://ftp.rtems.org/pub/rtems/releases/4.10/

iii)I created another directory rtems/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/4.10 4.10/rtems-i386'.
vi) Now the directory structure under $HOME/development/rtems/ looked like:
  | rtems-4.10
  | 4.10
  | src/rsb
  | kernel/pc386
I also used this command: "export
PATH=$HOME/development/rtems/4.10/bin:$PATH"
vi) Then I went to rtems/rtems-4.10 and used this command:
"./bootstrap -c &&
$HOME/development/rtems/src/rsb/source-builder/sb-bootstrap"
vi) After this I went insid directory $HOME/development/rtems/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 --enable-posix  --enable-rtemsbsp=pc386
--enable-tests=samples --prefix=$HOME/development/rtems/4.10 --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/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 Heinz sent to build EPICS for
rtems-4.10 for pc-386 which is:

> Very roughly:
> git clone —recursive epics-base
>
> in epics-base/configure/CONFIG_SITE
> set
>

Re: [GSoC 2020]: Weekly thread update

2020-07-14 Thread Chris Johns 
On 15/7/20 4:30 am, Mritunjay Sharma wrote:
> Hello everyone,
> 
> Pardon my mistake for that long thread. From now on the daily updates will be
> given on a thread that will end every week. 

Thank you :)

> 1) I studied about https://github.com/RTEMS/rtems-libbsd
> 2) Tried to fix the error that I reported yesterday: 
> 
> ```

Why cut the compile command line used to build this file out of the message? The
compiler command is important because it lets us see what paths are being used
and I think there may be a problem with them.

> ../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or 
> directory
>  #include 
>           ^

I cannot duplicate this because I am not sure what the sequence of commands are
you used to get to here. I am sorry if I missed it in a previous post.

The error indicates a set up issue. It normally means the networking software
(rtems-libbsd) has not been installed into a prefix path EPICS looks in.

> 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
> 
> ```
> 
> I am still not successful even though I tried to search for it. 

I doubt there will be anything to search for. You are solving the problem and
creating the first info to be searched. We need to debug the problem.

> On the advice of Heinz, I have already built EPICS 7 with RTEMS4.10
> by hand and am on the verge of doing the same for EPICS7 with RTEMS5 
> for pc-386. 

I am sorry I do not understand what "on the verge of doing the same" means.

> However, I will like to request all my mentors to help me set the goals
> for this week and where should I begin next?

Could you please update your blog with the exact command sequences you are using
to build EPICS7 for RTEMS 4.10 and EPICS7 for RTEMS 5 for a PC?

Have you run EPIRC7 for 4.10 in qemu? If so did the network come up and work?

Have you run the rtems-libbsd test executables in qemu?

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