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 <rtems/bsd.h>` from existing >>> `#include <rtems/bsd/bsd.h>` 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 <rtems/bsd/bsd.h>"). >>> >>> 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 <rtems/dhcpcd.h> >>> ` >>> 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 <rtems/stackchk.h> >>>> #include <rtems/rtems_bsdnet.h> >>>> #include <rtems/imfs.h> >>>> #include <librtemsNfs.h> >>>> #include <bsp.h> >>>> … >>>> Here the definition of the legacy stack will be included >>>> >>>> #include <rtems/rtems_bsdnet.h> >>>> >>>> >>>> >>>> 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 <chr...@rtems.org> 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 <rtems/bsd/bsd.h> >>>> > > ^~~~~~~~~~~~~~~~~ >>>> > >>>> > 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