<div dir="ltr">Thank you so much Gedare, I will do it and revert back to you.<div><br></div><div>Thanks</div><div>Mritunjay</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 4, 2020 at 3:01 AM Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Jul 3, 2020 at 3:07 PM Mritunjay Sharma<br>
<<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Fri, Jul 3, 2020 at 10:53 PM Mritunjay Sharma <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> ________________________________<br>
>> From: Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>><br>
>> Sent: Friday, July 3, 2020 9:42 PM<br>
>> To: Mritunjay Sharma<br>
>> Cc: Heinz Junkes; Chris Johns; RTEMS Devel<br>
>> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5<br>
>><br>
>> On Fri, Jul 3, 2020 at 9:17 AM Mritunjay Sharma<br>
>> <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
>> ><br>
>> > Hello Heinz and everyone,<br>
>> ><br>
>> > Thank you so much, with this email, I will try to clear all the things, and what is the status for now.<br>
>> ><br>
>> > First. let me tell you the current status: Vijay helped me last night in an offlist discussion to clear the confusions which<br>
>> > I was having (I will mention them below) due to which I was able to build and install RTEMS 4.10 for pc386 successfully.<br>
>> > With that, all my previous errors were resolved. Below is the detail of all the steps, I followed.<br>
>> ><br>
>> > Let me tell that my development environment was earlier set up for RTEMS5. For building EPICS with RTEMS,<br>
>> > I thought it will be right to first build RTEMS 4.10 for pc386.<br>
>> ><br>
>> > In order to do that, I made the directory<br>
>> ><br>
>> > i) $HOME/development/rtems_dev<br>
>> > ii) I extracted rtems-4.10.2 from here <a href="https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/" rel="noreferrer" target="_blank">https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/</a><br>
>> > iii)I created another directory rtems_dev/src<br>
>> > iv)Inside src, I cloned rsb and moved to 4.10 branch.<br>
>> > v) After performing checks, I entered to rsb/rtems and used this command:<br>
>> > '../source-builder/sb-set-builder --prefix=/home/mritunjay/development/rtems_dev/rtems-4.10.2 4.10/rtems-i386'<br>
>> > Even though the build completed successfully, this was the point where I made the error. I used the RTEMS source as the prefix which<br>
>> > was causing all the problems.<br>
>> > vi) After the discussion with Vijay and getting cleared, I deleted everything except the RTEMS RSB and restarted the process with prefix and source<br>
>> > different this time and rebuilt the compiler tools using RSB.<br>
>> > vii) Now the directory structure under $HOME/development/rtems_dev/ looked like:<br>
>> > | rtems-4.10.2<br>
>> > | 4.10<br>
>> > | src/rsb<br>
>> > | kernel/pc386<br>
>> > I also used this command: "export PATH=$HOME/development/rtems_dev/4.10/bin:$PATH"<br>
>> > vi) Then I went to rtems_dev/rtems-4.10.2 and used this command:<br>
>> > "./bootstrap -c && $HOME/development/rtems_dev/src/rsb/source-builder/sb-bootstrap"<br>
>> > vi) After this I went insid directory $HOME/development/rtems_dev/kernel/pc-386<br>
>> > vii) Inside pc-386, I used the following command:<br>
>> > ''$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"<br>
<br>
You need to --enable-posix<br>
<br>
>> > viii) Then I entered the make command which ran successfully and the make install was also successful.<br>
>> ><br>
>> > So all the errors were resolved and I moved on to build EPICS now for RTEMS 4.10.<br>
>> > I also used this command:<br>
>> > '''export RTEMS_MAKEFILE_PATH=$HOME/development/rtems_dev/4.10/i386-rtems4.10/pc386''<br>
>> > Location of epics-base in my system is as follows:<br>
>> > "$HOME/development/EPICS/epics-base"<br>
>> ><br>
>> > After this, I followed the tutorial you sent to build EPICS for rterms-4.10 for pc-386 which is:<br>
>> >><br>
>> >> Very roughly:<br>
>> >> git clone —recursive epics-base<br>
>> >><br>
>> >> in epics-base/configure/CONFIG_SITE<br>
>> >> set<br>
>> >> CROSS_COMPILER_TARGET_ARCHS=<br>
>> ><br>
>> > What I entered:<br>
>> > CROSS_COMPILER_TARGET_ARCHS= RTEMS-pc386<br>
>> >><br>
>> >> e.g. RTEMS-pc386<br>
>> >> or RTEMS-xilinx_zynq_a9_qemu<br>
>> >><br>
>> >> in epics-base/configure/os there must be a file for the target used,<br>
>> >> e.g.<br>
>> >> CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu<br>
>> >> or<br>
>> >> CONFIG.Common.RTEMS-pc386<br>
>> ><br>
>> > Checked. CONFIG.Common.RTEMS-pc386 was there<br>
>> >><br>
>> >><br>
>> >> Then you have to set in configure/os/CONFIG_SITE.Common.RTEMS<br>
>> >> where to find RTEMS:<br>
>> >><br>
>> >> # Where to find RTEMS<br>
>> >> #<br>
>> >> # APS:<br>
>> >> #RTEMS_VERSION = 4.10.2<br>
>> >> #RTEMS_BASE = /usr/local/vw/rtems/rtems-$(RTEMS_VERSION)<br>
>> ><br>
>> ><br>
>> > In my system, I entered this:<br>
>> > #APS<br>
>> > RTEMS_VERSION = 4.10<br>
>> > RTEMS_BASE = /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)<br>
>> ><br>
>> > I followed the above instructions and used the 'make' command.<br>
>> ><br>
>> ><br>
>> > While the earlier errors are resolved, The latest error that I have encountered is this after using make command.:<br>
>> ><br>
>> > ".......Info':<br>
>> > /home/mritunjay/development/EPICS/epics-base/modules/libcom/src/O.RTEMS-pc386/../osi/os/RTEMS/osdThread.c:747: undefined reference to `pthread_getschedparam'<br>
>> > collect2: ld returned 1 exit status<br>
>> > ../../../../configure/RULES_BUILD:212: recipe for target 'libComTestHarness' failed<br>
>> > make[4]: *** [libComTestHarness] Error 1<br>
>> > make[4]: Leaving directory '/home/mritunjay/development/EPICS/epics-base/modules/libcom/test/O.RTEMS-pc386'<br>
>> > ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed<br>
>> > make[3]: *** [install.RTEMS-pc386] Error 2<br>
>> > make[3]: Leaving directory '/home/mritunjay/development/EPICS/epics-base/modules/libcom/test'<br>
>> > ../../configure/RULES_DIRS:85: recipe for target 'test.install' failed<br>
>> > make[2]: *** [test.install] Error 2<br>
>> > make[2]: Leaving directory '/home/mritunjay/development/EPICS/epics-base/modules/libcom'<br>
>> > ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed<br>
>> > make[1]: *** [libcom.install] Error 2<br>
>> > make[1]: Leaving directory '/home/mritunjay/development/EPICS/epics-base/modules'<br>
>> > configure/RULES_DIRS:85: recipe for target 'modules.install' failed<br>
>> > make: *** [modules.install] Error 2"<br>
>> ><br>
>> > 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<br>
>> > of you to guide where I am going wrong.<br>
>> ><br>
>><br>
>> Probably the current epics-base is not working with 4.10.2 any longer?<br>
>><br>
>> The pthread_getschedparam() was introduced to allow epics-base to<br>
>> compile properly with the 4.10 HEAD (pending 4.10.3 release). Use the<br>
>> 4.10 HEAD instead of 4.10.2 release/tag and see how the process goes<br>
>> instead.<br>
>><br>
>> Thank you so much Gedare, I will check and revert as soon as possible.<br>
><br>
> I used the 4.10 HEAD as suggested by you and I cross-checked it using ` cat .git/HEAD`<br>
> which showed the following result: `ref: refs/heads/4.10`. I did the entire process again with 4.10 ahead but I got the<br>
> same error again after using 'make' in epics-base.<br>
><br>
> Thanks,<br>
> Mritunjay<br>
>><br>
>><br>
>> Mritunjay.<br>
>><br>
>> > Thanks,<br>
>> > Mritunjay<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > On Fri, Jul 3, 2020 at 9:03 AM Heinz Junkes <<a href="mailto:junkes@fhi-berlin.mpg.de" target="_blank">junkes@fhi-berlin.mpg.de</a>> wrote:<br>
>> >><br>
>> >> Hello, Mritunjay,<br>
>> >><br>
>> >> unfortunately i still miss a transcript in which the things you do are listed in detail.<br>
>> >> Then we could really help you better.<br>
>> >><br>
>> >> Heinz<br>
>> >><br>
>> >> > On 3. Jul 2020, at 04:14, Chris Johns <<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>> wrote:<br>
>> >> ><br>
>> >> > On 3/7/20 9:01 am, Mritunjay Sharma wrote:<br>
>> >> >> Thank you so much Gedare, I think the problem was with confusion related to<br>
>> >> >> prefix and source being the same which created a lot of problems.<br>
>> >> >><br>
>> >> >> I just had an offlist discussion with Vijay and he has cleared all my doubts and<br>
>> >> >> the mistakes I was making. The problem as of now seems to be resolved.<br>
>> >> ><br>
>> >> > Vijay, thanks for helping and Mritunjay thank you for letting us know.<br>
>> >> ><br>
>> >> > Chris<br>
>> >> > _______________________________________________<br>
>> >> > devel mailing list<br>
>> >> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
>> >> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
>> >><br>
</blockquote></div>