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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

Reply via email to