[Announcement]: Developed an automating tool that can help RTEMS conform with Python coding style

[Mritunjay Sharma]

Hello everyone!

After recently seeing the Python Development
guidelines for RTEMS, I found that
"RTEMS Tools should be piped through the yapf Python code
formatter before it is committed or sent for review."

This gave me an idea to build something that can automate
this process and take the pressure off both from
Maintainers as well as Contributors.

I am pleased to tell you that I have successfully implemented this
idea by building an open-source GitHub action called 'autoyapf'.

Link to the tool is: https://github.com/marketplace/actions/autoyapf
Link to the github repo: https://github.com/mritunjaysharma394/autoyapf

What it does is that whenever a maintainer pushes a python code in the repo
or merges a PR of a contributor containing Python code, autoyapf action is
triggered and it automatically checks if the file is piped in 'yapf' format
or not
and if not then it will automatically commit the changes in concerned file
to make it follow the PEP 8 style guide using yapf.

This action will immensely help in increasing the speed of the development
cycle of
RTEMS projects that use Python.

I will request all of you to please have a look at the project and give me
your
valuable feedback to improve.
I sincerely hope that this project can find it's use in RTEMS projects

Thanks a lot!
Mritunjay Sharma
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2020: Final Report for BSP Buildset For EPICS

[Mritunjay Sharma]

Thank you so much all the mentors!

I have completed my evaluation :)

I will continue contributing and make this project better
and better. Thank you so much for being kind and understanding
always!

Mritunjay

On Sun, Aug 30, 2020 at 2:26 AM Gedare Bloom  wrote:

> Thanks, this looks fine.
>
> On Sat, Aug 29, 2020 at 2:53 PM Mritunjay Sharma
>  wrote:
> >
> > Thanks a lot for the feedback!
> >
> > I have consolidated in one section all commits written by me as advised
> by you!
> >
> > Here's the link:  http://bit.ly/gsoc-2020-final-report
> >
> > Thank you so much!
> >
> > On Sat, Aug 29, 2020 at 4:15 AM Gedare Bloom  wrote:
> >>
> >> Please consolidate in one section all the links to "your code
> >> written". I found the way you did it in Phases makes it a little hard
> >> to parse. otherwise, looks great thanks!
> >>
> >> On Thu, Aug 27, 2020 at 4:28 PM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > Hello everyone,
> >> >
> >> > First of all, thank you so much to all the mentors
> >> > for being so supportive and helpful that helped me out
> >> > with this project.
> >> >
> >> > I have tried to make a final report which is detailed and with my
> >> > code links. This is the link to my final report:
> http://bit.ly/gsoc-2020-final-report
> >> >
> >> > Please do a review and share your feedback and suggestions
> >> > for any improvements.
> >> >
> >> > Thank you so much!
> >> > Mritunjay Sharma
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2020: Final Report for BSP Buildset For EPICS

[Mritunjay Sharma]

Thanks a lot for the feedback!

I have consolidated in one section all commits written by me as advised by
you!

Here's the link:  http://bit.ly/gsoc-2020-final-report

Thank you so much!

On Sat, Aug 29, 2020 at 4:15 AM Gedare Bloom  wrote:

> Please consolidate in one section all the links to "your code
> written". I found the way you did it in Phases makes it a little hard
> to parse. otherwise, looks great thanks!
>
> On Thu, Aug 27, 2020 at 4:28 PM Mritunjay Sharma
>  wrote:
> >
> > Hello everyone,
> >
> > First of all, thank you so much to all the mentors
> > for being so supportive and helpful that helped me out
> > with this project.
> >
> > I have tried to make a final report which is detailed and with my
> > code links. This is the link to my final report:
> http://bit.ly/gsoc-2020-final-report
> >
> > Please do a review and share your feedback and suggestions
> > for any improvements.
> >
> > Thank you so much!
> > Mritunjay Sharma
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

GSoC 2020: Final Report for BSP Buildset For EPICS

[Mritunjay Sharma]

Hello everyone,

First of all, thank you so much to all the mentors
for being so supportive and helpful that helped me out
with this project.

I have tried to make a final report which is detailed and with my
code links. This is the link to my final report:
http://bit.ly/gsoc-2020-final-report

Please do a review and share your feedback and suggestions
for any improvements.

Thank you so much!
Mritunjay Sharma
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

I have sent the tested patch and it can be found here:
https://lists.rtems.org/pipermail/devel/2020-August/061655.html.

Please do review.
Thank you so much and apologies again for the mistake.

Mritunjay Sharma

On Fri, Aug 28, 2020 at 3:21 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> [UPDATE]: My humble apologies as that patch had a problem. I forgot to add
> $ before the variable {source_dir_epics}
> which was causing the build to fail. Please ignore the above patch.
>
> I am sending the new tested patch again. Apologies for this inconvenience.
>
> Thanks
> Mritunjay Kumar Sharma
>
>
> On Fri, Aug 28, 2020 at 12:30 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>> Added commit message and removed Signed off
>> Please review.
>>
>> Adding EPICS7 Package to RSB for Building it with RTEMS
>>
>> ---
>>  rtems/config/epics/epics-7.0-1.cfg| 21 +
>>  rtems/config/epics/epics-base.bset| 14 ++
>>  source-builder/config/epics-7.0-1.cfg | 65 +++
>>  3 files changed, 100 insertions(+)
>>  create mode 100644 rtems/config/epics/epics-7.0-1.cfg
>>  create mode 100644 rtems/config/epics/epics-base.bset
>>  create mode 100644 source-builder/config/epics-7.0-1.cfg
>>
>> diff --git a/rtems/config/epics/epics-7.0-1.cfg
>> b/rtems/config/epics/epics-7.0-1.cfg
>> new file mode 100644
>> index 000..34270ee
>> --- /dev/null
>> +++ b/rtems/config/epics/epics-7.0-1.cfg
>> @@ -0,0 +1,21 @@
>> +#
>> +# EPICS 7.0
>> +#
>> +
>> +%if %{release} == %{nil}
>> + %define release 1
>> +%endif
>> +
>> +%include %{_configdir}/rtems-bsp.cfg
>> +
>> +#
>> +# EPICS Version
>> +#
>> +%define epics_version 7.0
>> +
>> +%hash sha512 epics-base-%{epics_version}.tar.gz
>> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
>> +
>> +#
>> +# EPICS Build configuration
>> +#
>> +%include %{_configdir}/epics-7.0-1.cfg
>> diff --git a/rtems/config/epics/epics-base.bset
>> b/rtems/config/epics/epics-base.bset
>> new file mode 100644
>> index 000..7ee3815
>> --- /dev/null
>> +++ b/rtems/config/epics/epics-base.bset
>> @@ -0,0 +1,14 @@
>> +#
>> +# Build set for EPICS
>> +#
>> +%define release 1
>> +
>> +#
>> +# The RTEMS Package defines
>> +#
>> +%include rtems-package.bset
>> +
>> +#
>> +# Build EPICS.
>> +#
>> +epics/epics-7.0-1
>> diff --git a/source-builder/config/epics-7.0-1.cfg
>> b/source-builder/config/epics-7.0-1.cfg
>> new file mode 100644
>> index 000..df75e1d
>> --- /dev/null
>> +++ b/source-builder/config/epics-7.0-1.cfg
>> @@ -0,0 +1,65 @@
>> +#
>> +# EPICS 7.x.x Version 1.
>> +#
>> +# This configuration file configure's, make's and install's EPICS.
>> +#
>> +
>> +%if %{release} == %{nil}
>> +%define release 1
>> +%endif
>> +
>> +%define epics_version 7.0
>> +
>> +Name:  epics-base-%{epics_version}-%{_host}-%{release}
>> +Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
>> +Version:   %{epics_version}
>> +Release:   %{release}
>> +URL: https://epics-controls.org/
>> +
>> +#
>> +# Source
>> +#
>> +%source set epics-base
>> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
>> +
>> +#
>> +# Prepare the source code.
>> +#
>> +%prep
>> +  build_top=$(pwd)
>> +
>> +  source_dir_epics="epics-base-%{epics_version}"
>> +
>> +  %source setup epics-base -q -n source_dir_epics
>> +
>> +  cd ${build_top}
>> +
>> +%build
>> +  build_top=$(pwd)
>> +
>> +  cd source_dir_epics
>> +
>> +  %{build_build_flags}
>> +
>> +  #
>> +  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION
>> using
>> +  # --with-rtems-bsp
>> +  #
>> +  %{__make} RTEMS_BASE=%{_prefix} \
>> +  RTEMS_VERSION=%{rtems_version} \
>> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
>> +
>> +  cd ${build_top}
>> +
>> +#%install
>> +  build_top=$(pwd)
>> +
>> +  %{__rmdir} $SB_BUILD_ROOT
>> +
>> +  cd source_dir_epics
>> +
>> +  %{__make} DESTDIR=$SB_BUILD_ROOT \
>> +  RTEMS_BASE=%{_prefix} \
>> +  RTEMS_VERSION=%{rtems_version} \
>> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
>> +
>> +  cd ${build_top}
>> --
>> 2.25.1
>>
>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] rsb: Adding EPICS7 Package to RTEMS RSB

[Mritunjay Sharma]

rsb: Adding EPICS7 Package to RTEMS RSB
---
 rtems/config/epics/epics-7.0-1.cfg| 21 +
 rtems/config/epics/epics-base.bset| 14 ++
 source-builder/config/epics-7.0-1.cfg | 65 +++
 3 files changed, 100 insertions(+)
 create mode 100644 rtems/config/epics/epics-7.0-1.cfg
 create mode 100644 rtems/config/epics/epics-base.bset
 create mode 100644 source-builder/config/epics-7.0-1.cfg

diff --git a/rtems/config/epics/epics-7.0-1.cfg 
b/rtems/config/epics/epics-7.0-1.cfg
new file mode 100644
index 000..34270ee
--- /dev/null
+++ b/rtems/config/epics/epics-7.0-1.cfg
@@ -0,0 +1,21 @@
+#
+# EPICS 7.0
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 7.0
+
+%hash sha512 epics-base-%{epics_version}.tar.gz 
63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
+
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7.0-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
new file mode 100644
index 000..7ee3815
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,14 @@
+#
+# Build set for EPICS
+#
+%define release 1
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+#
+# Build EPICS.
+#
+epics/epics-7.0-1
diff --git a/source-builder/config/epics-7.0-1.cfg 
b/source-builder/config/epics-7.0-1.cfg
new file mode 100644
index 000..c255dc3
--- /dev/null
+++ b/source-builder/config/epics-7.0-1.cfg
@@ -0,0 +1,65 @@
+#
+# EPICS 7.x.x Version 1.
+#
+# This configuration file configure's, make's and install's EPICS.
+#
+
+%if %{release} == %{nil}
+%define release 1
+%endif
+
+%define epics_version 7.0
+
+Name:  epics-base-%{epics_version}-%{_host}-%{release}
+Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
+Version:   %{epics_version}
+Release:   %{release}
+URL: https://epics-controls.org/
+
+#
+# Source
+#
+%source set epics-base 
https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
+
+#
+# Prepare the source code.
+#
+%prep
+  build_top=$(pwd)
+
+  source_dir_epics="epics-base-%{epics_version}"
+
+  %source setup epics-base -q -n ${source_dir_epics}
+
+  cd ${build_top}
+
+%build
+  build_top=$(pwd)
+
+  cd ${source_dir_epics}
+
+  %{build_build_flags}
+
+  #
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
+  # --with-rtems-bsp
+  #
+  %{__make} RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+
+  cd ${build_top}
+
+#%install
+  build_top=$(pwd)
+
+  %{__rmdir} $SB_BUILD_ROOT
+
+  cd ${source_dir_epics}
+
+  %{__make} DESTDIR=$SB_BUILD_ROOT \
+  RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
+
+  cd ${build_top}
-- 
2.25.1

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

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

[UPDATE]: My humble apologies as that patch had a problem. I forgot to add
$ before the variable {source_dir_epics}
which was causing the build to fail. Please ignore the above patch.

I am sending the new tested patch again. Apologies for this inconvenience.

Thanks
Mritunjay Kumar Sharma


On Fri, Aug 28, 2020 at 12:30 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Added commit message and removed Signed off
> Please review.
>
> Adding EPICS7 Package to RSB for Building it with RTEMS
>
> ---
>  rtems/config/epics/epics-7.0-1.cfg| 21 +
>  rtems/config/epics/epics-base.bset| 14 ++
>  source-builder/config/epics-7.0-1.cfg | 65 +++
>  3 files changed, 100 insertions(+)
>  create mode 100644 rtems/config/epics/epics-7.0-1.cfg
>  create mode 100644 rtems/config/epics/epics-base.bset
>  create mode 100644 source-builder/config/epics-7.0-1.cfg
>
> diff --git a/rtems/config/epics/epics-7.0-1.cfg
> b/rtems/config/epics/epics-7.0-1.cfg
> new file mode 100644
> index 000..34270ee
> --- /dev/null
> +++ b/rtems/config/epics/epics-7.0-1.cfg
> @@ -0,0 +1,21 @@
> +#
> +# EPICS 7.0
> +#
> +
> +%if %{release} == %{nil}
> + %define release 1
> +%endif
> +
> +%include %{_configdir}/rtems-bsp.cfg
> +
> +#
> +# EPICS Version
> +#
> +%define epics_version 7.0
> +
> +%hash sha512 epics-base-%{epics_version}.tar.gz
> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
> +
> +#
> +# EPICS Build configuration
> +#
> +%include %{_configdir}/epics-7.0-1.cfg
> diff --git a/rtems/config/epics/epics-base.bset
> b/rtems/config/epics/epics-base.bset
> new file mode 100644
> index 000..7ee3815
> --- /dev/null
> +++ b/rtems/config/epics/epics-base.bset
> @@ -0,0 +1,14 @@
> +#
> +# Build set for EPICS
> +#
> +%define release 1
> +
> +#
> +# The RTEMS Package defines
> +#
> +%include rtems-package.bset
> +
> +#
> +# Build EPICS.
> +#
> +epics/epics-7.0-1
> diff --git a/source-builder/config/epics-7.0-1.cfg
> b/source-builder/config/epics-7.0-1.cfg
> new file mode 100644
> index 000..df75e1d
> --- /dev/null
> +++ b/source-builder/config/epics-7.0-1.cfg
> @@ -0,0 +1,65 @@
> +#
> +# EPICS 7.x.x Version 1.
> +#
> +# This configuration file configure's, make's and install's EPICS.
> +#
> +
> +%if %{release} == %{nil}
> +%define release 1
> +%endif
> +
> +%define epics_version 7.0
> +
> +Name:  epics-base-%{epics_version}-%{_host}-%{release}
> +Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
> +Version:   %{epics_version}
> +Release:   %{release}
> +URL: https://epics-controls.org/
> +
> +#
> +# Source
> +#
> +%source set epics-base
> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
> +
> +#
> +# Prepare the source code.
> +#
> +%prep
> +  build_top=$(pwd)
> +
> +  source_dir_epics="epics-base-%{epics_version}"
> +
> +  %source setup epics-base -q -n source_dir_epics
> +
> +  cd ${build_top}
> +
> +%build
> +  build_top=$(pwd)
> +
> +  cd source_dir_epics
> +
> +  %{build_build_flags}
> +
> +  #
> +  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
> +  # --with-rtems-bsp
> +  #
> +  %{__make} RTEMS_BASE=%{_prefix} \
> +  RTEMS_VERSION=%{rtems_version} \
> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
> +
> +  cd ${build_top}
> +
> +#%install
> +  build_top=$(pwd)
> +
> +  %{__rmdir} $SB_BUILD_ROOT
> +
> +  cd source_dir_epics
> +
> +  %{__make} DESTDIR=$SB_BUILD_ROOT \
> +  RTEMS_BASE=%{_prefix} \
> +  RTEMS_VERSION=%{rtems_version} \
> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
> +
> +  cd ${build_top}
> --
> 2.25.1
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Added commit message and removed Signed off
Please review. 

Adding EPICS7 Package to RSB for Building it with RTEMS

---
 rtems/config/epics/epics-7.0-1.cfg| 21 +
 rtems/config/epics/epics-base.bset| 14 ++
 source-builder/config/epics-7.0-1.cfg | 65 +++
 3 files changed, 100 insertions(+)
 create mode 100644 rtems/config/epics/epics-7.0-1.cfg
 create mode 100644 rtems/config/epics/epics-base.bset
 create mode 100644 source-builder/config/epics-7.0-1.cfg

diff --git a/rtems/config/epics/epics-7.0-1.cfg 
b/rtems/config/epics/epics-7.0-1.cfg
new file mode 100644
index 000..34270ee
--- /dev/null
+++ b/rtems/config/epics/epics-7.0-1.cfg
@@ -0,0 +1,21 @@
+#
+# EPICS 7.0
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 7.0
+
+%hash sha512 epics-base-%{epics_version}.tar.gz 
63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
+
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7.0-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
new file mode 100644
index 000..7ee3815
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,14 @@
+#
+# Build set for EPICS
+#
+%define release 1
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+#
+# Build EPICS.
+#
+epics/epics-7.0-1
diff --git a/source-builder/config/epics-7.0-1.cfg 
b/source-builder/config/epics-7.0-1.cfg
new file mode 100644
index 000..df75e1d
--- /dev/null
+++ b/source-builder/config/epics-7.0-1.cfg
@@ -0,0 +1,65 @@
+#
+# EPICS 7.x.x Version 1.
+#
+# This configuration file configure's, make's and install's EPICS.
+#
+
+%if %{release} == %{nil}
+%define release 1
+%endif
+
+%define epics_version 7.0
+
+Name:  epics-base-%{epics_version}-%{_host}-%{release}
+Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
+Version:   %{epics_version}
+Release:   %{release}
+URL: https://epics-controls.org/
+
+#
+# Source
+#
+%source set epics-base 
https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
+
+#
+# Prepare the source code.
+#
+%prep
+  build_top=$(pwd)
+
+  source_dir_epics="epics-base-%{epics_version}"
+
+  %source setup epics-base -q -n source_dir_epics
+
+  cd ${build_top}
+
+%build
+  build_top=$(pwd)
+
+  cd source_dir_epics
+
+  %{build_build_flags}
+
+  #
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
+  # --with-rtems-bsp
+  #
+  %{__make} RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+
+  cd ${build_top}
+
+#%install
+  build_top=$(pwd)
+
+  %{__rmdir} $SB_BUILD_ROOT
+
+  cd source_dir_epics
+
+  %{__make} DESTDIR=$SB_BUILD_ROOT \
+  RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
+
+  cd ${build_top}
-- 
2.25.1

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

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Thanks, on it, sending it in a while.

Mritunjay

From: Gedare Bloom 
Sent: Friday, August 28, 2020 12:24:26 AM
To: Mritunjay Sharma 
Cc: devel@rtems.org ; Chris Johns ; Heinz 
Junkes 
Subject: Re: [PATCH] Adding EPICS7 Package to RSB

On Thu, Aug 27, 2020 at 11:48 AM Mritunjay Sharma
 wrote:
>
> Made suggested changes
> Please review.
>
> Adding EPICS7 Package to RSB
>
> Adding EPICS7 Package to RSB:Fixed minor changes

combine the commit message into what you would like it to say when it
gets pushed.

>
> Signed-off-by: Mritunjay Sharma 

We don't use sign-off for RTEMS repos.

> ---
>  rtems/config/epics/epics-7.0-1.cfg| 21 +
>  rtems/config/epics/epics-base.bset| 14 ++
>  source-builder/config/epics-7.0-1.cfg | 65 +++
>  3 files changed, 100 insertions(+)
>  create mode 100644 rtems/config/epics/epics-7.0-1.cfg
>  create mode 100644 rtems/config/epics/epics-base.bset
>  create mode 100644 source-builder/config/epics-7.0-1.cfg
>
> diff --git a/rtems/config/epics/epics-7.0-1.cfg 
> b/rtems/config/epics/epics-7.0-1.cfg
> new file mode 100644
> index 000..34270ee
> --- /dev/null
> +++ b/rtems/config/epics/epics-7.0-1.cfg
> @@ -0,0 +1,21 @@
> +#
> +# EPICS 7.0
> +#
> +
> +%if %{release} == %{nil}
> + %define release 1
> +%endif
> +
> +%include %{_configdir}/rtems-bsp.cfg
> +
> +#
> +# EPICS Version
> +#
> +%define epics_version 7.0
> +
> +%hash sha512 epics-base-%{epics_version}.tar.gz 
> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
> +
> +#
> +# EPICS Build configuration
> +#
> +%include %{_configdir}/epics-7.0-1.cfg
> diff --git a/rtems/config/epics/epics-base.bset 
> b/rtems/config/epics/epics-base.bset
> new file mode 100644
> index 000..7ee3815
> --- /dev/null
> +++ b/rtems/config/epics/epics-base.bset
> @@ -0,0 +1,14 @@
> +#
> +# Build set for EPICS
> +#
> +%define release 1
> +
> +#
> +# The RTEMS Package defines
> +#
> +%include rtems-package.bset
> +
> +#
> +# Build EPICS.
> +#
> +epics/epics-7.0-1
> diff --git a/source-builder/config/epics-7.0-1.cfg 
> b/source-builder/config/epics-7.0-1.cfg
> new file mode 100644
> index 000..df75e1d
> --- /dev/null
> +++ b/source-builder/config/epics-7.0-1.cfg
> @@ -0,0 +1,65 @@
> +#
> +# EPICS 7.x.x Version 1.
why x.x? should it be 7.0?

> +#
> +# This configuration file configure's, make's and install's EPICS.
> +#
> +
> +%if %{release} == %{nil}
> +%define release 1
> +%endif
> +
> +%define epics_version 7.0
> +
> +Name:  epics-base-%{epics_version}-%{_host}-%{release}
> +Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
> +Version:   %{epics_version}
> +Release:   %{release}
> +URL: https://epics-controls.org/
> +
> +#
> +# Source
> +#
> +%source set epics-base 
> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
> +
> +#
> +# Prepare the source code.
> +#
> +%prep
> +  build_top=$(pwd)
> +
> +  source_dir_epics="epics-base-%{epics_version}"
> +
> +  %source setup epics-base -q -n source_dir_epics
does this work? I would think it needs a variable expansion like % or $.

> +
> +  cd ${build_top}
> +
> +%build
> +  build_top=$(pwd)
> +
> +  cd source_dir_epics
ditto.  Did you test this patch before sending it?

> +
> +  %{build_build_flags}
> +
> +  #
> +  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
> +  # --with-rtems-bsp
> +  #
> +  %{__make} RTEMS_BASE=%{_prefix} \
> +  RTEMS_VERSION=%{rtems_version} \
> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
> +
> +  cd ${build_top}
> +
> +#%install
> +  build_top=$(pwd)
> +
> +  %{__rmdir} $SB_BUILD_ROOT
> +
> +  cd source_dir_epics
> +
> +  %{__make} DESTDIR=$SB_BUILD_ROOT \
> +  RTEMS_BASE=%{_prefix} \
> +  RTEMS_VERSION=%{rtems_version} \
> +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
> +
> +  cd ${build_top}
> --
> 2.25.1
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Made suggested changes
Please review. 

Adding EPICS7 Package to RSB

Adding EPICS7 Package to RSB:Fixed minor changes

Signed-off-by: Mritunjay Sharma 
---
 rtems/config/epics/epics-7.0-1.cfg| 21 +
 rtems/config/epics/epics-base.bset| 14 ++
 source-builder/config/epics-7.0-1.cfg | 65 +++
 3 files changed, 100 insertions(+)
 create mode 100644 rtems/config/epics/epics-7.0-1.cfg
 create mode 100644 rtems/config/epics/epics-base.bset
 create mode 100644 source-builder/config/epics-7.0-1.cfg

diff --git a/rtems/config/epics/epics-7.0-1.cfg 
b/rtems/config/epics/epics-7.0-1.cfg
new file mode 100644
index 000..34270ee
--- /dev/null
+++ b/rtems/config/epics/epics-7.0-1.cfg
@@ -0,0 +1,21 @@
+#
+# EPICS 7.0
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 7.0
+
+%hash sha512 epics-base-%{epics_version}.tar.gz 
63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
+
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7.0-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
new file mode 100644
index 000..7ee3815
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,14 @@
+#
+# Build set for EPICS
+#
+%define release 1
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+#
+# Build EPICS.
+#
+epics/epics-7.0-1
diff --git a/source-builder/config/epics-7.0-1.cfg 
b/source-builder/config/epics-7.0-1.cfg
new file mode 100644
index 000..df75e1d
--- /dev/null
+++ b/source-builder/config/epics-7.0-1.cfg
@@ -0,0 +1,65 @@
+#
+# EPICS 7.x.x Version 1.
+#
+# This configuration file configure's, make's and install's EPICS.
+#
+
+%if %{release} == %{nil}
+%define release 1
+%endif
+
+%define epics_version 7.0
+
+Name:  epics-base-%{epics_version}-%{_host}-%{release}
+Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
+Version:   %{epics_version}
+Release:   %{release}
+URL: https://epics-controls.org/
+
+#
+# Source
+#
+%source set epics-base 
https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
+
+#
+# Prepare the source code.
+#
+%prep
+  build_top=$(pwd)
+
+  source_dir_epics="epics-base-%{epics_version}"
+
+  %source setup epics-base -q -n source_dir_epics
+
+  cd ${build_top}
+
+%build
+  build_top=$(pwd)
+
+  cd source_dir_epics
+
+  %{build_build_flags}
+
+  #
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
+  # --with-rtems-bsp
+  #
+  %{__make} RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+
+  cd ${build_top}
+
+#%install
+  build_top=$(pwd)
+
+  %{__rmdir} $SB_BUILD_ROOT
+
+  cd source_dir_epics
+
+  %{__make} DESTDIR=$SB_BUILD_ROOT \
+  RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
+
+  cd ${build_top}
-- 
2.25.1

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

Re: [PATCH v2] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Thank you for the feedback, Gedare.

Sending in the new patch soon.

Thanks
Mritunjay

On Thu, Aug 27, 2020 at 9:19 PM Gedare Bloom  wrote:

> Mritunjay,
>
> On Wed, Aug 26, 2020 at 3:58 PM Mritunjay Sharma
>  wrote:
> >
> > Modified as per the suggestions of Dr. Gedare. Please do review
> > Signed-off-by: Mritunjay Sharma 
> > ---
> >  .../epics/{epics-7-1.cfg => epics-7.0-1.cfg}  |  5 ++--
> >  rtems/config/epics/epics-base.bset| 14 +--
> >  .../config/{epics-7-1.cfg => epics-7.0-1.cfg} | 24 ---
> >  3 files changed, 19 insertions(+), 24 deletions(-)
> >  rename rtems/config/epics/{epics-7-1.cfg => epics-7.0-1.cfg} (87%)
> >  rename source-builder/config/{epics-7-1.cfg => epics-7.0-1.cfg} (64%)
> >
> > diff --git a/rtems/config/epics/epics-7-1.cfg
> b/rtems/config/epics/epics-7.0-1.cfg
> > similarity index 87%
> > rename from rtems/config/epics/epics-7-1.cfg
> > rename to rtems/config/epics/epics-7.0-1.cfg
> > index 30ed9cb..34270ee 100644
> > --- a/rtems/config/epics/epics-7-1.cfg
> > +++ b/rtems/config/epics/epics-7.0-1.cfg
> > @@ -1,5 +1,5 @@
> >  #
> > -# EPICS 7
> > +# EPICS 7.0
> >  #
> >
> >  %if %{release} == %{nil}
> > @@ -15,8 +15,7 @@
> >
> >  %hash sha512 epics-base-%{epics_version}.tar.gz
> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
> >
> > -#
> >  #
> >  # EPICS Build configuration
> >  #
> > -%include %{_configdir}/epics-7-1.cfg
> > +%include %{_configdir}/epics-7.0-1.cfg
> > diff --git a/rtems/config/epics/epics-base.bset
> b/rtems/config/epics/epics-base.bset
> > index e56fc6a..7ee3815 100644
> > --- a/rtems/config/epics/epics-base.bset
> > +++ b/rtems/config/epics/epics-base.bset
> > @@ -1,26 +1,14 @@
> >  #
> >  # Build set for EPICS
> >  #
> > -
> >  %define release 1
> >
> > -#
> > -# RTEMS Version
> > -#
> > -%define rtems_version 5
> > -
> > -#
> > -# The RTEMS URL paths.
> > -#
> > -%include rtems-urls.bset
> > -
> >  #
> >  # The RTEMS Package defines
> >  #
> >  %include rtems-package.bset
> >
> > -
> >  #
> >  # Build EPICS.
> >  #
> > -epics/epics-7-1 .
> > \ No newline at end of file
> > +epics/epics-7.0-1
> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7.0-1.cfg
> > similarity index 64%
> > rename from source-builder/config/epics-7-1.cfg
> > rename to source-builder/config/epics-7.0-1.cfg
> > index 2a52ea5..2a06008 100644
> > --- a/source-builder/config/epics-7-1.cfg
> > +++ b/source-builder/config/epics-7.0-1.cfg
> > @@ -27,7 +27,7 @@ URL:https://epics.mpg.de/
> >  %prep
> >build_top=$(pwd)
> >
> > -  source_dir_epics="epics-base-%{epics_version}"
> > + # source_dir_epics="epics-base-%{epics_version}"
> you can keep this variable, that wasn't my point.
>
> >
> >%source setup epics-base -q -n epics-base-%{epics_version}
> I was wondering if you should/could use the variable here?
>
> >
> > @@ -36,22 +36,30 @@ URL:  https://epics.mpg.de/
> >  %build
> >build_top=$(pwd)
> >
> > -  cd ${source_dir_epics}
> > +  cd epics-base-%{epics_version}
>
> and here. not that the name is likely to change, but it is good
> programming to use a variable to store something that gets used
> repeatedly.
>
> >
> >%{build_build_flags}
> >
> >#
> > -  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION
> using --with-rtems-bsp
> > +  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION
> using
> > +  # --with-rtems-bsp
> >#
> > -  %{__make} RTEMS_BASE=%{_prefix} RTEMS_VERSION=%{rtems_version}
> CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
> > +  %{__make} RTEMS_BASE=%{_prefix} \
> > +   RTEMS_VERSION=%{rtems_version} \
> > +   CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
> indent these broken lines, probably two "nesting levels" (maybe 4 spaces?)
>
> >
> >cd ${build_top}
> >
> > -%install
> > +#%install
> >build_top=$(pwd)
> >
> > -  rm -rf $SB_BUILD_ROOT
> > +  %{__rmdir} $SB_BUILD_ROOT
> > +
> > +  cd epics-base-%{epics_version}
> keep source_dir-epics
>
> > +
> > +  %{__make} DESTDIR=$SB_BUILD_ROOT \
> > +  RTEMS_BASE=%{_prefix} \
> > +  RTEMS_VERSION=%{rtems_version} \
> > +  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
> ditto
>
> >
> > -  cd ${source_dir_epics}
> > -  %{__make} DESTDIR=$SB_BUILD_ROOT RTEMS_BASE=%{_prefix}
> RTEMS_VERSION=%{rtems_version}
> CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
> >cd ${build_top}
> > --
>
> after you make these changes and fix the URL, send a new single patch
> with all changes squashed together.
>
> > 2.25.1
> >
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

On Thu, Aug 27, 2020 at 2:15 PM Heinz Junkes 
wrote:

> Dear Mritunjay,
>
>
> > On 26. Aug 2020, at 23:34, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >
> > > +Name:  epics-base-%{epics_version}-%{_host}-%{release}
> > > +Summary:   EPICS v%{epics_version} for target %{_target} on host
> %{_host}
> > > +Version:   %{epics_version}
> > > +Release:   %{release}
> > > +URL: https://epics.mpg.de/
> > This doesn't look like the right url.
> >
> > I cross-checked and it seems to be working.
>
>
> The link should be
> https://epics-controls.org/
> please.
>
> My apologies for this. I will update with the above link. Thank you so
much!

>
> >
> > > +
> > > +#
> > > +# Source
> > > +#
> > > +%source set epics-base
> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
> > ditto
> >
> > where do official EPICS releases go?
> >
> > I think we need Heinz intervention in this and I am ready to help him
> get it done.
> > We have to use this repo for the time being.
>
> Yes, please leave it like this temporarily. I am working on the
> integration into the official release and then
> the link will change something like this:
>
> git clone //https://github.com/epics-base/epics-base.git
>
> or possibly then also set to a fix release, like:
> https://github.com/epics-base/epics-base/releases/tag/R7.0.4.1


Definitely, thank you so much!

Mritunjay


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

[PATCH v2] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Modified as per the suggestions of Dr. Gedare. Please do review
Signed-off-by: Mritunjay Sharma 
---
 .../epics/{epics-7-1.cfg => epics-7.0-1.cfg}  |  5 ++--
 rtems/config/epics/epics-base.bset| 14 +--
 .../config/{epics-7-1.cfg => epics-7.0-1.cfg} | 24 ---
 3 files changed, 19 insertions(+), 24 deletions(-)
 rename rtems/config/epics/{epics-7-1.cfg => epics-7.0-1.cfg} (87%)
 rename source-builder/config/{epics-7-1.cfg => epics-7.0-1.cfg} (64%)

diff --git a/rtems/config/epics/epics-7-1.cfg 
b/rtems/config/epics/epics-7.0-1.cfg
similarity index 87%
rename from rtems/config/epics/epics-7-1.cfg
rename to rtems/config/epics/epics-7.0-1.cfg
index 30ed9cb..34270ee 100644
--- a/rtems/config/epics/epics-7-1.cfg
+++ b/rtems/config/epics/epics-7.0-1.cfg
@@ -1,5 +1,5 @@
 #
-# EPICS 7
+# EPICS 7.0
 #
 
 %if %{release} == %{nil}
@@ -15,8 +15,7 @@
 
 %hash sha512 epics-base-%{epics_version}.tar.gz 
63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
 
-#
 #
 # EPICS Build configuration
 #
-%include %{_configdir}/epics-7-1.cfg
+%include %{_configdir}/epics-7.0-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
index e56fc6a..7ee3815 100644
--- a/rtems/config/epics/epics-base.bset
+++ b/rtems/config/epics/epics-base.bset
@@ -1,26 +1,14 @@
 #
 # Build set for EPICS
 #
-
 %define release 1
 
-#
-# RTEMS Version
-#
-%define rtems_version 5
-
-#
-# The RTEMS URL paths.
-#
-%include rtems-urls.bset
-
 #
 # The RTEMS Package defines
 #
 %include rtems-package.bset
 
-
 #
 # Build EPICS.
 #
-epics/epics-7-1 .
\ No newline at end of file
+epics/epics-7.0-1
diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7.0-1.cfg
similarity index 64%
rename from source-builder/config/epics-7-1.cfg
rename to source-builder/config/epics-7.0-1.cfg
index 2a52ea5..2a06008 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7.0-1.cfg
@@ -27,7 +27,7 @@ URL:https://epics.mpg.de/
 %prep
   build_top=$(pwd)
 
-  source_dir_epics="epics-base-%{epics_version}"
+ # source_dir_epics="epics-base-%{epics_version}"
 
   %source setup epics-base -q -n epics-base-%{epics_version}
 
@@ -36,22 +36,30 @@ URL:  https://epics.mpg.de/
 %build
   build_top=$(pwd)
 
-  cd ${source_dir_epics}
+  cd epics-base-%{epics_version}
 
   %{build_build_flags}
 
   #
-  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using 
--with-rtems-bsp
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
+  # --with-rtems-bsp
   #
-  %{__make} RTEMS_BASE=%{_prefix} RTEMS_VERSION=%{rtems_version} 
CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+  %{__make} RTEMS_BASE=%{_prefix} \
+   RTEMS_VERSION=%{rtems_version} \
+   CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
 
   cd ${build_top}
 
-%install
+#%install
   build_top=$(pwd)
 
-  rm -rf $SB_BUILD_ROOT
+  %{__rmdir} $SB_BUILD_ROOT
+
+  cd epics-base-%{epics_version}
+
+  %{__make} DESTDIR=$SB_BUILD_ROOT \
+  RTEMS_BASE=%{_prefix} \
+  RTEMS_VERSION=%{rtems_version} \
+  CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp} install
 
-  cd ${source_dir_epics}
-  %{__make} DESTDIR=$SB_BUILD_ROOT RTEMS_BASE=%{_prefix} 
RTEMS_VERSION=%{rtems_version} 
CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
   cd ${build_top}
-- 
2.25.1

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

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

On Thu, Aug 27, 2020 at 3:04 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Thank you so much for taking time to review the PATCH.
>
> On Wed, Aug 26, 2020 at 8:56 PM Gedare Bloom  wrote:
>
>> On Tue, Aug 25, 2020 at 4:36 PM Mritunjay Sharma
>>  wrote:
>> >
>> > This patch add supports for EPICS7 Package to RTEMS RSB.
>> > Signed-off-by: Mritunjay Sharma 
>> > ---
>> >  rtems/config/epics/epics-7-1.cfg| 22 +++
>> >  rtems/config/epics/epics-base.bset  | 26 +
>> >  source-builder/config/epics-7-1.cfg | 57 +
>> >  3 files changed, 105 insertions(+)
>> >  create mode 100644 rtems/config/epics/epics-7-1.cfg
>> >  create mode 100644 rtems/config/epics/epics-base.bset
>> >  create mode 100644 source-builder/config/epics-7-1.cfg
>> >
>> > diff --git a/rtems/config/epics/epics-7-1.cfg
>> b/rtems/config/epics/epics-7-1.cfg
>> > new file mode 100644
>> > index 000..30ed9cb
>> > --- /dev/null
>> > +++ b/rtems/config/epics/epics-7-1.cfg
>>
>> should this file be epics-7.0-1.cfg?
>>
>> Yes, thanks for highlighting it. Fixed this.
>
>
>> > @@ -0,0 +1,22 @@
>> > +#
>> > +# EPICS 7
>> EPICS 7.0?
>>
>> > +#
>> > +
>> > +%if %{release} == %{nil}
>> > + %define release 1
>> > +%endif
>> > +
>> > +%include %{_configdir}/rtems-bsp.cfg
>> > +
>> > +#
>> > +# EPICS Version
>> > +#
>> > +%define epics_version 7.0
>> > +
>> > +%hash sha512 epics-base-%{epics_version}.tar.gz
>> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
>> > +
>> > +#
>> > +#
>> Only one blank comment line.
>>
>> Fixed.
>
>
>> > +# EPICS Build configuration
>> > +#
>> > +%include %{_configdir}/epics-7-1.cfg
>> > diff --git a/rtems/config/epics/epics-base.bset
>> b/rtems/config/epics/epics-base.bset
>> > new file mode 100644
>> > index 000..e56fc6a
>> > --- /dev/null
>> > +++ b/rtems/config/epics/epics-base.bset
>> > @@ -0,0 +1,26 @@
>> > +#
>> > +# Build set for EPICS
>> > +#
>> > +
>> > +%define release 1
>> > +
>> > +#
>> > +# RTEMS Version
>> > +#
>> > +%define rtems_version 5
>>
>> is this correct?
>>
>> Do you want to apply this to the 5 branch of rsb?
>>
>> I have removed this line.
>
>
>> > +
>> > +#
>> > +# The RTEMS URL paths.
>> > +#
>> > +%include rtems-urls.bset
>> > +
>> > +#
>> > +# The RTEMS Package defines
>> > +#
>> > +%include rtems-package.bset
>> > +
>> > +
>> 1 blank line only
>>
>
> Fixed.
>
>
>>
>> > +#
>> > +# Build EPICS.
>> > +#
>> > +epics/epics-7-1 .
>> Stray . ?
>>
>
> If I was not using '.' and I was simply using, the build failed, in the
> beginning, itself with the following error:
> `Build Set: epics/epics-base
> error: epics/epics-base:15: cannot find file: epics/epics-7.0-1.cf `
>

[UPDATE]: Removed the '.' The above error was due to missing space after
line 15. On adding space, it was resolved.

>
> The command I am entering is: `/source-builder/sb-set-builder
> --with-rtems-bsp="xilinx_zynq_a9_qemu" --log=log_epics epics/epics-base
>  --trace --prefix=$HOME/development/rtems/5-arm --host=arm-rtems5`
>
>>
>> > \ No newline at end of file
>> > diff --git a/source-builder/config/epics-7-1.cfg
>> b/source-builder/config/epics-7-1.cfg
>> > new file mode 100644
>> > index 000..2a52ea5
>> > --- /dev/null
>> > +++ b/source-builder/config/epics-7-1.cfg
>> > @@ -0,0 +1,57 @@
>> > +#
>> > +# EPICS 7.x.x Version 1.
>> > +#
>> > +# This configuration file configure's, make's and install's EPICS.
>> > +#
>> > +
>> > +%if %{release} == %{nil}
>> > +%define release 1
>> > +%endif
>> > +
>> > +%define epics_version 7.0
>> > +
>> > +Name:  epics-base-%{epics_version}-%{_host}-%{release}
>> > +Summary:   EPICS v%{epics_version} for target %{_target} on host
>> %{_host}
>> > +Version:   %{epics_version}
>> > +Release:   %{release}
>> > +URL

Re: [PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

Thank you so much for taking time to review the PATCH.

On Wed, Aug 26, 2020 at 8:56 PM Gedare Bloom  wrote:

> On Tue, Aug 25, 2020 at 4:36 PM Mritunjay Sharma
>  wrote:
> >
> > This patch add supports for EPICS7 Package to RTEMS RSB.
> > Signed-off-by: Mritunjay Sharma 
> > ---
> >  rtems/config/epics/epics-7-1.cfg| 22 +++
> >  rtems/config/epics/epics-base.bset  | 26 +
> >  source-builder/config/epics-7-1.cfg | 57 +
> >  3 files changed, 105 insertions(+)
> >  create mode 100644 rtems/config/epics/epics-7-1.cfg
> >  create mode 100644 rtems/config/epics/epics-base.bset
> >  create mode 100644 source-builder/config/epics-7-1.cfg
> >
> > diff --git a/rtems/config/epics/epics-7-1.cfg
> b/rtems/config/epics/epics-7-1.cfg
> > new file mode 100644
> > index 000..30ed9cb
> > --- /dev/null
> > +++ b/rtems/config/epics/epics-7-1.cfg
>
> should this file be epics-7.0-1.cfg?
>
> Yes, thanks for highlighting it. Fixed this.


> > @@ -0,0 +1,22 @@
> > +#
> > +# EPICS 7
> EPICS 7.0?
>
> > +#
> > +
> > +%if %{release} == %{nil}
> > + %define release 1
> > +%endif
> > +
> > +%include %{_configdir}/rtems-bsp.cfg
> > +
> > +#
> > +# EPICS Version
> > +#
> > +%define epics_version 7.0
> > +
> > +%hash sha512 epics-base-%{epics_version}.tar.gz
> 63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
> > +
> > +#
> > +#
> Only one blank comment line.
>
> Fixed.


> > +# EPICS Build configuration
> > +#
> > +%include %{_configdir}/epics-7-1.cfg
> > diff --git a/rtems/config/epics/epics-base.bset
> b/rtems/config/epics/epics-base.bset
> > new file mode 100644
> > index 000..e56fc6a
> > --- /dev/null
> > +++ b/rtems/config/epics/epics-base.bset
> > @@ -0,0 +1,26 @@
> > +#
> > +# Build set for EPICS
> > +#
> > +
> > +%define release 1
> > +
> > +#
> > +# RTEMS Version
> > +#
> > +%define rtems_version 5
>
> is this correct?
>
> Do you want to apply this to the 5 branch of rsb?
>
> I have removed this line.


> > +
> > +#
> > +# The RTEMS URL paths.
> > +#
> > +%include rtems-urls.bset
> > +
> > +#
> > +# The RTEMS Package defines
> > +#
> > +%include rtems-package.bset
> > +
> > +
> 1 blank line only
>

Fixed.


>
> > +#
> > +# Build EPICS.
> > +#
> > +epics/epics-7-1 .
> Stray . ?
>

If I was not using '.' and I was simply using, the build failed, in the
beginning, itself with the following error:
`Build Set: epics/epics-base
error: epics/epics-base:15: cannot find file: epics/epics-7.0-1.cf `

The command I am entering is: `/source-builder/sb-set-builder
--with-rtems-bsp="xilinx_zynq_a9_qemu" --log=log_epics epics/epics-base
 --trace --prefix=$HOME/development/rtems/5-arm --host=arm-rtems5`

>
> > \ No newline at end of file
> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> > new file mode 100644
> > index 000..2a52ea5
> > --- /dev/null
> > +++ b/source-builder/config/epics-7-1.cfg
> > @@ -0,0 +1,57 @@
> > +#
> > +# EPICS 7.x.x Version 1.
> > +#
> > +# This configuration file configure's, make's and install's EPICS.
> > +#
> > +
> > +%if %{release} == %{nil}
> > +%define release 1
> > +%endif
> > +
> > +%define epics_version 7.0
> > +
> > +Name:  epics-base-%{epics_version}-%{_host}-%{release}
> > +Summary:   EPICS v%{epics_version} for target %{_target} on host
> %{_host}
> > +Version:   %{epics_version}
> > +Release:   %{release}
> > +URL: https://epics.mpg.de/
> This doesn't look like the right url.
>

I cross-checked and it seems to be working.

>
> > +
> > +#
> > +# Source
> > +#
> > +%source set epics-base
> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
> ditto
>
> where do official EPICS releases go?
>

I think we need Heinz intervention in this and I am ready to help him get
it done.
We have to use this repo for the time being.

>
> > +
> > +#
> > +# Prepare the source code.
> > +#
> > +%prep
> > +  build_top=$(pwd)
> > +
> > +  source_dir_epics="epics-base-%{epics_version}"
> > +
> > +  %source setup epics-base -q -n epics-base-%{epics_version}
> I&#

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

On Wed, Aug 26, 2020 at 6:01 AM Chris Johns  wrote:

> On 26/8/20 8:48 am, Mritunjay Sharma wrote:
> > First of all, Apologies for the little delay in response. I was actually
> a
> > little stuck with assignments in classes.
>
> Thanks for letting us know. You will need to make up the lost time somehow.


Yes, I will make surely make sure of it.

> There's one problem although,  while building using:
> > `./source-builder/sb-set-builder --with-rtems-bsp="xilinx_zynq_a9_qemu"
> > --log=log_epics epics/epics-base  --trace
> --prefix=$HOME/development/rtems/5-arm
> > --host=arm-rtems5
> > `
> > The EPICS is building perfectly fine but the Buildset fails with the
> following
> > error:
> >
> > `cleaning: epics-base-7.0-arm-rtems5-1
> > error: copying tree (4):
> >
>
> /home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000
> > ->
> >
>
> /home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/sb-1000/epics/epics-base:
> > [Errno 2] No such file or directory:
> >
>
> '/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000'
> > Build Set: Time 0:02:57.099708
> > Build FAILED
> > `
> > I am not sure what it is and it was not encountered earlier?
> >
>
> You need to take a look at the log and the directories left after the
> build in
> the build tree. The names used need to match up or the RSB will not be
> able to
> find the installed tree to copy to the prefix.
>
> Note, most packages support the `DESTDIR=` make option to `make install` to
> control installing to a location that is not the specified prefix. The RSB
> does
> this to stage packages that form part of a vertical stack.
>

Hi Chris,

I tried to debug this with the help of trace file and what you suggested
above. I still haven't been successful in it.
With RSB 5 branch when sb-builder was available, the EPICS build was
running successfully using RSB recipe. However, in the RSB master,
sb-builder is no longer available and I used sb-set-builder to build EPICS.
I used this command:

`../source-builder/sb-set-builder --with-rtems-bsp="xilinx_zynq_a9_qemu"
--log=log_epics epics/epics-base  --trace
--prefix=$HOME/development/rtems/5-arm
--with-tools=$HOME/development/rtems/5-arm --host=arm-rtems5
`

This gave me the following error again and again
cleaning: epics-base-7.0-arm-rtems5-1
error: copying tree (4):
/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000
->
/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/sb-1000/epics/epics-base:
[Errno 2] No such file or directory:
'/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000'
Build Set: Time 0:02:52.146050
Build FAILED
`
For your reference, Below is the last part of the log file. Please see if
you can help me out and tell me if you want me to share any other details

`cleaning: epics-base-7.0-arm-rtems5-1
run: /bin/sh -ex
 
/home/mritunjay/development/rtems/src/rsb/rtems/build/epics-base-7.0-arm-rtems5-1/do-clean
exe: shell: /bin/sh -ex
 
/home/mritunjay/development/rtems/src/rsb/rtems/build/epics-base-7.0-arm-rtems5-1/do-clean
exe: /bin/sh -ex
 
/home/mritunjay/development/rtems/src/rsb/rtems/build/epics-base-7.0-arm-rtems5-1/do-clean
+ export
SB_ORIG_PATH=/home/mritunjay/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
+ SB_PREFIX=/home/mritunjay/development/rtems/5-arm
+ echo /home/mritunjay/development/rtems/5-arm
+ /bin/sed -e s/^\///
+ SB_PREFIX_CLEAN=home/mritunjay/development/rtems/5-arm
+ SB_SOURCE_DIR=/home/mritunjay/development/rtems/src/rsb/rtems/sources
+
SB_BUILD_DIR=/home/mritunjay/development/rtems/src/rsb/rtems/build/epics-base-7.0-arm-rtems5-1
+
SB_HOST_CPPFLAGS=-I/home/mritunjay/development/rtems/5-arm/arm-rtems5/xilinx_zynq_a9_qemu/lib/include
+ SB_HOST_CFLAGS=-qrtems
-B/home/mritunjay/development/rtems/5-arm/arm-rtems5/lib/
-B/home/mritunjay/development/rtems/5-arm/arm-rtems5/xilinx_zynq_a9_qemu/lib/
--specs bsp_specs -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard
-mtune=cortex-a9 -O0 -g -ffunction-sections -fdata-sections
+ SB_HOST_CXXFLAGS=-qrtems
-B/home/mritunjay/development/rtems/5-arm/arm-rtems5/lib/
-B/home/mritunjay/development/rtems/5-arm/arm-rtems5/xilinx_zynq_a9_qemu/lib/
--specs bsp_specs -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard
-mtune=cortex-a9 -O0 -g -ffunction-sections -fdata-sections
+ echo -qrtems -B/home/mritunjay/development/rtems/5-arm/arm-rtems5/lib/
-B/home/mritunjay/development/rtems/5-arm/arm-rtems5/xilinx_zynq_a9_qemu/lib/
--specs bsp_specs -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard
-mtune=cortex-a9 -O0 -g -ffunction-sections -fdata-sections
+ awk {for (i=1;i epics-ba

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

Hello, everyone!

First of all, Apologies for the little delay in response. I was actually a
little stuck with assignments in classes.

Thank you so much, Chris, for such a nice explanation and detailed review.
It cleared a lot of things even for me.
I have tried to respond to further suggestions and feedback below.

On Mon, Aug 24, 2020 at 6:25 AM Chris Johns  wrote:

> On 23/8/20 8:08 am, Mritunjay Sharma wrote:
> > [Good news and Update]:
> >
> > Thank you so much Chris! Your advice to search for macros using --trace
> solved
> > the problem of hard coding!
> > It took two complete days to figure out this beautiful thing but it is
> every
> > worth it.
>
> Well done, that looks like time worth spending given the results. The
> --trace is
> not the most pleasant of output but it has all the detail.
>

Thanks a lot :)


>
> > Now the user has to just enter the below command and it will make things
> work:
> >
> > `../source-builder/sb-builder --with-rtems-bsp="xilinx_zynq_a9_qemu"
> > --log=log_epics epics-7-1  --trace
> --prefix=$HOME/development/rtems/5-arm`
> >
> > Note: prefix will depend on the user.
> >
> > What made this possible? Your suggestion and the changes in code
> mentioned below:
> >
> > ```diff --git a/rtems/config/epics/epics-7-1.cfg
> b/rtems/config/epics/epics-7-1.cfg
> > index aeb39a9..4b20f82 100644
> > --- a/rtems/config/epics/epics-7-1.cfg
> > +++ b/rtems/config/epics/epics-7-1.cfg
> > @@ -6,6 +6,8 @@
> >   %define release 1
> >  %endif
> >
> > +%include %{_configdir}/rtems-bsp.cfg
>
> Great.
>

Thanks.


>
> > +
> >  #
> >  # EPICS Version
> >  #
> > diff --git a/source-builder/config/epics-7-1.cfg
> > b/source-builder/config/epics-7-1.cfg
> > index a9581a2..a47aecb 100644
> > --- a/source-builder/config/epics-7-1.cfg
> > +++ b/source-builder/config/epics-7-1.cfg
> > @@ -40,7 +40,10 @@ URL:  https://epics.mpg.de/
> >
> >%{build_build_flags}
> >
> > -  %{__make} PREFIX=%{_prefix} RTEMS_BASE=$HOME/development/rtems/5-arm
> > RTEMS_VERSION=5 CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
> > +  #
> > +  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION
> using
> > --with-rtems-bsp
> > +  #
> > +  %{__make} PREFIX=%{_prefix} RTEMS_BASE=%{_exec_prefix}
> > RTEMS_VERSION=%{rtems_version}
> >
> >cd ${build_top}
> >
> > @@ -50,6 +53,5 @@ URL:  https://epics.mpg.de/
> >rm -rf $SB_BUILD_ROOT
> >
> >cd ${source_dir_epics}
> > -  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
> > RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
> > CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
> > -
> > +  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
> RTEMS_BASE=%{_exec_prefix}
> > RTEMS_VERSION=%{rtems_version}
>
> Nice, this is along the lines of what I had hope at the start was possible.
>
> >cd ${build_top}
> > ```
> >
> > These couple of changes made this build successful using RSB recipe. The
> only
> > problem remains
> > is that a warning of 'no hash found' is coming, even though I have added
> it.
>
> The config hash is for epics-%{epics_version}.tar.gz and %source is using
> --rsb-file=epics-base-%{epics_version}.tar.gz. The names do not match. Is
> --rsb-file needed? This is only added if the download file is some
> generated
> name and not what we expect.
>
> > The above changes can be found pushed
> > here:
> https://github.com/RTEMS/rtems-source-builder/commit/a505877157f63f6ae17906276b3ffcb699ed1297
>
> Can you please create a suitable patch against the RSB master repo?
>

Done. I have just sent, please do review.
Modified the patch to remove warning and made a change to ask for rtems-bsp
and host from the terminal.
There's one problem although,  while building using:
`./source-builder/sb-set-builder --with-rtems-bsp="xilinx_zynq_a9_qemu"
--log=log_epics epics/epics-base  --trace
--prefix=$HOME/development/rtems/5-arm --host=arm-rtems5
`
The EPICS is building perfectly fine but the Buildset fails with the
following error:

`cleaning: epics-base-7.0-arm-rtems5-1
error: copying tree (4):
/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000
->
/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/sb-1000/epics/epics-base:
[Errno 2] No such file or directory:
'/home/mritunjay/development/rtems/src/rsb/rtems/build/tmp/epics-base-7.0-arm-rtems5-1-1000'
Build Set: Time 0:02:57.099708
Build FAILED
`
I am not sure what it is and it was not encountered e

[PATCH] Adding EPICS7 Package to RSB

[Mritunjay Sharma]

This patch add supports for EPICS7 Package to RTEMS RSB.
Signed-off-by: Mritunjay Sharma 
---
 rtems/config/epics/epics-7-1.cfg| 22 +++
 rtems/config/epics/epics-base.bset  | 26 +
 source-builder/config/epics-7-1.cfg | 57 +
 3 files changed, 105 insertions(+)
 create mode 100644 rtems/config/epics/epics-7-1.cfg
 create mode 100644 rtems/config/epics/epics-base.bset
 create mode 100644 source-builder/config/epics-7-1.cfg

diff --git a/rtems/config/epics/epics-7-1.cfg b/rtems/config/epics/epics-7-1.cfg
new file mode 100644
index 000..30ed9cb
--- /dev/null
+++ b/rtems/config/epics/epics-7-1.cfg
@@ -0,0 +1,22 @@
+#
+# EPICS 7
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 7.0
+
+%hash sha512 epics-base-%{epics_version}.tar.gz 
63edef9d3019e8253b81610286578a1e917cc9df75db3e8f5aaf99210b4fa842be296cf7cbd384726b81b648c4e0d041c4ef266ae81a580940d7613ce8ce48e0
+
+#
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
new file mode 100644
index 000..e56fc6a
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,26 @@
+#
+# Build set for EPICS
+#
+
+%define release 1
+
+#
+# RTEMS Version
+#
+%define rtems_version 5
+
+#
+# The RTEMS URL paths.
+#
+%include rtems-urls.bset
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+
+#
+# Build EPICS.
+#
+epics/epics-7-1 .
\ No newline at end of file
diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7-1.cfg
new file mode 100644
index 000..2a52ea5
--- /dev/null
+++ b/source-builder/config/epics-7-1.cfg
@@ -0,0 +1,57 @@
+#
+# EPICS 7.x.x Version 1.
+#
+# This configuration file configure's, make's and install's EPICS.
+#
+
+%if %{release} == %{nil}
+%define release 1
+%endif
+
+%define epics_version 7.0
+
+Name:  epics-base-%{epics_version}-%{_host}-%{release}
+Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
+Version:   %{epics_version}
+Release:   %{release}
+URL: https://epics.mpg.de/
+
+#
+# Source
+#
+%source set epics-base 
https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
+
+#
+# Prepare the source code.
+#
+%prep
+  build_top=$(pwd)
+
+  source_dir_epics="epics-base-%{epics_version}"
+
+  %source setup epics-base -q -n epics-base-%{epics_version}
+
+  cd ${build_top}
+
+%build
+  build_top=$(pwd)
+
+  cd ${source_dir_epics}
+
+  %{build_build_flags}
+
+  #
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using 
--with-rtems-bsp
+  #
+  %{__make} RTEMS_BASE=%{_prefix} RTEMS_VERSION=%{rtems_version} 
CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+
+  cd ${build_top}
+
+%install
+  build_top=$(pwd)
+
+  rm -rf $SB_BUILD_ROOT
+
+  cd ${source_dir_epics}
+  %{__make} DESTDIR=$SB_BUILD_ROOT RTEMS_BASE=%{_prefix} 
RTEMS_VERSION=%{rtems_version} 
CROSS_COMPILER_TARGET_ARCHS=RTEMS-%{with_rtems_bsp}
+  cd ${build_top}
-- 
2.25.1

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

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

[Good news and Update]:

Thank you so much Chris! Your advice to search for macros using --trace
solved the problem of hard coding!
It took two complete days to figure out this beautiful thing but it is
every worth it.

Now the user has to just enter the below command and it will make things
work:

`../source-builder/sb-builder --with-rtems-bsp="xilinx_zynq_a9_qemu"
--log=log_epics epics-7-1  --trace --prefix=$HOME/development/rtems/5-arm`

Note: prefix will depend on the user.

What made this possible? Your suggestion and the changes in code mentioned
below:

```diff --git a/rtems/config/epics/epics-7-1.cfg
b/rtems/config/epics/epics-7-1.cfg
index aeb39a9..4b20f82 100644
--- a/rtems/config/epics/epics-7-1.cfg
+++ b/rtems/config/epics/epics-7-1.cfg
@@ -6,6 +6,8 @@
  %define release 1
 %endif

+%include %{_configdir}/rtems-bsp.cfg
+
 #
 # EPICS Version
 #
diff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg
index a9581a2..a47aecb 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -40,7 +40,10 @@ URL:  https://epics.mpg.de/

   %{build_build_flags}

-  %{__make} PREFIX=%{_prefix} RTEMS_BASE=$HOME/development/rtems/5-arm
RTEMS_VERSION=5 CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
+  #
+  # Using macros to dynamically path to RTEMS_BASE and RTEMS_VERSION using
--with-rtems-bsp
+  #
+  %{__make} PREFIX=%{_prefix} RTEMS_BASE=%{_exec_prefix}
RTEMS_VERSION=%{rtems_version}

   cd ${build_top}

@@ -50,6 +53,5 @@ URL:  https://epics.mpg.de/
   rm -rf $SB_BUILD_ROOT

   cd ${source_dir_epics}
-  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
-
+  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
RTEMS_BASE=%{_exec_prefix} RTEMS_VERSION=%{rtems_version}
   cd ${build_top}
```

These couple of changes made this build successful using RSB recipe. The
only problem remains
is that a warning of 'no hash found' is coming, even though I have added
it.

The above changes can be found pushed here:
https://github.com/RTEMS/rtems-source-builder/commit/a505877157f63f6ae17906276b3ffcb699ed1297

Please do give feedback and suggest improvements so that the recipe can
become mergeable.

Thanks
Mritunjay Sharma







On Thu, Aug 20, 2020 at 8:51 AM Chris Johns  wrote:

> On 20/8/20 8:09 am, Mritunjay Sharma wrote:
> > [UPDATE]: Finally modified the RSB recipes to make them work with make
> utility
> > and EPICS was built successfully.
>
> Great you have had some success but there is a lot more work before it is
> usable.
>
> > iff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> > index f51c6582..a9581a2e 100644
> > --- a/source-builder/config/epics-7-1.cfg
> > +++ b/source-builder/config/epics-7-1.cfg
> > @@ -21,7 +21,6 @@ URL:  https://epics.mpg.de/
> >  #
> >  %source set epics --rsb-file=epics-base-%{epics_version}.tar.gz
> https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz
> >
> > -
> >  #
> >  # Prepare the source code.
> >  #
> > @@ -31,20 +30,9 @@ URL: https://epics.mpg.de/
> >source_dir_epics="epics-base-%{epics_version}"
> >
> >%source setup epics -q -n epics-base-%{epics_version}
> > -#
> > -# Changing the RTEMS Version in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
> > -#
> > -sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
> configure/os/CONFIG_SITE.Common.RTEMS
> > -
> > -#
> > -# Changing the RTEMS Base in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
> > -#
> > -sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
> configure/os/CONFIG_SITE.Common.RTEMS
> >
> >cd ${build_top}
> >
> > -
> > -
> >  %build
> >build_top=$(pwd)
> >
> > @@ -52,7 +40,7 @@ sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems\/\$\
> >
> >%{build_build_flags}
> >
> > -  %{__make} PREFIX=%{_prefix}
> > +  %{__make} PREFIX=%{_prefix} RTEMS_BASE=$HOME/development/rtems/5-arm
> RTEMS_VERSION=5 CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
> >
> >cd ${build_top}
> >
> > @@ -62,6 +50,6 @@ sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems\/\$\
> >rm -rf $SB_BUILD_ROOT
> >
> >cd ${source_dir_epics}
> > -  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix} install
> > +  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
> RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
>

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

[UPDATE]: Finally modified the RSB recipes to make them work with make
utility and EPICS was built successfully.

iff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg
index f51c6582..a9581a2e 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -21,7 +21,6 @@ URL:https://epics.mpg.de/
 #
 %source set epics --rsb-file=epics-base-%{epics_version}.tar.gz
https://gitlab.fhi.mpg.de/junkes/epics-base/-/archive/%{epics_version}/epics-base-%{epics_version}.tar.gz

-
 #
 # Prepare the source code.
 #
@@ -31,20 +30,9 @@ URL:   https://epics.mpg.de/
   source_dir_epics="epics-base-%{epics_version}"

   %source setup epics -q -n epics-base-%{epics_version}
-#
-# Changing the RTEMS Version in
epics-base/configure/os/CONFIG_SITE.Common.RTEMS
-#
-sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
configure/os/CONFIG_SITE.Common.RTEMS
-
-#
-# Changing the RTEMS Base in epics-base/configure/os/CONFIG_SITE.Common.RTEMS
-#
-sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
configure/os/CONFIG_SITE.Common.RTEMS

   cd ${build_top}

-
-
 %build
   build_top=$(pwd)

@@ -52,7 +40,7 @@ sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems\/\$\

   %{build_build_flags}

-  %{__make} PREFIX=%{_prefix}
+  %{__make} PREFIX=%{_prefix}
RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu

   cd ${build_top}

@@ -62,6 +50,6 @@ sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems\/\$\
   rm -rf $SB_BUILD_ROOT

   cd ${source_dir_epics}
-  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix} install
+  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix}
RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu


Thanks

Mritunjay


On Wed, Aug 19, 2020 at 2:47 PM Heinz Junkes 
wrote:

> Hallo Mritunjay,
>
> this was an improvement in the EPICS configuration to include the
> tool/path definitions
> from the RTEMS BSP directory:
>
> configure/os/CONFIG.Common.RTEMS:
> ...
> #---
> # Pick up the RTEMS tool/path definitions from the RTEMS BSP directory.
> include $(RTEMS_BASE)/$(GNU_TARGET)/$(RTEMS_BSP)/Makefile.inc
> include $(RTEMS_CUSTOM)
> include $(CONFIG.CC)
>
> #---
> # RTEMS cross-development tools
> CC = $(RTEMS_TOOLS)/bin/$(CC_FOR_TARGET) $(GCCSPECS) -fasm
> CCC = $(RTEMS_TOOLS)/bin/$(CXX)
> CPP = $(RTEMS_TOOLS)/bin/$(CC_FOR_TARGET) -x c -E
> AR = $(RTEMS_TOOLS)/bin/$(AR_FOR_TARGET)
> LD = $(RTEMS_TOOLS)/bin/$(LD_FOR_TARGET) -r
> …
>
> The assumption was that Makefile.inc is present in every BSP.
> If it cannot be found in the pc-386 BSP, should the BSP be adapted?
>

I will have to look into it again tomorrow and then I will revert on it.

Thanks
Mritunjay

>
>
> Viele Grüße
> Heinz Junkes
> --
> Experience directly varies with equipment ruined.
>
>
>
> > On 19. Aug 2020, at 07:09, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >
> > Hi everyone,
> >
> > Before I begin my queries [ mainly regarding epics upstream], let me
> give a few updates.
> >
> > As per the suggestion of Gedare, I started building by hand the pc-386
> and xilinx_zynq_a9_qemu using
> > the terminal configured make command.
> >
> > What I did initially as an experiment is that, in
> configure/os/CONFIG_SITE.Common.RTEMS:
> >
> > I made
> > RTEMS_VERSION =
> > RTEMS_BASE =
> >
> > That is both were left blank.
> >
> > Similarly, I did it for configure/CONFIG_SITE:
> > CROSS_COMPILER_TARGET_ARCHS=
> >
> > After this, I started building EPICS for xilinx_zynq_a9_qemu from the
> 'epics-base' downloaded from this source of Heinz [
> https://gitlab.fhi.mpg.de/junkes/epics-base]
> >
> > The command I used was:
> >
> > ` make RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
> CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu`
> >
> > The Build was successful for xilinx_zynq_a9_qemu.
> >
> > However, if I used the same `epics-base` and tried to build it for
> pc-386 using the command:
> >
> > `make RTEMS_BASE=$HOME/development/rtems/5 RTEMS_VERSION=5
> BUILD_ARCHS=RTEMS-pc386`
> >
> > The Build failed and I got this error:
> >
> > `make -C ./configure install
> > make[1]: Entering directory
> '/home/mritunjay/development/EPICS/epics-base/configure'
> > make -C O.RTEMS-pc386 -f ../Makefile TOP=../.. \
> > T_A=RTEMS-pc386 inst

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

Hi everyone,

Before I begin my queries [ mainly regarding epics upstream], let me give a
few updates.

As per the suggestion of Gedare, I started building by hand the pc-386 and
xilinx_zynq_a9_qemu using
the terminal configured make command.

What I did initially as an experiment is that, in
configure/os/CONFIG_SITE.Common.RTEMS:

I made
RTEMS_VERSION =
RTEMS_BASE =

That is both were left blank.

Similarly, I did it for configure/CONFIG_SITE:
CROSS_COMPILER_TARGET_ARCHS=

After this, I started building EPICS for xilinx_zynq_a9_qemu from the
'epics-base' downloaded from this source of Heinz [
https://gitlab.fhi.mpg.de/junkes/epics-base]

The command I used was:

` make RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5
CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu`

The Build was successful for xilinx_zynq_a9_qemu.

However, if I used the same `epics-base` and tried to build it for pc-386
using the command:

`make RTEMS_BASE=$HOME/development/rtems/5 RTEMS_VERSION=5
BUILD_ARCHS=RTEMS-pc386`

The Build failed and I got this error:

`make -C ./configure install
make[1]: Entering directory
'/home/mritunjay/development/EPICS/epics-base/configure'
make -C O.RTEMS-pc386 -f ../Makefile TOP=../.. \
T_A=RTEMS-pc386 install
make[2]: Entering directory
'/home/mritunjay/development/EPICS/epics-base/configure/O.RTEMS-pc386'
../../configure/os/CONFIG.Common.RTEMS:36:
/home/mritunjay/development/rtems/5//pc386/Makefile.inc: No such file or
directory
make[2]: *** No rule to make target
'/home/mritunjay/development/rtems/5//pc386/Makefile.inc'.  Stop.
make[2]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/configure/O.RTEMS-pc386'
make[1]: *** [../configure/RULES_ARCHS:58: install.RTEMS-pc386] Error 2
make[1]: Leaving directory
'/home/mritunjay/development/EPICS/epics-base/configure'
make: *** [configure/RULES_DIRS:84: configure.install] Error 2
`
This made me try another `epics-base` of Heinz that he earlier suggested
which is:
https://github.com/hjunkes/epicsBaseOwnPlayground/tree/3afec267ab08568ea454789e562450b00feea5c0

Running the same `make RTEMS_BASE=$HOME/development/rtems/5 RTEMS_VERSION=5
BUILD_ARCHS=RTEMS-pc386`
the command worked here and EPICS for pc-386 was successfully built.

Therefore, we need to make changes in the epics code base so that we can
have one common epics-base which works for both.

This was the update. I am modifying the RSB recipes and soon will update
regarding the build related to it.

Now, I am commenting on the queries further below.


On Wed, Aug 19, 2020 at 9:45 AM Gedare Bloom  wrote:

> On Tue, Aug 18, 2020 at 7:13 PM Heinz Junkes 
> wrote:
> >
> > Hi Mritunjay,
> >
> > To define the architecture you can create a file “CONFIG_SITE.local” in
> “configure”.
> > Look at the comment at the end of the file "CONFIG_SITE":
> >
>
Do I have to just write `CROSS_COMPILER_TARGET_ARCHS=` in CONFIG_SITE.local
file?
Please if you can tell more about what changes it can bring for us?

> > "
> > ...
> > # Overrides for the settings above may appear in a CONFIG_SITE.local file
> > -include $(CONFIG)/CONFIG_SITE.local.
> > “
> >
>
> Can we generate/inject the file/variables directly from scripts?
>

I also have the same question.

Thanks
Mritunjay Sharma


>
> > Heinz
> >
> > > On 16. Aug 2020, at 12:16, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> > >
> > >
> > >
> > > On Sun, Aug 16, 2020 at 1:12 PM Chris Johns  wrote:
> > > On 16/8/20 8:29 am, Mritunjay Sharma wrote:
> > > > On Sun, Aug 16, 2020 at 12:15 AM Gedare Bloom  > > > <mailto:ged...@rtems.org>> wrote:
> > > >
> > > > Hi Mritunjay, Chris:
> > > >
> > > > For the RSB, since it is user-facing, we need to be sure to
> minimize
> > > > its dependencies on the user environment and platform. So this
> pycli
> > > > can only be used if it is distributed standard with Python 2 and
> > > > Python 3.
> > > >
> > > > Would someone be able to apply this patch and use it to build
> epics?
> > > > No, because (1) they won't have pycli available, and (2) they
> don't
> > > > have a path /home/mritunjay
> > > >
> > > >
> > > > I think what you are saying is absolutely right. It will be really a
> great help
> > > > if Chris can guide on what next can be done.
> > >
> > > See below.
> > >
> > > > As far as 'pycli' is concerned, I have made a couple of minor
> tweaks. Gave it a
> > > > better name 'sedpy' and made it public on Gi

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

On Sun, Aug 16, 2020 at 1:12 PM Chris Johns  wrote:

> On 16/8/20 8:29 am, Mritunjay Sharma wrote:
> > On Sun, Aug 16, 2020 at 12:15 AM Gedare Bloom  > <mailto:ged...@rtems.org>> wrote:
> >
> > Hi Mritunjay, Chris:
> >
> > For the RSB, since it is user-facing, we need to be sure to minimize
> > its dependencies on the user environment and platform. So this pycli
> > can only be used if it is distributed standard with Python 2 and
> > Python 3.
> >
> > Would someone be able to apply this patch and use it to build epics?
> > No, because (1) they won't have pycli available, and (2) they don't
> > have a path /home/mritunjay
> >
> >
> > I think what you are saying is absolutely right. It will be really a
> great help
> > if Chris can guide on what next can be done.
>
> See below.
>
> > As far as 'pycli' is concerned, I have made a couple of minor tweaks.
> Gave it a
> > better name 'sedpy' and made it public on GitHub.
> >
> > Please find the link to the
> > project here: https://github.com/mritunjaysharma394/sedpy
>
> Thanks but I currently do not see a need for this tool.
>
> > I will appreciate if mentors can have a look and try this and see if it
> in any
> > way can be modified
> > to be used with RSB or else we will go with what is suggested.
>
> Please put the RSB to one side. I will let you know when we can return to
> it.
>
> I believe patching config files in EPCIS from the RSB is fragile. EPICS
> should
> be free to change any of these files without needing to considering the
> effect
> it has on the RSB. Just because we can peek inside does not means we are
> free to
> exploit what we see.
>
> What happens if you define the needed variables on the make command line?
> For
> example:
>
>  gmake RTEMS_BASE=$HOME/development/rtems/5 RTEMS_VERSION=5.1-rc2
>
> These variables are just normal make ones and so they can be overridden
> from the
> command line.
>
> Please investigate this and see what happens?
>

Hi Chris,
I investigated and used:

 `make RTEMS_BASE=$HOME/development/rtems/5-arm RTEMS_VERSION=5`

This worked perfectly fine and the build was successful. Thank you so much
for telling this. It makes it so
easy. What can we do next? This surely removes the requirement of `sed` or
the tool I built to make command line changes.

Thanks
Mritunjay


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

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

On Sun, Aug 16, 2020 at 12:15 AM Gedare Bloom  wrote:

> Hi Mritunjay, Chris:
>
> For the RSB, since it is user-facing, we need to be sure to minimize
> its dependencies on the user environment and platform. So this pycli
> can only be used if it is distributed standard with Python 2 and
> Python 3.
>
> Would someone be able to apply this patch and use it to build epics?
> No, because (1) they won't have pycli available, and (2) they don't
> have a path /home/mritunjay
>

I think what you are saying is absolutely right. It will be really a great
help
if Chris can guide on what next can be done.

As far as 'pycli' is concerned, I have made a couple of minor tweaks. Gave
it a better name
'sedpy' and made it public on GitHub.

Please find the link to the project here:
https://github.com/mritunjaysharma394/sedpy

I will appreciate if mentors can have a look and try this and see if it in
any way can be modified
to be used with RSB or else we will go with what is suggested.

Thanks
Mritunjay

>
> If there is no standard way to do line editing out of the box in
> Python, we might need to write our own little helper function to do
> it. I think Chris should weigh in on this issue, and whether there is
> anything to consider mimicking that does some custom Python scripting
> in RSB.
>
> Gedare
>
> On Sat, Aug 15, 2020 at 8:18 AM Mritunjay Sharma
>  wrote:
> >
> >
> > On Sat, Aug 15, 2020 at 7:42 PM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >> [Update]: I have built a workable python cli package known as 'pycli'
> >> which works as an alternative for 'sed'.
> >>
> >> I made the following changes in the config file:
> >>
> >> diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> >> index f51c658..6408534 100644
> >> --- a/source-builder/config/epics-7-1.cfg
> >> +++ b/source-builder/config/epics-7-1.cfg
> >> @@ -34,12 +34,11 @@ URL:  https://epics.mpg.de/
> >>  #
> >>  # Changing the RTEMS Version in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
> >>  #
> >> -sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
> configure/os/CONFIG_SITE.Common.RTEMS
> >> +pycli 'RTEMS_VERSION = .*' 'RTEMS_VERSION = 5'
> configure/os/CONFIG_SITE.Common.RTEMS
> >>
> >>  #
> >>  # Changing the RTEMS Base in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
> >> -#
> >> -sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
> configure/os/CONFIG_SITE.Common.RTEMS
> >> +pycli '^RTEMS_BASE .*' 'RTEMS_BASE =
> /home/mritunjay/development/rtems/$(RTEMS_VERSION)-arm/'
> configure/os/CONFIG_SITE.Common.RTEMS
> >>
> >>cd ${build_top}
> >>
> >
> >
> > Kindly ignore this spike part, It was mistakenly sent.
> >
> >>
> >> diff --git a/source-builder/config/spike-1-1.cfg
> b/source-builder/config/spike-1-1.cfg
> >> index e731348..aff3f35 100644
> >> --- a/source-builder/config/spike-1-1.cfg
> >> +++ b/source-builder/config/spike-1-1.cfg
> >> @@ -3,7 +3,7 @@
> >>  #
> >>  # This configuration file configure's, make's and install's RISC-V's
> spike simulator.
> >>  #
> >> -
> >> +%define spike_version 01252686902fa30665fbecfc1476d169ad1333d1
> >>  %if %{release} == %{nil}
> >>  %define release 1
> >>  %endif
> >>
> >> This worked successfully and the build ran fine. I am going to upload
> the entire python pycli project on the github in a couple of hours.
> >>
> >> The main part of the python script that did the work is here:
> >>
> >> '''import re
> >>
> >> def replace(oldstring, newstring, infile, dryrun=False):
> >> '''
> >> Sed-like Replace
> >> Usage: pycli
> >> Example: pycli 'xyz' 'XYZ' '/path/to/file.txt'
> >> '''
> >> linelist = []
> >> with open(infile) as f:
> >> for item in f:
> >> newitem = re.sub(oldstring, newstring, item)
> >> linelist.append(newitem)
> >> if dryrun == False:
> >> with open(infile, "w") as f:
> >> f.truncate()
> >> for line in linelist: f.writelines(line)
> >> elif dryrun == True:

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

On Sat, Aug 15, 2020 at 7:42 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> [Update]: I have built a workable python cli package known as 'pycli'
> which works as an alternative for 'sed'.
>
> I made the following changes in the config file:
>
> diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> index f51c658..6408534 100644
> --- a/source-builder/config/epics-7-1.cfg
> +++ b/source-builder/config/epics-7-1.cfg
> @@ -34,12 +34,11 @@ URL:  https://epics.mpg.de/
>  #
>  # Changing the RTEMS Version in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
>  #
> -sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
> configure/os/CONFIG_SITE.Common.RTEMS
> +pycli 'RTEMS_VERSION = .*' 'RTEMS_VERSION = 5'
> configure/os/CONFIG_SITE.Common.RTEMS
>
>  #
>  # Changing the RTEMS Base in
> epics-base/configure/os/CONFIG_SITE.Common.RTEMS
> -#
> -sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
> configure/os/CONFIG_SITE.Common.RTEMS
> +pycli '^RTEMS_BASE .*' 'RTEMS_BASE =
> /home/mritunjay/development/rtems/$(RTEMS_VERSION)-arm/'
> configure/os/CONFIG_SITE.Common.RTEMS
>
>cd ${build_top}
>
>

Kindly ignore this spike part, It was mistakenly sent.


> diff --git a/source-builder/config/spike-1-1.cfg
> b/source-builder/config/spike-1-1.cfg
> index e731348..aff3f35 100644
> --- a/source-builder/config/spike-1-1.cfg
> +++ b/source-builder/config/spike-1-1.cfg
> @@ -3,7 +3,7 @@
>  #
>  # This configuration file configure's, make's and install's RISC-V's
> spike simulator.
>  #
> -
> +%define spike_version 01252686902fa30665fbecfc1476d169ad1333d1
>  %if %{release} == %{nil}
>  %define release 1
>  %endif
>
> This worked successfully and the build ran fine. I am going to upload the
> entire python pycli project on the github in a couple of hours.
>
> The main part of the python script that did the work is here:
>
> '''import re
>
> def replace(oldstring, newstring, infile, dryrun=False):
> '''
> Sed-like Replace
> Usage: pycli
> Example: pycli 'xyz' 'XYZ' '/path/to/file.txt'
> '''
> linelist = []
> with open(infile) as f:
> for item in f:
> newitem = re.sub(oldstring, newstring, item)
> linelist.append(newitem)
> if dryrun == False:
>     with open(infile, "w") as f:
>     f.truncate()
> for line in linelist: f.writelines(line)
> elif dryrun == True:
> for line in linelist: print(line, end='')
> else:
> exit("Unknown option specified to 'dryrun' argument, Usage:
> dryrun=.")'''
>
> Please do give the feedback if this has been done in the right way?
>
> Thanks
> Mritunjay Sharma
>
>
>
> On Fri, Aug 14, 2020 at 3:13 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> Based on the input received by Gedare, I have started working
>> on finding a 'sed' alternative to be used in the RSB recipes to
>> do streamline text replacements.
>>
>> I have gone through the Python Development Guidelines (
>> https://docs.rtems.org/branches/master/eng/python-devel.html)
>> and have installed the things suggested in this for the development
>> environment.
>>
>> To start with the research work, I found this interesting
>> the discussion here
>> https://unix.stackexchange.com/questions/13711/differences-between-sed-on-mac-osx-and-other-standard-sed
>>  that
>> gave me an idea
>> on how sed differs in BSD and UNIX platforms.
>>
>> I learnt about differences like:
>> `OS X's sed uses -E for ERE and GNU sed uses -r. -E is an alias for -r in
>> GNU sed (added in 4.2, not documented until 4.3). Newer versions of FreeBSD
>> and NetBSD sed support both -E and -r. OpenBSD sed only supports -E.
>> `
>>
>> I also found a similar project https://github.com/chmln/sd which can
>> help us in
>> developing the Python code needed in our case.
>>
>> I would request the mentors to guide me on how and where to begin from
>> in writing this alternative?
>> Where do I have to write it? Is it the rtems-tools project (
>> https://github.com/RTEMS/rtems-tools) where I have to contribute to for
>> building this alternative?
>>
>> Thanks
>> Mritunjay Sharma
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

[Update]: I have built a workable python cli package known as 'pycli'
which works as an alternative for 'sed'.

I made the following changes in the config file:

diff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg
index f51c658..6408534 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -34,12 +34,11 @@ URL:  https://epics.mpg.de/
 #
 # Changing the RTEMS Version in
epics-base/configure/os/CONFIG_SITE.Common.RTEMS
 #
-sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
configure/os/CONFIG_SITE.Common.RTEMS
+pycli 'RTEMS_VERSION = .*' 'RTEMS_VERSION = 5'
configure/os/CONFIG_SITE.Common.RTEMS

 #
 # Changing the RTEMS Base in
epics-base/configure/os/CONFIG_SITE.Common.RTEMS
-#
-sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
configure/os/CONFIG_SITE.Common.RTEMS
+pycli '^RTEMS_BASE .*' 'RTEMS_BASE =
/home/mritunjay/development/rtems/$(RTEMS_VERSION)-arm/'
configure/os/CONFIG_SITE.Common.RTEMS

   cd ${build_top}

diff --git a/source-builder/config/spike-1-1.cfg
b/source-builder/config/spike-1-1.cfg
index e731348..aff3f35 100644
--- a/source-builder/config/spike-1-1.cfg
+++ b/source-builder/config/spike-1-1.cfg
@@ -3,7 +3,7 @@
 #
 # This configuration file configure's, make's and install's RISC-V's spike
simulator.
 #
-
+%define spike_version 01252686902fa30665fbecfc1476d169ad1333d1
 %if %{release} == %{nil}
 %define release 1
 %endif

This worked successfully and the build ran fine. I am going to upload the
entire python pycli project on the github in a couple of hours.

The main part of the python script that did the work is here:

'''import re

def replace(oldstring, newstring, infile, dryrun=False):
'''
Sed-like Replace
Usage: pycli
Example: pycli 'xyz' 'XYZ' '/path/to/file.txt'
'''
linelist = []
with open(infile) as f:
for item in f:
newitem = re.sub(oldstring, newstring, item)
linelist.append(newitem)
if dryrun == False:
with open(infile, "w") as f:
f.truncate()
for line in linelist: f.writelines(line)
elif dryrun == True:
for line in linelist: print(line, end='')
else:
exit("Unknown option specified to 'dryrun' argument, Usage:
dryrun=.")'''

Please do give the feedback if this has been done in the right way?

Thanks
Mritunjay Sharma



On Fri, Aug 14, 2020 at 3:13 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Hello everyone,
>
> Based on the input received by Gedare, I have started working
> on finding a 'sed' alternative to be used in the RSB recipes to
> do streamline text replacements.
>
> I have gone through the Python Development Guidelines (
> https://docs.rtems.org/branches/master/eng/python-devel.html)
> and have installed the things suggested in this for the development
> environment.
>
> To start with the research work, I found this interesting
> the discussion here
> https://unix.stackexchange.com/questions/13711/differences-between-sed-on-mac-osx-and-other-standard-sed
>  that
> gave me an idea
> on how sed differs in BSD and UNIX platforms.
>
> I learnt about differences like:
> `OS X's sed uses -E for ERE and GNU sed uses -r. -E is an alias for -r in
> GNU sed (added in 4.2, not documented until 4.3). Newer versions of FreeBSD
> and NetBSD sed support both -E and -r. OpenBSD sed only supports -E.
> `
>
> I also found a similar project https://github.com/chmln/sd which can help
> us in
> developing the Python code needed in our case.
>
> I would request the mentors to guide me on how and where to begin from
> in writing this alternative?
> Where do I have to write it? Is it the rtems-tools project (
> https://github.com/RTEMS/rtems-tools) where I have to contribute to for
> building this alternative?
>
> Thanks
> Mritunjay Sharma
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

[Mritunjay Sharma]

Hello everyone,

Based on the input received by Gedare, I have started working
on finding a 'sed' alternative to be used in the RSB recipes to
do streamline text replacements.

I have gone through the Python Development Guidelines (
https://docs.rtems.org/branches/master/eng/python-devel.html)
and have installed the things suggested in this for the development
environment.

To start with the research work, I found this interesting
the discussion here
https://unix.stackexchange.com/questions/13711/differences-between-sed-on-mac-osx-and-other-standard-sed
that
gave me an idea
on how sed differs in BSD and UNIX platforms.

I learnt about differences like:
`OS X's sed uses -E for ERE and GNU sed uses -r. -E is an alias for -r in
GNU sed (added in 4.2, not documented until 4.3). Newer versions of FreeBSD
and NetBSD sed support both -E and -r. OpenBSD sed only supports -E.
`

I also found a similar project https://github.com/chmln/sd which can help
us in
developing the Python code needed in our case.

I would request the mentors to guide me on how and where to begin from
in writing this alternative?
Where do I have to write it? Is it the rtems-tools project (
https://github.com/RTEMS/rtems-tools) where I have to contribute to for
building this alternative?

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

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

[Mritunjay Sharma]

Thank you so much Heinz and Gedare for the suggestion of using sed instead
of patches.

The good news is that I worked with them and EPICS 7 was built successfully
for "xilinx_zynq_a9_qemu" using RSB recipe.

The changes I made were  as follows:

```diff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg

index 2398cacf..f51c6582 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -31,10 +31,20 @@ URL:  https://epics.mpg.de/
   source_dir_epics="epics-base-%{epics_version}"

   %source setup epics -q -n epics-base-%{epics_version}
-  %patch setup epics -p1
+#
+# Changing the RTEMS Version in
epics-base/configure/os/CONFIG_SITE.Common.RTEMS
+#
+sed -i 's/RTEMS_VERSION = .*/RTEMS_VERSION = 5/g'
configure/os/CONFIG_SITE.Common.RTEMS
+
+#
+# Changing the RTEMS Base in epics-base/configure/os/CONFIG_SITE.Common.RTEMS
+#
+sed -i "s/^RTEMS_BASE .*/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems\/\$\(RTEMS_VERSION\)\-arm/g"
configure/os/CONFIG_SITE.Common.RTEMS

   cd ${build_top}

+
+
 %build
   build_top=$(pwd)
 ```

The changes can be observed from here as well:
https://github.com/RTEMS/rtems-source-builder/commit/1e7d7d4237a479dce564711b1080a9b3225e9e9a

One issue that remains is that even after adding sha512 has for
epics-base-7.0.tar.gz, I am getting "no hash found"  warning.
However, the build is running successfully.

Now that it is seen that sed can be used, the next step, in my opinion, is
to develop a logic for making these changes use-oriented as even now,
I have to specify my directory in the scripts, the only difference is that
I am using sed instead of patch.

Thank you again, Heinz and Gedare for introducing me to sed and making me
revise some regex as well!

Thanks
Mritunjay Sharma


On Wed, Aug 12, 2020 at 7:07 PM Gedare Bloom  wrote:

> On Wed, Aug 12, 2020 at 1:58 AM Heinz Junkes 
> wrote:
> >
> > I think you should not make a patch for these two changes but a
> > simple replacement with e.g. sed.
> >
> > like
> >
> > sed -i ’s/^RTEMS_BASE/RTEMS_BASE =
> \/home\/mritunjay\/development\/rtems/\$\(RTEMS_VERSION\)-arm\/g’
> configure/os/CONFIG_SITE.Common.RTEMS
> >
> > oder so ;-)
> >
>
> Yes, great, that was something I think I mentioned before--the patches
> are fine to get things hacked, but we should script the configuration
> if we can from RSB. A cross-platform python-based approach must be
> used.
>
> >
> > Viele Grüße
> > Heinz Junkes
> > --
> > Experience directly varies with equipment ruined.
> >
> >
> >
> > > On 12. Aug 2020, at 02:13, Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> > >
> > > Hello Heinz and everyone!
> > >
> > > Thank you so much for this update. I started to work first by building
> EPICS by hand
> > > for "xilinx_zynq_a9_qemu". Till the time, you gave
> https://gitlab.fhi.mpg.de/junkes/epics-base.git,
> > > I had to struggle with lot of errors which cloning into this repo
> solved.
> > >
> > > So I started by building "xilinx_zynq_a9_qemu" BSP for RTEMS5 using my
> own blog with only difference being
> > > that  I used '--disable-networking' to use libbsd.
> > >
> > > After that, I used this blog https://rmeena840.github.io/Fourth-Post/
> of a GSoC 19 Student to build and install rtems-libbsd
> > > for  "xilinx_zynq_a9_qemu".
> > >
> > > Everything worked perfectly fine till now. Now I entered the
> 'epics-base' directory and made
> > > the changes in configure/os/CONFIG_SITE.Common.RTEMS as:
> > >
> > > # FHI:
> > > RTEMS_SERIES = 5
> > > RTEMS_VERSION = 5
> > > RTEMS_BASE = /home/mritunjay/development/rtems/$(RTEMS_VERSION)-arm
> > >
> > > Also made the change in configure/CONFIG_SITE:
> > >
> > > CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu
> > >
> > > After this I used 'make' command and it worked fine.
> > >
> > > So, I can say that there were just two changes which I had to make
> then the previous one.
> > >
> > > The successful build by hand enabled me to work on the RSB recipe.
> > >
> > > I worked on them and it can be found here
> https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support-zynq
> .
> > >
> > > The patch I am applying can be found here:
> https://raw.githubusercontent.com/mritunjaysharma394/epics-mritunjay/master/patches/0001-Added-support-for-RTEMS-xilinx_zynq_a9_qemu.patch
> > >
> > > H

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

[Mritunjay Sharma]

On Sat, Aug 8, 2020 at 11:10 PM Gedare Bloom  wrote:

> On Sat, Aug 8, 2020 at 11:08 AM Mritunjay Sharma
>  wrote:
> >
> >
> >
> > On Sat, Aug 8, 2020 at 9:46 PM Heinz Junkes 
> wrote:
> >>
> >> Hallo Mritunjay,
> >> everything looks pretty good. I'm commenting on the text. I also send
> this mail
> >> to two EPICS experts (Andrew Johnson and Michael Davidsaver). Maybe
> they also have some ideas.
> >
> >
> > Thank you so much Heinz! It will be really a great help!
> >>
> >>
> >>
> >> >
> >> > Current Status:
> >> >
> >> > 1) Successfully built EPICS7 with RTEMS5 by hand for pc-386
> >> > 2) Worked for RSB recipe.
> >> >In its due process, I Wrote:
> >> > i) rsb/rtems/config/epics/epics-7-1.cfg
> >> > ii)rsb/rtems/config/epics/epics-base.bset
> >> > iii)rsb/source-builder/config/epics-7-1.cfg
> >> > 3) Added Patch for RTEMS-pc-386 support which made the above recipe
> work successfully.
> >> > 4) Therefore, Successully built EPICS7 with RTEMS5 by using RSB
> recipe as well for pc-386 as of now.
> >> > 5) Sent 4 Patches for review of the same.
> >> >
> >> > What problems are in the next steps?
> >> >
> >> > 1) How to make it work across different architectures?
> >> > 2) Exisiting EPICS works on the old legacy network stack.
> >> > 3) I am not using EPICS upstream branch. It is being built
> >> > by Heinz's epics playground.
> >> > 4) Doubts in how to start with testing.
> >> >
> >> > My Resarch work for the Problem no: 1
> >> >
> >> > I have gone through the EPICS developer guide from here
> >> > exhaustively in the past couple of day and here are few interesting
> things
> >> > that I found which can help:
> >> >
> >> > 1) "The main ingredients of the build system are:
> >> > • A set of configuration files and tools provided in the EPICS
> base/configure directory
> >> > • A corresponding set of configuration files in the /configure
> directory of a non-base  directory
> >> > structure to be built. The makeBaseApp.pl and makeBaseExt.pl scripts
> create these configuration files. Many of
> >> > these files just include a file of the same name from the
> base/configure directory.
> >> > • Makefiles in each directory of the  directory structure to be
> built
> >> > • User created configuration files in build created
> $(INSTALL_LOCATION)/cfg directories.
> >> > "
> >> >
> >> > Remarks: Now since it is also mentioned in the guide that
> "makeBaseApp.pl
> >> > creates directories and then copies template files into the newly
> created directories
> >> > while expanding macros in the template files. EPICS base provides two
> sets of template files: simple and example."
> >> > Can we think of using makeBaseApp.pl to that end? Making the user
> allow
> >> > to change the configurations from the terminal?
> >>
> >> I don't think that makeBaseApp.pl will help you. This is intended to
> build an example IOC. It takes the settings from the above mentioned
> configuration files.
> >>
> >> You "only" need to specify the location of the RTEMS installation in
> configure/os/CONFIG_SITE.Common.RTEMS.
> >> RTEMS_VERSION =
> >> RTEMS_BASE =
> >>
> >> Then you have to define the target in 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=
> >> …
> >> e.g. “CROSS_COMPILER_TARGET_ARCHS=RTEMS-xilinx_zynq_a9_qemu"
> >>
> >> And for each target there must be a file in configure/os:
> >> e.g. CONFIG_Common.RTEMS-xilinx_zynq_a9_qemu
> >> If it is not provided by EPICS, the RSB should install it there
> (adapted to the target to be used by epics make).
> >
>
> Probably they should be provided by EPICS for known-to-work
> configurations. If they are not, we should push upstream.
>
> >
> > Yes, Heinz. I followed the above steps and created a patch which I
> applied in the configuration files of RSB recipe.
> > The problem with it is that it's made only for pc-386 and I have to
> hardcode there about location of the RTEMS installation in
>

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

[Mritunjay Sharma]

ecture on which it is started.
>
> > Remarks: As EPICS_HOST_ARCH, can we do something similar for
> CROSS_COMPILER_TARGET_ARCHS?
> >
> > 3) ") The following is a summary of targets that can be specified for
> gnumake:
> > • 
> > • 
> > • .
> > • 
> > • .
> > • .
> > • ..
> > where:
> >  is an architecture such as solaris-sparc, vxWorks-68040,
> win32-x86, etc.
> >  is help, clean, realclean, distclean, inc, install, build,
> rebuild, buildInstall, realuninstall, or uninstall"
> >
> > Remarks: Now similar to the above stated, can we work for Cross Compiler
> target Architecture?
> >
>
> But this does not refer to 3) ?


No no, this remark is also for the problem 1 only as told above. Slight
misunderstanding here :)

>


> 3) You have to take "my" repo at the moment, because the adaptations to
> RTEMS5 are not yet included in the official epics-base. This is a
> hen-and-egg problem because RTEMS is only now in the release phase, so my
> changes have not been implemented yet.
>

Ok, I hope Dr. Gedare and Chris can help you with that.

>
> 2) I'm just about to figure out in the Epics Makefiles whether the target
> was built with the legacy-stack or libbsd-stack. It's working already.
> Now I also have to adjust the rtems_init.c accordingly. Here I have to
> clean up a little bit. But I hope to have this finished by the middle of
> the week.
>

Thank you so much for the update!

So I would like to ask my other mentors - what can I do for the time being?
What should be the next steps for this week?
And yes how to begin the testing part?
I have tried to find some resources but I think it will be
better if you can help somewhere to look at.

Thanks
Mritunjay Sharma

>
> > These were the little doubts that originated from the research work I
> did.
> > I will like the opinion of mentors that what can be the optimal way now
> to approach the
> > project after this? What can be some resources for better research work
> of the
> > above problems?
> >
> > Also, for the reference:
> > Link to the changes in commits of rsb can be found here:
> https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support
> >
> > The patch for epics can be found here:
> https://github.com/mritunjaysharma394/epics-mritunjay/tree/master/patches
> >
> >
> > Thanks
> > Mritunjay Sharma
> >
> >
> >
> >
> Heinz
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[GSoC 2020] : BSP Buildset for EPICS (next steps)

[Mritunjay Sharma]

First of all apologies for a little delayed
email. The classes have resumed just the
day after that 72 hours Hackathon and it became a lot hectic.

Finally, I am a little better synchronised now and hoping to
catch up pace. Before telling about my research work, let me
share with you about the past status.

Current Status:

1) Successfully built EPICS7 with RTEMS5 by hand for pc-386
2) Worked for RSB recipe.
   In its due process, I Wrote:
i) rsb/rtems/config/epics/epics-7-1.cfg
ii)rsb/rtems/config/epics/epics-base.bset
iii)rsb/source-builder/config/epics-7-1.cfg
3) Added Patch for RTEMS-pc-386 support which made the above recipe work
successfully.
4) Therefore, Successully built EPICS7 with RTEMS5 by using RSB recipe as
well for pc-386 as of now.
5) Sent 4 Patches for review of the same.

What problems are in the next steps?

1) How to make it work across different architectures?
2) Exisiting EPICS works on the old legacy network stack.
3) I am not using EPICS upstream branch. It is being built
by Heinz's epics playground.
4) Doubts in how to start with testing.

My Resarch work for the Problem no: 1

I have gone through the EPICS developer guide from here
exhaustively in the past couple of day and here are few interesting things
that I found which can help:

1) "The main ingredients of the build system are:
• A set of configuration files and tools provided in the EPICS
base/configure directory
• A corresponding set of configuration files in the /configure
directory of a non-base  directory
structure to be built. The makeBaseApp.pl and makeBaseExt.pl scripts create
these configuration files. Many of
these files just include a file of the same name from the base/configure
directory.
• Makefiles in each directory of the  directory structure to be built
• User created configuration files in build created $(INSTALL_LOCATION)/cfg
directories.
"

Remarks: Now since it is also mentioned in the guide that "makeBaseApp.pl
creates directories and then copies template files into the newly created
directories
while expanding macros in the template files. EPICS base provides two sets
of template files: simple and example."
Can we think of using makeBaseApp.pl to that end? Making the user allow
to change the configurations from the terminal?

2) "The startup directory in EPICS base contains a perl script,
EpicsHostArch.pl, which can be used to define
EPICS_HOST_ARCH. This script can be invoked with a command line parameter
defining the alternate compiler (e.g.
if invoking EpicsHostArch.pl yields solaris-sparc, then invoking
EpicsHostArch.pl gnu will yield
solaris-sparc-gnu).
The startup directory also contains scripts to help users set the path and
other environment variables"

Remarks: As EPICS_HOST_ARCH, can we do something similar
for CROSS_COMPILER_TARGET_ARCHS?

3) ") The following is a summary of targets that can be specified for
gnumake:
• 
• 
• .
• 
• .
• .
• ..
where:
 is an architecture such as solaris-sparc, vxWorks-68040, win32-x86,
etc.
 is help, clean, realclean, distclean, inc, install, build,
rebuild, buildInstall, realuninstall, or uninstall"

Remarks: Now similar to the above stated, can we work for Cross Compiler
target Architecture?

These were the little doubts that originated from the research work I did.
I will like the opinion of mentors that what can be the optimal way now to
approach the
project after this? What can be some resources for better research work of
the
above problems?

Also, for the reference:
Link to the changes in commits of rsb can be found here:
https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support

The patch for epics can be found here:
https://github.com/mritunjaysharma394/epics-mritunjay/tree/master/patches


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

Updates of Smart India Hackathon 2020 Finale

[Mritunjay Sharma]

Hello everyone!

I feel elated to share with the community that my Team 'Altruist'
won the first Prize in the Grand Finale of the World's
Biggest Hackathon - Smart India Hackathon 2020! We will not
only be awarded with INR 100,000 but also the Government of India
will help us to scale our project!

Thank you so much to the community for understanding my concern
and allowing me to take a break from 31st July to 3rd August.

I am resuming my work from today and will start a new thread
to ask the doubts after proper research work!

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

Re: [GSoC 2020: Offlist] Request to Pardon my unavailability from 31st July to 3rd of August,2020

[Mritunjay Sharma]

I think I mistakenly wrote offlist in the subject line.
Apologies
Mritunjay

On Fri, Jul 31, 2020 at 4:00 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Hello all!
>
> With great joy, I will like to share with you all that my team
> is a finalist in India's biggest and most prestigious - "Smart India
> Hackathon"
> 2020 and the Grand Finale of this Hackathon is being held in between
> August 1st - August 3rd which will be also graced by Honourable Prime
> Minister of India.
>
> Considering the nature and magnitude of the Hackathon and the
> amount of efforts our team has to put in to solve the challenge - I am
> very likely to be less
> active for the period between July 31st to August 3rd, 2020.
>
> I will resume the work here with all the more vigour from August 4th and
> I sincerely request you all to pardon me for the inactivity over the above
> mentioned
> period.
>
> With your best wishes, I hope that our team will learn and build something
> great
> in this Hackathon!
>
> Thanks
> Mritunjay
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[GSoC 2020: Offlist] Request to Pardon my unavailability from 31st July to 3rd of August,2020

[Mritunjay Sharma]

Hello all!

With great joy, I will like to share with you all that my team
is a finalist in India's biggest and most prestigious - "Smart India
Hackathon"
2020 and the Grand Finale of this Hackathon is being held in between
August 1st - August 3rd which will be also graced by Honourable Prime
Minister of India.

Considering the nature and magnitude of the Hackathon and the
amount of efforts our team has to put in to solve the challenge - I am very
likely to be less
active for the period between July 31st to August 3rd, 2020.

I will resume the work here with all the more vigour from August 4th and
I sincerely request you all to pardon me for the inactivity over the above
mentioned
period.

With your best wishes, I hope that our team will learn and build something
great
in this Hackathon!

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

[GSoC 2020]: Doubts related to testing for EPICS7+RTEMS5 (pc386) built using recipe.

[Mritunjay Sharma]

Hello all!

I tried to work on the testing part and here's what I did as per my
understanding:

I went inside the epics built by RSB recipe and ran "make runtests".
It gave results somewhat like this:

"Base.t  ok
Breaktable.t .. ok
DBD.t . ok
Device.t .. ok
Driver.t .. ok
Function.t  ok
Menu.t  ok
Recfield.t  ok
Recordtype.t .. ok
Registrar.t ... ok
Variable.t  ok
All tests successful.
Files=11, Tests=293,  1 wallclock secs ( 0.05 usr  0.00 sys +  0.40 cusr
 0.06 csys =  0.51 CPU)
Result: PASS"

I also downloaded rtems-testing directory and tried to run simulator
using the tutorial here:
https://devel.rtems.org/wiki/Developer/Simulators/QEMU

However, I was encountered with this error when I entered:
```./sim-scripts/pc386 -i
~/development/rtems/kernels-5/pc-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe```

Error: ```qemu-system-i386: Initialization of device ide-hd failed: Block
node is read-only```.

It is very much possible that I am following a wrong approach for testing.
I really look forward to you all to help me out with it and
also share some resources which can help me guide on what exactly I have
to proceed with ahead.

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

Re: [GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

[Mritunjay Sharma]

On Wed, Jul 29, 2020 at 10:02 AM Chris Johns  wrote:

> On 29/7/20 4:43 am, Mritunjay Sharma wrote:
> > First of all apologies for a little late response,
> > please find the link to the blogs which tell how to Build EPICS7 with
> > RTEMS5 for pc-386 by hand here:
> >
> > Part 1
> > :
> https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902
> >
> > Part
> > 2:
> https://medium.com/@mritunjaysharma394/building-epics7-with-rtems5-by-hand-12d9fbd2eb82
> >
> > Please do have a read and give me your feedback for improvements
> >
>
> It looks good.
>
> I think adding the commands you use after the text "Unzip the downloaded
> Zip
> file inside this directory." helps. If the blob captures the exact
> commands it
> makes it easier for me to follow. The EPICS link is hard to find.
>

Thank you so much for the feedback. I will fix that.

>
> > On Mon, Jul 27, 2020 at 7:20 AM Chris Johns  > <mailto:chr...@rtems.org>> wrote:
> >
> > On 27/7/20 10:34 am, Mritunjay Sharma wrote:
> > >
> > > Please find the patch for PC for EPICS here
> > >
> >
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/patches/0001-Added-Support-for-RTEMS-pc386.patch
> >
> > Thanks.
> >
> > > As an experiment, in the 4 patches I have sent to devel for RSB
> recipe a few
> > > days pack, I worked on a local file. I will modify it to published
> source soon
> > > in the next version of patch.
> >
> > Are the EPICS configure files just Makefiles?
> >
> >
> > I think so and more clarity can be given by Heinz on it.
>
> Lets assume they are for now.
>

Okay.

>
> > Can the variables altered in your patch be controlled from the
> command line?
> >
> > What does the `T_A` variables in EPICS mean? I see this is used here
> ...
> >
> > I searched about it in the EPICS documentation and found that T_A
> variable refers
> > to 'T_A) is the current build’s target architecture'.
>
> Target Architecture seems likely. I would assume we need to look into what
> these
> are more.


Yes.


>
>
> I tried to alter it using the command line but I think it didn't work or
> maybe I
> > was doing in the wrong way? Heinz, can you comment on this?
>
> Please post the commands and the output. I find it hard to follow what is
> happening here.
>
> >
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/configure/CONFIG#L64
> >
> > If you look down from this there are some special includes ...
> >
> >
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/configure/CONFIG#L113
> >
> > What are these files for?
> >
> >
> > I found this information about them in the documentation:
> >
> > 'User specific override definitions are allowed in user created files in
> the user’s
> > /configure subdirectory. These override definitions will be used
> for builds
> > in all  directory structures. The files must have the following
> names.
> >
> > /configure/CONFIG_USER
> > /configure/CONFIG_USER.
> > /configure/CONFIG_USER.Common.
> > /configure/CONFIG_USER..'
>
> That is promising but using $HOME makes it hard.
>
> > The link to the documentation is:
> > https://epics.anl.gov/base/R3-15/6-docs/AppDevGuide/BuildFacility.html
>
>
> Thank you for the link. I will take a look.
>
> Chris
>

You are welcome, Chris! Meanwhile, I worked out on testing part a little
bit and will be starting another thread for it.
I am looking forward to your suggestions for the roadmap ahead.

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

Re: [GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

[Mritunjay Sharma]

First of all apologies for a little late response,
please find the link to the blogs which tell how to Build EPICS7 with
RTEMS5 for pc-386 by hand here:

Part 1 :
https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902

Part 2:
https://medium.com/@mritunjaysharma394/building-epics7-with-rtems5-by-hand-12d9fbd2eb82

Please do have a read and give me your feedback for improvements


On Mon, Jul 27, 2020 at 7:20 AM Chris Johns  wrote:

> On 27/7/20 10:34 am, Mritunjay Sharma wrote:
> >
> > Please find the patch for PC for EPICS here
> >
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/patches/0001-Added-Support-for-RTEMS-pc386.patch
>
> Thanks.
>
> > As an experiment, in the 4 patches I have sent to devel for RSB recipe a
> few
> > days pack, I worked on a local file. I will modify it to published
> source soon
> > in the next version of patch.
>
> Are the EPICS configure files just Makefiles?
>

I think so and more clarity can be given by Heinz on it.

>
> Can the variables altered in your patch be controlled from the command
> line?
>
> What does the `T_A` variables in EPICS mean? I see this is used here ...
>

I searched about it in the EPICS documentation and found that T_A variable
refers
to 'T_A) is the current build’s target architecture'.
I tried to alter it using the command line but I think it didn't work or
maybe I was doing in
the wrong way? Heinz, can you comment on this?

>
>
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/configure/CONFIG#L64
>
> If you look down from this there are some special includes ...
>
>
> https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/configure/CONFIG#L113
>
> What are these files for?
>

I found this information about them in the documentation:

'User specific override definitions are allowed in user created files in the
user’s /configure subdirectory. These override definitions will be
used for builds in all  directory structures. The files must have the
following names.

/configure/CONFIG_USER
/configure/CONFIG_USER.
/configure/CONFIG_USER.Common.
/configure/CONFIG_USER..'

The link to the documentation is:
https://epics.anl.gov/base/R3-15/6-docs/AppDevGuide/BuildFacility.html

Thanks
Mritunjay

>
> > There are a few corrections in the blog that I have to make and then
> republish.
> > It’s a bit late here in India now and I am a bit sleepy. Please if you
> don’t
> > mind can I send the blog link in around 6-7 hrs from now?
>
> That fine. Thanks
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

[Mritunjay Sharma]

Hi Chris and Joel,

Thanks for the discussion!

Please find the patch for PC for EPICS here
https://github.com/mritunjaysharma394/epics-mritunjay/blob/master/patches/0001-Added-Support-for-RTEMS-pc386.patch

As an experiment, in the 4 patches I have sent to devel for RSB recipe a few 
days pack, I worked on a local file. I will modify it to published source soon 
in the next version of patch.

There are a few corrections in the blog that I have to make and then republish. 
It’s a bit late here in India now and I am a bit sleepy. Please if you don’t 
mind can I send the blog link in around 6-7 hrs from now?

Thanks
Mritunjay

From: Chris Johns 
Sent: Monday, July 27, 2020 5:35:59 AM
To: j...@rtems.org ; Mritunjay Sharma 

Cc: rtems-de...@rtems.org 
Subject: Re: [GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple 
architectures

On 27/7/20 9:46 am, Joel Sherrill wrote:
> On Fri, Jul 24, 2020 at 8:51 AM Mritunjay Sharma  <mailto:mritunjaysharma...@gmail.com>> wrote:
>
> Hello all,
>
> To update you all, I have sent the first version of PATCHES that
> implement an RSB recipe for EPICS7 building with RTEMS5 for pc-386.
>
> While the build was successful for pc-386, I have doubts and need
> suggestions on how to make it work across different BSP targets.
> I will request Chris to show me the path and if possible then also review
> the patches.
>
>
> I didn't see anything in the patches that look to be pc specific but admit I
> could have missed something.

There is a patch to EPICS for the PC BSP that I cannot find posted online 
anywhere.

> I would try another couple of BSPs known to work with EPICS
> using the same network stack you used for the PC. Options include:
>
> + powerpc and beatnik or a motorola_powerpc variant
> + arm zynq qemu
> + m68k uc5282
>
> Which network stack did you build against?
>

It currently is the legacy stack. Heinz has changes pending for RTEMS 5.

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

Re: [GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

[Mritunjay Sharma]

Hello everyone,

Meanwhile, I publish a couple of blogs of the learnings I made in this
phase, tonight,
I will request you all to kindly review the patches so that I can send the
next version of them.

Also kindly guide, so that the RSB recipe which works only on pc-386 can
also work for other BSP targets for EPICS7+RTEMS5

Thanks
Mritunjay

On Fri, Jul 24, 2020 at 7:20 PM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Hello all,
>
> To update you all, I have sent the first version of PATCHES that
> implement an RSB recipe for EPICS7 building with RTEMS5 for pc-386.
>
> While the build was successful for pc-386, I have doubts and need
> suggestions on how to make it work across different BSP targets.
> I will request Chris to show me the path and if possible then also review
> the patches.
>
> Gedare has suggested using sed but it will be really nice if I can get a
> a more clear idea on how to implement it.
>
> The existing changes in the file can be seen here:
>
>
>
> https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support
>
> Thanks,
> Mritunjay
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

[Mritunjay Sharma]

Hello all,

To update you all, I have sent the first version of PATCHES that
implement an RSB recipe for EPICS7 building with RTEMS5 for pc-386.

While the build was successful for pc-386, I have doubts and need
suggestions on how to make it work across different BSP targets.
I will request Chris to show me the path and if possible then also review
the patches.

Gedare has suggested using sed but it will be really nice if I can get a
a more clear idea on how to implement it.

The existing changes in the file can be seen here:


https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support

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

Re: [GSoC 2020]: Weekly thread: Preparing RSB recipies for EPICS

[Mritunjay Sharma]

Sorry for the inconvenience, Gedare,
I will create another thread in relation with my doubts.

I will also check about sed from here:
https://docs.rtems.org/branches/master/user/testing/configuration.html
and revert back to you!


Thanks
Mritunjay

On Fri, Jul 24, 2020 at 4:35 AM Gedare Bloom  wrote:

> On Thu, Jul 23, 2020 at 3:26 PM Mritunjay Sharma
>  wrote:
> >
> > I have sent the Patches related to the RSB recipe of EPICS build
> > and I will request Chris and other mentors to kindly review and suggest
> improvements.
> >
> > Also Chris, please can you help me how to ake it work across different
> BSPs / architectures?
> > How to add some code to parameterize the EPICS configuration?
> >
> At this point you might want to write a separate email thread to
> clearly describe the problem, your current solution, and request for
> help. Sometimes these conversations in threads get a little bit
> confusing.
>
> I'm starting to wonder if the EPICS configuration can be handled by
> script to manipulate the files (something like sed)
>
> > Thanks
> > Mritunjay
> >
> > On Wed, Jul 22, 2020 at 2:55 AM Gedare Bloom  wrote:
> >>
> >> On Tue, Jul 21, 2020 at 2:16 PM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > I cancelled the earlier message because the log file size was very big
> >> > and could not be posted in the devel list.
> >> >
> >> > [UPDATE]: Applying PATCH for RTEMS-pc386 support to EPICS and
> >> > making other changes in code worked and EPICS7 was successfully built
> >> > and installed using the RSB recipe.
> >> >
> >> > Tha changes that made it work:
> >> >
> >> > -
> >> > diff --git a/rtems/config/epics/epics-7-1.cfg
> b/rtems/config/epics/epics-7-1.cfg
> >> > new file mode 100644
> >> > index ..ed1f768b
> >> > --- /dev/null
> >> > +++ b/rtems/config/epics/epics-7-1.cfg
> >> > @@ -0,0 +1,28 @@
> >> > +#
> >> > +# EPICS 3afec267ab08568ea454789e562450b00feea5c0
> >> > +#
> >> > +
> >> > +%if %{release} == %{nil}
> >> > + %define release 1
> >> > +%endif
> >> > +
> >> > +#%include %{_configdir}/rtems-bsp.cfg
> >> > +
> >> > +#
> >> > +# EPICS Version
> >> > +#
> >> > +%define epics_version 3afec267ab08568ea454789e562450b00feea5c0
> >> > +
> >> > +#%hash sha512 epics-%{ntp_version}.tar.gz
> 8d76fc7e92b2ea6dd5031e6030a7aba4ff6fb3e19d3bc0153852509861be5d0960e70604814163caedb81f8315a451d78371f99634a50b55cfe1cbd2c69e3046
> >> > +
> >> > +#
> >> > +# Patch for RTEMS support.
> >> > +#
> >> > +%patch add epics -p1
> file:///home/mritunjay/development/rtems/src/rsb_GSoC/rtems/patches/0001-Added-Support-for-RTEMS-pc386.patch
> >> > +
> >> > +#%hash  sha512 rtems-ntp-4.2.6p5.diff
> 257223d207d0b77cde2b9d7add22e3b9d657b58998411d2e20d0b1adf36910be21f1277386c54c34f5d9616fccd29f721d007295708047ea7ae0270a00be25a0
> >> > +
> >> > +#
> >> > +# EPICS Build configuration
> >> > +#
> >> > +%include %{_configdir}/epics-7-1.cfg
> >> > diff --git a/rtems/config/epics/epics-base.bset
> b/rtems/config/epics/epics-base.bset
> >> > new file mode 100644
> >> > index ..550daad0
> >> > --- /dev/null
> >> > +++ b/rtems/config/epics/epics-base.bset
> >> > @@ -0,0 +1,26 @@
> >> > +#
> >> > +# Build set for EPICS
> >> > +#
> >> > +
> >> > +%define release 1
> >> > +
> >> > +#
> >> > +# RTEMS Version
> >> > +#
> >> > +%define rtems_version 5
> >> > +
> >> > +#
> >> > +# The RTEMS URL paths.
> >> > +#
> >> > +%include rtems-urls.bset
> >> > +
> >> > +#
> >> > +# The RTEMS Package defines
> >> > +#
> >> > +%include rtems-package.bset
> >> > +
> >> > +
> >> > +#
> >> > +# Build EPICS.
> >> > +#
> >> > +epics/epics-7-1.cfg
> >> > \ No newline at end of file
> >> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> >> > index ea25f284..b18f62bd 100644
> >> > --- a/source-builder/config/epics-7-1.cfg
> >> > +++ 

Re: [GSoC 2020]: Weekly thread: Preparing RSB recipies for EPICS

[Mritunjay Sharma]

I have sent the Patches related to the RSB recipe of EPICS build
and I will request Chris and other mentors to kindly review and suggest
improvements.

Also Chris, please can you help me how to ake it work across different BSPs
/ architectures?
How to add some code to parameterize the EPICS configuration?

Thanks
Mritunjay

On Wed, Jul 22, 2020 at 2:55 AM Gedare Bloom  wrote:

> On Tue, Jul 21, 2020 at 2:16 PM Mritunjay Sharma
>  wrote:
> >
> > I cancelled the earlier message because the log file size was very big
> > and could not be posted in the devel list.
> >
> > [UPDATE]: Applying PATCH for RTEMS-pc386 support to EPICS and
> > making other changes in code worked and EPICS7 was successfully built
> > and installed using the RSB recipe.
> >
> > Tha changes that made it work:
> >
> > -
> > diff --git a/rtems/config/epics/epics-7-1.cfg
> b/rtems/config/epics/epics-7-1.cfg
> > new file mode 100644
> > index ..ed1f768b
> > --- /dev/null
> > +++ b/rtems/config/epics/epics-7-1.cfg
> > @@ -0,0 +1,28 @@
> > +#
> > +# EPICS 3afec267ab08568ea454789e562450b00feea5c0
> > +#
> > +
> > +%if %{release} == %{nil}
> > + %define release 1
> > +%endif
> > +
> > +#%include %{_configdir}/rtems-bsp.cfg
> > +
> > +#
> > +# EPICS Version
> > +#
> > +%define epics_version 3afec267ab08568ea454789e562450b00feea5c0
> > +
> > +#%hash sha512 epics-%{ntp_version}.tar.gz
> 8d76fc7e92b2ea6dd5031e6030a7aba4ff6fb3e19d3bc0153852509861be5d0960e70604814163caedb81f8315a451d78371f99634a50b55cfe1cbd2c69e3046
> > +
> > +#
> > +# Patch for RTEMS support.
> > +#
> > +%patch add epics -p1
> file:///home/mritunjay/development/rtems/src/rsb_GSoC/rtems/patches/0001-Added-Support-for-RTEMS-pc386.patch
> > +
> > +#%hash  sha512 rtems-ntp-4.2.6p5.diff
> 257223d207d0b77cde2b9d7add22e3b9d657b58998411d2e20d0b1adf36910be21f1277386c54c34f5d9616fccd29f721d007295708047ea7ae0270a00be25a0
> > +
> > +#
> > +# EPICS Build configuration
> > +#
> > +%include %{_configdir}/epics-7-1.cfg
> > diff --git a/rtems/config/epics/epics-base.bset
> b/rtems/config/epics/epics-base.bset
> > new file mode 100644
> > index ..550daad0
> > --- /dev/null
> > +++ b/rtems/config/epics/epics-base.bset
> > @@ -0,0 +1,26 @@
> > +#
> > +# Build set for EPICS
> > +#
> > +
> > +%define release 1
> > +
> > +#
> > +# RTEMS Version
> > +#
> > +%define rtems_version 5
> > +
> > +#
> > +# The RTEMS URL paths.
> > +#
> > +%include rtems-urls.bset
> > +
> > +#
> > +# The RTEMS Package defines
> > +#
> > +%include rtems-package.bset
> > +
> > +
> > +#
> > +# Build EPICS.
> > +#
> > +epics/epics-7-1.cfg
> > \ No newline at end of file
> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> > index ea25f284..b18f62bd 100644
> > --- a/source-builder/config/epics-7-1.cfg
> > +++ b/source-builder/config/epics-7-1.cfg
> > @@ -31,6 +31,7 @@ URL:  https://epics.mpg.de/
> >source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"
> >
> >%source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}
> > +  %patch setup epics -p1
> >
> >cd ${build_top}
> >
> > @@ -43,10 +44,7 @@ URL:  https://epics.mpg.de/
> >
> >%{__make} PREFIX=%{_prefix}
> >
> > -  ./configure \
> > ---prefix=%{_prefix}
> > -
> > -  %{__make} %{?_smp_mflags}
> > +  #%{__make} %{?_smp_mflags}
> >
> >cd ${build_top}
> > --
> >
> > The changes can also be looked here:
> https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support?expand=1
> >
> >
> >
> >
> >
> > On Tue, Jul 21, 2020 at 10:23 PM Gedare Bloom  wrote:
> >>
> >> On Tue, Jul 21, 2020 at 10:42 AM Mritunjay Sharma
> >>  wrote:
> >> >
> >> > [UPDATE]: The error was actually a mismatch of names which was fixed
> with the following
> >> > changes:
> >> > ---
> >> >
> >> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> >> > index fe1fb458..ea25f284 100644
> >> > --- a/source-builder/config/epics-7-1.cfg
> >> > +++ b/

[PATCH rtems_rsb 4/4] Added sha512 hash for patch and source

[Mritunjay Sharma]

Signed-off-by: Mritunjay Sharma 
---
 rtems/config/epics/epics-7-1.cfg| 10 +++---
 source-builder/config/epics-7-1.cfg |  2 --
 2 files changed, 3 insertions(+), 9 deletions(-)

diff --git a/rtems/config/epics/epics-7-1.cfg b/rtems/config/epics/epics-7-1.cfg
index ed1f768..f9541d5 100644
--- a/rtems/config/epics/epics-7-1.cfg
+++ b/rtems/config/epics/epics-7-1.cfg
@@ -6,23 +6,19 @@
  %define release 1
 %endif
 
-#%include %{_configdir}/rtems-bsp.cfg
-
 #
 # EPICS Version
 #
 %define epics_version 3afec267ab08568ea454789e562450b00feea5c0
 
-#%hash sha512 epics-%{ntp_version}.tar.gz 
8d76fc7e92b2ea6dd5031e6030a7aba4ff6fb3e19d3bc0153852509861be5d0960e70604814163caedb81f8315a451d78371f99634a50b55cfe1cbd2c69e3046
-
+%hash sha512 epicsBaseOwnPlayground-%{epics_version}.tar.gz 
6f2953756cc3c8420da59d8bafac83380565f49c16ec82e8ed253b803419e477ff1b7760f356237da7d028b24e393da717c31dbf733b41a8a586dc111868a418
 #
 # Patch for RTEMS support.
 #
 %patch add epics -p1 
file:///home/mritunjay/development/rtems/src/rsb_GSoC/rtems/patches/0001-Added-Support-for-RTEMS-pc386.patch
- 
-#%hash  sha512 rtems-ntp-4.2.6p5.diff 
257223d207d0b77cde2b9d7add22e3b9d657b58998411d2e20d0b1adf36910be21f1277386c54c34f5d9616fccd29f721d007295708047ea7ae0270a00be25a0
 
+%hash  sha512 0001-Added-Support-for-RTEMS-pc386.patch 
436e2dc08bba1e9a14636ca8a859c6df361207e59d544f8c6cf5b6da90989b88e31b36c8b876b478af4f995238199c1a60a4ca9b044d237c2ec099942788dcdb
 #
 # EPICS Build configuration
 #
-%include %{_configdir}/epics-7-1.cfg
+%include %{_configdir}/epics-7-1.cfg
\ No newline at end of file
diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7-1.cfg
index b18f62b..16f1471 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -44,8 +44,6 @@ URL:https://epics.mpg.de/
 
   %{__make} PREFIX=%{_prefix}
 
-  #%{__make} %{?_smp_mflags}
-
   cd ${build_top}
 
 %install
-- 
2.25.1

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

[PATCH rtems_rsb 3/4] Added Patch for pc386 and EPICS build is working now

[Mritunjay Sharma]

Signed-off-by: Mritunjay Sharma 
---
 rtems/config/epics/epics-7-1.cfg| 28 
 rtems/config/epics/epics-base.bset  | 26 ++
 source-builder/config/epics-7-1.cfg |  6 ++
 3 files changed, 56 insertions(+), 4 deletions(-)
 create mode 100644 rtems/config/epics/epics-7-1.cfg
 create mode 100644 rtems/config/epics/epics-base.bset

diff --git a/rtems/config/epics/epics-7-1.cfg b/rtems/config/epics/epics-7-1.cfg
new file mode 100644
index 000..ed1f768
--- /dev/null
+++ b/rtems/config/epics/epics-7-1.cfg
@@ -0,0 +1,28 @@
+#
+# EPICS 3afec267ab08568ea454789e562450b00feea5c0
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+#%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 3afec267ab08568ea454789e562450b00feea5c0
+
+#%hash sha512 epics-%{ntp_version}.tar.gz 
8d76fc7e92b2ea6dd5031e6030a7aba4ff6fb3e19d3bc0153852509861be5d0960e70604814163caedb81f8315a451d78371f99634a50b55cfe1cbd2c69e3046
+
+#
+# Patch for RTEMS support.
+#
+%patch add epics -p1 
file:///home/mritunjay/development/rtems/src/rsb_GSoC/rtems/patches/0001-Added-Support-for-RTEMS-pc386.patch
+ 
+#%hash  sha512 rtems-ntp-4.2.6p5.diff 
257223d207d0b77cde2b9d7add22e3b9d657b58998411d2e20d0b1adf36910be21f1277386c54c34f5d9616fccd29f721d007295708047ea7ae0270a00be25a0
+
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7-1.cfg
diff --git a/rtems/config/epics/epics-base.bset 
b/rtems/config/epics/epics-base.bset
new file mode 100644
index 000..550daad
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,26 @@
+#
+# Build set for EPICS
+#
+
+%define release 1
+
+#
+# RTEMS Version
+#
+%define rtems_version 5
+
+#
+# The RTEMS URL paths.
+#
+%include rtems-urls.bset
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+
+#
+# Build EPICS.
+#
+epics/epics-7-1.cfg
\ No newline at end of file
diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7-1.cfg
index ea25f28..b18f62b 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -31,6 +31,7 @@ URL:https://epics.mpg.de/
   source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"
 
   %source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}
+  %patch setup epics -p1
 
   cd ${build_top}
 
@@ -43,10 +44,7 @@ URL:   https://epics.mpg.de/
 
   %{__make} PREFIX=%{_prefix}
 
-  ./configure \
---prefix=%{_prefix}
-
-  %{__make} %{?_smp_mflags}
+  #%{__make} %{?_smp_mflags}
 
   cd ${build_top}
 
-- 
2.25.1

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

[PATCH rtems_rsb 1/4] Initial step to build EPICS

[Mritunjay Sharma]

Signed-off-by: Mritunjay Sharma 
---
 source-builder/config/epics-7-1.cfg | 65 +
 1 file changed, 65 insertions(+)
 create mode 100644 source-builder/config/epics-7-1.cfg

diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7-1.cfg
new file mode 100644
index 000..fe1fb45
--- /dev/null
+++ b/source-builder/config/epics-7-1.cfg
@@ -0,0 +1,65 @@
+#
+# EPICS 7.x.x Version 1.
+#
+# This configuration file configure's, make's and install's EPICS.
+#
+
+%if %{release} == %{nil}
+%define release 1
+%endif
+
+%define epics_version 3afec267ab08568ea454789e562450b00feea5c0
+
+Name:  epics-%{epics_version}-%{_host}-%{release}
+Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
+Version:   %{epics_version}
+Release:   %{release}
+URL: https://epics.mpg.de/
+
+#
+# Source
+#
+%source set epics --rsb-file=epics-%{epics_version}.zip 
https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.zip
+
+#
+# Prepare the source code.
+#
+%prep
+  build_top=$(pwd)
+
+  source_dir_epics="epics-%{epics_version}"
+
+  %source setup epics -q -n epics-%{epics_version}
+
+  cd ${build_top}
+
+%build
+  build_top=$(pwd)
+
+
+
+  %{build_directory}
+
+  mkdir -p ${build_dir}
+  cd ${build_dir}
+
+  %{host_build_flags}
+
+  #cd ${source_dir_epics}
+
+  ./configure \
+--prefix=%{_prefix}
+
+  %{__make} %{?_smp_mflags}
+
+  cd ${build_top}
+
+%install
+  build_top=$(pwd)
+
+  rm -rf $SB_BUILD_ROOT
+
+  cd ${source_dir_epics}
+  %{__make} DESTDIR=$SB_BUILD_ROOT PREFIX=%{_prefix} install
+
+  cd ${build_top}
-- 
2.25.1

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

[PATCH rtems_rsb 2/4] Modified to fix 'can't cd' error

[Mritunjay Sharma]

Signed-off-by: Mritunjay Sharma 
---
 source-builder/config/epics-7-1.cfg | 20 
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/source-builder/config/epics-7-1.cfg 
b/source-builder/config/epics-7-1.cfg
index fe1fb45..ea25f28 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -10,7 +10,7 @@
 
 %define epics_version 3afec267ab08568ea454789e562450b00feea5c0
 
-Name:  epics-%{epics_version}-%{_host}-%{release}
+Name:  epicsBaseOwnPlayground-%{epics_version}-%{_host}-%{release}
 Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
 Version:   %{epics_version}
 Release:   %{release}
@@ -19,7 +19,8 @@ URL:https://epics.mpg.de/
 #
 # Source
 #
-%source set epics --rsb-file=epics-%{epics_version}.zip 
https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.zip
+%source set epics --rsb-file=epicsBaseOwnPlayground-%{epics_version}.tar.gz 
https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.tar.gz
+
 
 #
 # Prepare the source code.
@@ -27,25 +28,20 @@ URL:  https://epics.mpg.de/
 %prep
   build_top=$(pwd)
 
-  source_dir_epics="epics-%{epics_version}"
+  source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"
 
-  %source setup epics -q -n epics-%{epics_version}
+  %source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}
 
   cd ${build_top}
 
 %build
   build_top=$(pwd)
 
-
-
-  %{build_directory}
-
-  mkdir -p ${build_dir}
-  cd ${build_dir}
+  cd ${source_dir_epics}
 
-  %{host_build_flags}
+  %{build_build_flags}
 
-  #cd ${source_dir_epics}
+  %{__make} PREFIX=%{_prefix}
 
   ./configure \
 --prefix=%{_prefix}
-- 
2.25.1

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

Re: [GSoC 2020]: Weekly thread: Preparing RSB recipies for EPICS

[Mritunjay Sharma]

I cancelled the earlier message because the log file size was very big
and could not be posted in the devel list.

[UPDATE]: Applying PATCH for RTEMS-pc386 support to EPICS and
making other changes in code worked and EPICS7 was successfully built
and installed using the RSB recipe.

Tha changes that made it work:

-
diff --git a/rtems/config/epics/epics-7-1.cfg
b/rtems/config/epics/epics-7-1.cfg
new file mode 100644
index ..ed1f768b
--- /dev/null
+++ b/rtems/config/epics/epics-7-1.cfg
@@ -0,0 +1,28 @@
+#
+# EPICS 3afec267ab08568ea454789e562450b00feea5c0
+#
+
+%if %{release} == %{nil}
+ %define release 1
+%endif
+
+#%include %{_configdir}/rtems-bsp.cfg
+
+#
+# EPICS Version
+#
+%define epics_version 3afec267ab08568ea454789e562450b00feea5c0
+
+#%hash sha512 epics-%{ntp_version}.tar.gz
8d76fc7e92b2ea6dd5031e6030a7aba4ff6fb3e19d3bc0153852509861be5d0960e70604814163caedb81f8315a451d78371f99634a50b55cfe1cbd2c69e3046
+
+#
+# Patch for RTEMS support.
+#
+%patch add epics -p1
file:///home/mritunjay/development/rtems/src/rsb_GSoC/rtems/patches/0001-Added-Support-for-RTEMS-pc386.patch
+
+#%hash  sha512 rtems-ntp-4.2.6p5.diff
257223d207d0b77cde2b9d7add22e3b9d657b58998411d2e20d0b1adf36910be21f1277386c54c34f5d9616fccd29f721d007295708047ea7ae0270a00be25a0
+
+#
+# EPICS Build configuration
+#
+%include %{_configdir}/epics-7-1.cfg
diff --git a/rtems/config/epics/epics-base.bset
b/rtems/config/epics/epics-base.bset
new file mode 100644
index ..550daad0
--- /dev/null
+++ b/rtems/config/epics/epics-base.bset
@@ -0,0 +1,26 @@
+#
+# Build set for EPICS
+#
+
+%define release 1
+
+#
+# RTEMS Version
+#
+%define rtems_version 5
+
+#
+# The RTEMS URL paths.
+#
+%include rtems-urls.bset
+
+#
+# The RTEMS Package defines
+#
+%include rtems-package.bset
+
+
+#
+# Build EPICS.
+#
+epics/epics-7-1.cfg
\ No newline at end of file
diff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg
index ea25f284..b18f62bd 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -31,6 +31,7 @@ URL:  https://epics.mpg.de/
   source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"

   %source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}
+  %patch setup epics -p1

   cd ${build_top}

@@ -43,10 +44,7 @@ URL:  https://epics.mpg.de/

   %{__make} PREFIX=%{_prefix}

-  ./configure \
---prefix=%{_prefix}
-
-  %{__make} %{?_smp_mflags}
+  #%{__make} %{?_smp_mflags}

   cd ${build_top}
--

The changes can also be looked here:
https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support?expand=1





On Tue, Jul 21, 2020 at 10:23 PM Gedare Bloom  wrote:

> On Tue, Jul 21, 2020 at 10:42 AM Mritunjay Sharma
>  wrote:
> >
> > [UPDATE]: The error was actually a mismatch of names which was fixed
> with the following
> > changes:
> > ---
> >
> > diff --git a/source-builder/config/epics-7-1.cfg
> b/source-builder/config/epics-7-1.cfg
> > index fe1fb458..ea25f284 100644
> > --- a/source-builder/config/epics-7-1.cfg
> > +++ b/source-builder/config/epics-7-1.cfg
> > @@ -10,7 +10,7 @@
> >
> >  %define epics_version 3afec267ab08568ea454789e562450b00feea5c0
> >
> > -Name:  epics-%{epics_version}-%{_host}-%{release}
> > +Name:  epicsBaseOwnPlayground-%{epics_version}-%{_host}-%{release}
> >  Summary:   EPICS v%{epics_version} for target %{_target} on host
> %{_host}
> >  Version:   %{epics_version}
> >  Release:   %{release}
> > @@ -19,7 +19,8 @@ URL:  https://epics.mpg.de/
> >  #
> >  # Source
> >  #
> > -%source set epics --rsb-file=epics-%{epics_version}.zip
> https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.zip
> > +%source set epics
> --rsb-file=epicsBaseOwnPlayground-%{epics_version}.tar.gz
> https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.tar.gz
> > +
> >
> >  #
> >  # Prepare the source code.
> > @@ -27,25 +28,20 @@ URL:  https://epics.mpg.de/
> >  %prep
> >build_top=$(pwd)
> >
> > -  source_dir_epics="epics-%{epics_version}"
> > +  source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"
> >
> > -  %source setup epics -q -n epics-%{epics_version}
> > +  %source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}
> >
>
> We will eventually want this to work from the upstream EPICS.
>

Yes, I think we need to discuss it with Heinz when he is available.


>
>
> >cd ${build_top}
> >
> >  %build
> >build_top=$(pwd)
> >
> > -
> > -
> > -  %{build_directory

Re: [GSoC 2020]: Weekly thread: Preparing RSB recipies for EPICS

[Mritunjay Sharma]

[UPDATE]: The error was actually a mismatch of names which was fixed with
the following
changes:
---

diff --git a/source-builder/config/epics-7-1.cfg
b/source-builder/config/epics-7-1.cfg
index fe1fb458..ea25f284 100644
--- a/source-builder/config/epics-7-1.cfg
+++ b/source-builder/config/epics-7-1.cfg
@@ -10,7 +10,7 @@

 %define epics_version 3afec267ab08568ea454789e562450b00feea5c0

-Name:  epics-%{epics_version}-%{_host}-%{release}
+Name:  epicsBaseOwnPlayground-%{epics_version}-%{_host}-%{release}
 Summary:   EPICS v%{epics_version} for target %{_target} on host %{_host}
 Version:   %{epics_version}
 Release:   %{release}
@@ -19,7 +19,8 @@ URL:https://epics.mpg.de/
 #
 # Source
 #
-%source set epics --rsb-file=epics-%{epics_version}.zip
https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.zip
+%source set epics
--rsb-file=epicsBaseOwnPlayground-%{epics_version}.tar.gz
https://github.com/hjunkes/epicsBaseOwnPlayground/archive/%{epics_version}.tar.gz
+

 #
 # Prepare the source code.
@@ -27,25 +28,20 @@ URL:  https://epics.mpg.de/
 %prep
   build_top=$(pwd)

-  source_dir_epics="epics-%{epics_version}"
+  source_dir_epics="epicsBaseOwnPlayground-%{epics_version}"

-  %source setup epics -q -n epics-%{epics_version}
+  %source setup epics -q -n epicsBaseOwnPlayground-%{epics_version}

   cd ${build_top}

 %build
   build_top=$(pwd)

-
-
-  %{build_directory}
-
-  mkdir -p ${build_dir}
-  cd ${build_dir}
+  cd ${source_dir_epics}

-  %{host_build_flags}
+  %{build_build_flags}

-  #cd ${source_dir_epics}
+  %{__make} PREFIX=%{_prefix}

   ./configure \
 --prefix=%{_prefix}


--

After this, I ran the command

`../source-builder/sb-builder --prefix=/home/mritunjay/development
--log=log_epics epics-7-1 --trace`

again. The error that has come now was expected because the changes I
made in epicsBaseOwnPlayground/configure file

were done manually and here it has to be done through a script. The
changes that I did manually were;

in epics-base/configure/CONFIG_SITE
> set
> CROSS_COMPILER_TARGET_ARCHS=
>
   What I entered:
   CROSS_COMPILER_TARGET_ARCHS=  RTEMS-pc386-qemu

> 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:
#FHI
RTEMS_VERSION = 5
RTEMS_BASE = /home/mritunjay/development/rtems/$(RTEMS_VERSION)

I have a doubt on how to implement the above changes in the
`source-builder/config/epics-7-1.cfg` to make it work.

Do we have to write a patch? And what will be the best way to do it?

The latest error looks somewhat like this which is because I have to
change the configurations in epics directory.

The question is how to accomplish it through the script.

../../configure/os/CONFIG.Common.RTEMS:36:
/Users/junkes/MVME6100/RTEMS/rtems-5/powerpc-rtems5/beatnik/Makefile.inc:
No such file or directory



Thanks

Mritunjay



On Tue, Jul 21, 2020 at 4:09 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Hello all,
>
> I went through the
> https://docs.rtems.org/branches/master/user/rsb/index.html
> and started writing a recipe for building EPICS 7.
>
> The code is based on a very raw idea just now and
> so was expected to give errors.
>
> The code can be found here:
> https://github.com/mritunjaysharma394/rtems-source-builder/blob/epics-support/source-builder/config/epics-7-1.cfg
>
> After this, just to check, what errors it might gave,
> I ran the following command:
>
> ../source-builder/sb-builder --prefix=/home/mritunjay/development
>  --log=log_epics epics-7-1 --trace
>
> This gave me the following error:
>
> `+ cd epics-3afec267ab08568ea454789e562450b00feea5c0
> /home/mritunjay/development/rtems/src/rsb_GSoC/rtems/build/epics-3afec267ab08568ea454789e562450b00feea5c0-x86_64-linux-gnu-1/do-build:
> 90: cd: can't cd to epics-3afec267ab08568ea454789e562450b00feea5c0
> shell cmd failed: /bin/sh -ex
>  
> /home/mritunjay/development/rtems/src/rsb_GSoC/rtems/build/epics-3afec267ab08568ea454789e562450b00feea5c0-x86_64-linux-gnu-1/do-build
> error: building
> epics-3afec267ab08568ea454789e562450b00feea5c0-x86_64-linux-gnu-1`
>
> I think there seems to be some problem with naming the directory.
> I request you all to kindly help with the error as well as please check
> the code
> to see if I am on the right path.
> I am attaching the log and trace file as well.
>
> Thanks,
> Mritunjay
>
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2020]: Weekly thread update

[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:
>> >>>>
>> >>

Re: [GSoC 2020]: Weekly thread update

[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.
> >>>>>
> &g

Re: [GSoC 2020]: Weekly thread update

[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 fo

Re: [GSoC 2020]: Weekly thread update

[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
>>>
>>>>
&

Re: [GSoC 2020]: Weekly thread update

[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:
>>

Re: [GSoC 2020]: Weekly thread update

[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

[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/
<https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/>
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.

S

[GSoC 2020]: Weekly thread update

[Mritunjay Sharma]

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.

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

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

```

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

However, I will like to request all my mentors to help me set the goals
for this week and where should I begin 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]

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

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 Git

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 c

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

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

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

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

[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

[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: Error in bootstraping RTEMS

[Mritunjay Sharma]

Hello Eshan,

Can you please try to re-run bootstrap? I think I faced similar error and 
bootstrapping again helped me

Thanks,
Mritunjay

Get Outlook for iOS

From: devel  on behalf of Eshan Dhawan 

Sent: Sunday, July 5, 2020 12:40:37 AM
To: rtems-de...@rtems.org 
Subject: Error in bootstraping RTEMS

hello everyone,
I was bootstrapping my branch and got this error
link to the branch : https://github.com/eshandhawan51/rtems/tree/ftw_test
It has tests for FTW.H tests
error :
120/121: autoreconf: testsuites/libtests/configure.ac
Makefile.am:457: error: lib_tests must be set with '=' before using '+='
Makefile.am:458: error: lib_screens must be set with '=' before using '+='
Makefile.am:459: error: lib_docs must be set with '=' before using '+='
Makefile.am:460: warning: variable 'tar01_SOURCES' is defined but no program or
Makefile.am:460: library has 'tar01' as canonical name (possible typo)
Makefile.am:465: warning: variable 'tar01_LDADD' is defined but no program or
Makefile.am:465: library has 'tar01' as canonical name (possible typo)
autoreconf: automake failed with exit status: 1
error: error: autoreconf: autoreconf -i --no-recursive
Bootstrap FAILED

--
Thanks
- Eshan
___
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

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

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

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 instruct

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]: *** [libComTestH

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

[Mritunjay Sharma]

 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 9:03 AM Heinz Junkes 
wrote:

> Hello, Mritunjay,
>
> unfortunately i still miss a transcript in which the things you do are
> listed in detail.
> Then we could really help you better.
>
> Heinz
>
> > On 3. Jul 2020, at 04:14, Chris Johns  wrote:
> >
> > 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
>
>
___
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

[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 Hei

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

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

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/

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

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

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

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/epi

Re: GSoC 2020: Weekly Progress Update

[Mritunjay Sharma]

On Fri, Jun 19, 2020 at 11:45 AM Chris Johns  wrote:

> On 17/6/20 3:11 pm, Mritunjay Sharma wrote:
> > Hello everyone,
> >
> > Following up as decided to update the weekly progress report on irc
> > channel on every Wednesday, I am updating the progress on the mailing
> list as well.
>
> Thank you for this. I cannot make IRC on a regular basis and email is best
> for
> me. Please keep the posts coming.
>
> >
> > ==Previous Work==
> >
> > Trying to fix missing files like "install/sh" error
> > to make the ptpd build run.
> >
> > ==Progress==
> >
> > Earlier errors have been resolved but a new one popped up in the morning.
> >
> > Modified source-builder/config/ptpd-2-1.cfg file again,
> > after Googling a little and following Heinz advice,
> >
> > %source setup ptpd -q -n ptpd-%{ptpd_version}
> > %patch setup ptpd -p1
> >
> >
> > +autoreconf -vfi
>
> This is causing me problems. I wonder why. I get ...
>
> configure.ac:27: error: possibly undefined macro: AC_PROG_LIBTOOL
>
> I will take a look at the release tarballs  tt looks like the release
> tarballs do not have generated autoconf files. Hmmm.
> > +automake --add-missing
> >
> > cd ${build_top}
> >
> > %build
> >
> > After this I made the local ptpd-master again a tar ball and used it,
> > which fixed the earlier, but now another error has popped up which I
> > am trying to fix.
> >
> > The error is as follows:
> >
> "/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build:
> > 155:
> >
> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build:
> > ../ptpd-master/configure: not found
> > shell cmd failed: /bin/sh -ex
> >
>  
> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build
> > error: building ptpd-master-arm-rtems5-1
> >   See error report: rsb-report-ptpd-master-arm-rtems5-1.txt
> > Build Set: Time 0:00:00.191542"
> >
> > ==Blockers==
> >
> > These configure errors are the main blockers.
> >
> > ==Future options==
> >
> > Looking forward to raise this with the ptpd community
> > and trying with the help of mentors to fix the problems
> > as soon as possible.
>
> I think we are wedged. For us to build a package for RTEMS we need access
> the
> RTEMS tools built by the RSB. Building these tools also builds a version of
> autoconf and automake we need to configure RTEMS. With the path set to
> include
> the RTEMS tools and so the RTEMS built autoconf and automake the PTPD
> INSTALL
> documented step of `autoreconf -vi` fails with the error above.
>
> I decided to test by hand using the following steps:
>
>  wget https://github.com/ptpd/ptpd/archive/ptpd.2.3.1.tar.gz
>  tar zxf ptpd.2.3.1.tar.gz
>  cd ptpd-ptpd.2.3.1
>  autoreconf -vi
>
> The generate has no isssue.
>
> I then added the RTEMS tools path back into my path. I also have the
> Xilinx Zynq
> QEMU BSP installed under my prefix so I entered ...
>
> LIBS="-lrtemsdefaultconfig"
> CFLAGS="-I/opt/work/rtems/5/arm-rtems5/xilinx_zynq_a9_qemu/lib/include
> -qrtems
> -B/opt/work/rtems/5/arm-rtems5/lib/
> -B/opt/work/rtems/5/arm-rtems5/xilinx_zynq_a9_qemu/lib/ --specs bsp_specs
> -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard -mtune=cortex-a9 -O0 -g
> -ffunction-sections -fdata-sections" ./configure --host=arm-rtems5
> --disable-snmp --enable-slave-only --disable-pcap
>
> The configure completed without error. I do not think there is any point
> contacting the ptpd community just yet.
>
> The build however failed with ..
>
> ptpd.h:93:10: fatal error: netinet/ip.h: No such file or directory
>
> I suggest you step back from the RSB and build ptpd by hand. I have not
> looked
> into what is wrong and why I get this compile error.
>

Okay Chris, thank you for this suggestion, I will work on this and update
you.
I can tell you that I encountered the same error when I was building ptpd
with erc32 using RSB and then I was asked to add a different package that
contains netinet/ip.h and then build it first. I will get to you more on
this error
because I have worked on it earlier however while building it configure
errors
again started playing their tricks and when I started doing it with
xilinx_zynq_a9_qemu using RSB,
 it never came but the errors as mentioned earlier came up.

Mritunjay

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

GSoC 2020: Weekly Progress Update

[Mritunjay Sharma]

Hello everyone,

Following up as decided to update the weekly progress report on irc
channel on every Wednesday, I am updating the progress on the mailing list
as well.

==Previous Work==

Trying to fix missing files like "install/sh" error
to make the ptpd build run.

==Progress==

Earlier errors have been resolved but a new one popped up in the morning.

Modified source-builder/config/ptpd-2-1.cfg file again,
after Googling a little and following Heinz advice,

%source setup ptpd -q -n ptpd-%{ptpd_version}
%patch setup ptpd -p1


+autoreconf -vfi
+automake --add-missing

cd ${build_top}

%build

After this I made the local ptpd-master again a tar ball and used it,
which fixed the earlier, but now another error has popped up which I
am trying to fix.

The error is as follows:
"/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build:
155:
/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build:
../ptpd-master/configure: not found
shell cmd failed: /bin/sh -ex
 
/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build
error: building ptpd-master-arm-rtems5-1
  See error report: rsb-report-ptpd-master-arm-rtems5-1.txt
Build Set: Time 0:00:00.191542"

==Blockers==

These configure errors are the main blockers.

==Future options==

Looking forward to raise this with the ptpd community
and trying with the help of mentors to fix the problems
as soon as possible.

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

Re: GSoC 2020: [rtems/rsb]: Error while adding ptp support. This time building for xilinx_zynq_a9_qemu

[Mritunjay Sharma]

Thank you so much Heinz for such a detailed response.
It really helped me a lot.

As advised by you and Heinz, I changed the source to
https://github.com/mritunjaysharma394/ptpd/archive/master.zip
with suggested changes. However, I have encountered few bugs again related
to autoreconf.
It looks somewhat like this:

+ autoreconf -i -v
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: creating directory build-aux
autoreconf: configure.ac: not using Libtool
autoreconf: running: /home/mritunjay/development/rtems/5/bin/autoconf
configure.ac:28: error: possibly undefined macro: AC_PROG_LIBTOOL
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /home/mritunjay/development/rtems/5/bin/autoconf failed with
exit status: 1
shell cmd failed: /bin/sh -ex
 
/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-master-arm-rtems5-1/do-build
error: building ptpd-master-arm-rtems5-1

I have attached the error report as well and changes in cfg files can be
found here:
https://github.com/mritunjaysharma394/rtems-source-builder/commit/6b6bb2b3bd778ebe56e9a1bf3aec1747b078fd39

Thanks,
Mritunjay


On Fri, Jun 5, 2020 at 2:53 AM Gedare Bloom  wrote:

> On Thu, Jun 4, 2020 at 1:38 PM junkes  wrote:
> >
> > Hallo Mritunjay,
> >
> > You can't just take the github ptpd sources and make them work in RTEMS.
> You have to make some configuration
> > and sources changes before you can build the with the rsb.
> >
> > Some things like the sys/cpuset.h seems not to be fully compatible yet
> and so the configure simply makes
> > "wrong" decisions. E.g. defines HAVE_SYS_CPUSET_H = 1 as sys/cpuset.h
> exists.I played a little bit with it and reset
> > the definition in ptpd-master/src/ptpd.h  (quick and dirty) and could
> reduce the error messages because there is a query for
> > this variable in the code (src/dep/sys.c):
> >
> > in ptpd.h after the include of the created configs :
> >
> > ...
> > #ifdef HAVE_CONFIG_H
> > # include 
> > #endif /* HAVE_CONFIG_H */
> >
> > #undef HAVE_NTP_GETTIME
> > #undef HAVE_SYS_CPUSET_H
> >
> > #ifdef linux
> > ...
> >
> > in src/dep/sys.c
> >
> > ...
> > #ifdef HAVE_SYS_CPUSET_H
> >cpuset_t mask;
> >CPU_ZERO(&mask);
> >if(cpu >= 0) {
> >CPU_SET(cpu,&mask);
> >} else {
> >int i;
> >for(i = 0;  i < CPU_SETSIZE; i++) {
> >CPU_SET(i, &mask);
> >}
> >}
> >return(cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_PID,
> >  -1, sizeof(mask), &mask));
> > #endif /* HAVE_SYS_CPUSET_H */
> >
> > In src/dep/constants_dep.h  one can find:
> >
> > * platform dependent */
> >
> > #if !defined(linux) && !defined(__NetBSD__) && !defined(__FreeBSD__) && \
> > !defined(__APPLE__) && !defined(__OpenBSD__) && !defined(__sun) &&
> !defined(__QNXNTO__)
> > #error PTPD hasn't been ported to this OS - should be possible \
> > if it's POSIX compatible, if you succeed, report it to
> ptpd-de...@sourceforge.net
> > #endif
> >
> > here I added "&& !defined(__rtems__)
> >
> > and here:
> > ...
> > #if defined(__NetBSD__) || defined(__FreeBSD__) || defined(__APPLE__) ||
> defined(__OpenBSD__) || defined(__sun) || defined(__QNXNTO__) ||
> defined(__rtems__)
> > # include 
> > # include 
> > #ifdef HAVE_SYS_SOCKIO_H
> > #include 
> > #endif /* HAVE_SYS_SOCKIO_H */
> > # include 
> > # include 
> > # include 
> > # include 
> > #ifdef HAVE_NET_IF_ETHER_H
> > #  include 
> > ...
> >
> > and so on... You'd have to bite through it once and then you will surely
> get it compiled.
> >
> Great start Heinz! Mritunjay, I think this definitely the way forward.
> Later, you might try to circle back and fix the hacks in nicer ways by
> learning how to make the autoconf stuff work correctly, and contribute
> those fixes back upstream to ptpd project.
>
> > HTH Heinz
> >
> >
> >
> > On 2020-06-04 20:29, Mritunjay Sharma wrote:
> >
> >
> >
> > On Thu, Jun 4, 2020 at 11:07 PM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
> >
> > On 04/06/2020 16:22, Gedare Bloom wrote:
> >
> > >>> In the github version this co

Re: GSoC 2020: [rtems/rsb]: Error while adding ptp support. This time building for xilinx_zynq_a9_qemu

[Mritunjay Sharma]

On Thu, Jun 4, 2020 at 11:07 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 04/06/2020 16:22, Gedare Bloom wrote:
>
> >>> In the github version this code is conditional on sys/cpuset.h being
> present.
> >>>
> > Well, we do have a sys/cpuset.h in newlib. It doesn't have these BSD
> > definitions though. Probably either:
> > 1. Add more stuff to sys/cpuset.h to make it support BSDisms. This
> > would mean adding cpuset_setaffinity support in rtems, I guess.
> > 2. Figure out how to disable the conditional code using the
> > cpuset_setaffinity function.
> The  is already as compatible as possible to glibc and
> FreeBSD. There is always room for improvement, however, in this area it
> will be difficult.
>

Please it would be kind of you all to guide on what is the best thing I can
do next. It is looking
a little difficult. If something similar has been done earlier, sharing it
can be a lot helpful to take a cue.

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

Re: GSoC 2020: [rtems/rsb]: Error while adding ptp support. This time building for xilinx_zynq_a9_qemu

[Mritunjay Sharma]

On Thu, Jun 4, 2020 at 10:39 AM Chris Johns  wrote:

> On 4/6/20 2:31 pm, Gedare Bloom wrote:
> > On Wed, Jun 3, 2020 at 1:53 PM Mritunjay Sharma
> >  wrote:
> >>
> >> Hello everyone,
> >>
> >> As suggested by Heinz, I started building for xilinx_zynq_a9_qemu
> >> with a little modification in ptp cfg file.
> >>
> >> The netinet is no longer a problem here but another problem has come as
> follows:
> >>
> >> ../../ptpd-2.3.1/src/dep/startup.c: In function 'ptpdStartup':
>
> Is this from sourceforge?
>

Earlier I used from debian, today I tried with Sourceforge, but same error
still :(

>
> How does the ptpd-2.3.1 source code relate to the github repo
> https://github.com/ptpd/ptpd ?
>
> I have been referencing the github repo.
>

Yes, that's the repo that we are working with.

Mritunjay

>
> >> ../../ptpd-2.3.1/src/dep/startup.c:948:29: error: 'CPU_LEVEL_WHICH'
> undeclared (first use in this function)
> >>if(cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_PID,
> >>  ^~~
> >> ../../ptpd-2.3.1/src/dep/startup.c:948:46: error: 'CPU_WHICH_PID'
> undeclared (first use in this function)
> >>if(cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_PID,
> >>   ^
> >
> > These are from BSD. This probably needs to be compiled with libbsd
> > somehow? or picking up its header files...
>
> In the github version this code is conditional on sys/cpuset.h being
> present.


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

GSoC 2020: [rtems/rsb]: Error while adding ptp support. This time building for xilinx_zynq_a9_qemu

[Mritunjay Sharma]

Hello everyone,

As suggested by Heinz, I started building for xilinx_zynq_a9_qemu
with a little modification in ptp cfg file.

The netinet is no longer a problem here but another problem has come as
follows:

../../ptpd-2.3.1/src/dep/startup.c: In function 'ptpdStartup':
../../ptpd-2.3.1/src/dep/startup.c:948:29: error: 'CPU_LEVEL_WHICH'
undeclared (first use in this function)
   if(cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_PID,
 ^~~
../../ptpd-2.3.1/src/dep/startup.c:948:46: error: 'CPU_WHICH_PID'
undeclared (first use in this function)
   if(cpuset_setaffinity(CPU_LEVEL_WHICH, CPU_WHICH_PID,
  ^
Makefile:629: recipe for target 'dep/startup.o' failed
make[2]: Leaving directory
'/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-arm-rtems5-1/build-cxc/src'
make[2]: *** [dep/startup.o] Error 1
Makefile:502: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
'/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-arm-rtems5-1/build-cxc'
Makefile:412: recipe for target 'all' failed
make: *** [all] Error 2
shell cmd failed: /bin/sh -ex
 
/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-arm-rtems5-1/do-build
error: building ptpd-2.3.1-arm-rtems5-1
  See error report: rsb-report-ptpd-2.3.1-arm-rtems5-1.txt
Build Set: Time 0:00:21.081476

I am also attaching the log file and trace report.

Thanks,
Mritunjay
RTEMS Tools Project - Source Builder Error Report
 Build: error: building ptpd-2.3.1-arm-rtems5-1
 Command Line: ../source-builder/sb-set-builder --log=log 
--prefix=/home/mritunjay/development/rtems/5 
--with-tools=/home/mritunjay/development/rtems/5 --host=arm-rtems5 
--with-rtems-bsp=xilinx_zynq_a9_qemu net/ptpd
 Python: 2.7.17 (default, Apr 15 2020, 17:20:14) [GCC 7.5.0]
 
git://git.rtems.org/rtems-source-builder.git/origin/855818015a378a8333754625296f3b15ce52aadd-modified
 Linux mritunjay-XPS-15-9570 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 
14:27:18 UTC 2020 x86_64
Tail of the build log:
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gawk... (cached) mawk
checking for arm-rtems5-gcc... arm-rtems5-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether arm-rtems5-gcc accepts -g... yes
checking for arm-rtems5-gcc option to accept ISO C89... none needed
checking whether arm-rtems5-gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of arm-rtems5-gcc... gcc3
checking for arm-rtems5-gcc option to accept ISO C99... none needed
checking build system type... x86_64-unknown-linux-gnu
checking host system type... arm-unknown-rtems5
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by arm-rtems5-gcc... 
/home/mritunjay/development/rtems/5/arm-rtems5/bin/ld
checking if the linker (/home/mritunjay/development/rtems/5/arm-rtems5/bin/ld) 
is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... 
/home/mritunjay/development/rtems/5/bin/arm-rtems5-nm -B
checking the name lister (/home/mritunjay/development/rtems/5/bin/arm-rtems5-nm 
-B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to 
arm-unknown-rtems5 format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain 
format... func_convert_file_noop
checking for /home/mritunjay/development/rtems/5/arm-rtems5/bin/ld option to 
reload object files... -r
checking for arm-rtems5-objdump... arm-rtems5-objdump
checking how to recognize dependent libraries... unknown
checking for arm-rtems5-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for arm-rtems5-ar... arm-rtems5-ar
checking for archiver @FILE support... @
checking for arm-rtems5-strip... (cached) arm-rtems5-strip
checking for arm-rtems5-ranlib... arm-rtems5-ranlib
checking command to parse /home/mritunjay/development/rtems/5/bin/arm-rtems5-nm 
-B output from arm-rtems5-gcc object... failed
checking for sysroot... no
checking for arm-rtems5-mt... no
checking for mt... mt
configu

[rtems/rsb]: Error while building and Adding Netinet cfg (dependency of PTP) [GSoC 2020]

[Mritunjay Sharma]

Hello everyone,

As advised I tried adding Netinet package which
is a dependency to add PTP and was causing an error
earlier, I have encountered another error as mentioned below
while testing the build for netinet.

/home/mritunjay/development/rtems/rsb/rtems/build/netinet--sparc-rtems5-1/do-build:
90: cd: can't cd to netinet
shell cmd failed: /bin/sh -ex
 
/home/mritunjay/development/rtems/rsb/rtems/build/netinet--sparc-rtems5-1/do-build
error: building netinet--sparc-rtems5-1
  See error report: rsb-report-netinet--sparc-rtems5-1.txt
Build Set: Time 0:00:00.667194

Attaching trace file as well.

Thanks,
Mritunjay


log
Description: Binary data
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

On Sat, May 23, 2020 at 12:57 AM Vijay Kumar Banerjee 
wrote:

>
>
> On Sat, May 23, 2020, 12:26 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>>
>>
>> On Thu, May 21, 2020 at 1:07 AM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, May 20, 2020 at 1:46 AM Vijay Kumar Banerjee 
>>> wrote:
>>>
>>>> On Wed, May 20, 2020 at 1:27 AM Mritunjay Sharma
>>>>  wrote:
>>>> >
>>>> >> Thanks for the log files. From a quick look, there is one obvious
>>>> >> error, the linker can't find libbsd most probably because it is not
>>>> >> there. So, you need to remove the -lbsd option from ptpd-2-1.cfg file
>>>> >> LIBS value. Another thing to be noted is that there are a few errors
>>>> >> due to failed version checking of the sparc-rtems5-gcc, this can
>>>> >> probably ignored for now if removing the -lbsd option fixes your
>>>> >> issue.
>>>> >>
>>>> > Thank you so much! Removing the lbsd from cfg file resloved the
>>>> earlier
>>>> > compiler issue but now another error is coming up and it is somewhat
>>>> like this:
>>>> >  "Makefile:502: recipe for target 'all-recursive' failed
>>>> > make[1]: Leaving directory
>>>> '/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc'
>>>> > make[1]: *** [all-recursive] Error 1
>>>> > Makefile:412: recipe for target 'all' failed
>>>> > make: *** [all] Error 2
>>>> > shell cmd failed: /bin/sh -ex
>>>> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/do-build
>>>> > error: building ptpd-2.3.1-sparc-rtems5-1"
>>>> >
>>>>
>>>> The error is generally at the end of the log file. In this case, it is:
>>>> ```
>>>>
>>>> In file included from ../../ptpd-2.3.1/src/arith.c:53:0:
>>>> ../../ptpd-2.3.1/src/ptpd.h:93:10: fatal error: netinet/ip.h: No such
>>>> file or directory
>>>>  #include 
>>>>   ^~
>>>> compilation terminated.
>>>> ```
>>>> This header file isn't there in the include directory. Is netinet a
>>>> dependency fo ptpd? If so, you'll have to find the package that
>>>> provides netinet, and add that to rsb in a similar manner as in ptpd,
>>>> then you'll have to add it in the ptpd.bset .
>>>>
>>>
>> Hi, I am attaching netinet/ip.h file, do we need to add entire netinet
>> package as ptpd?
>>
> We can't just pull one file and add it to rsb, this will make it almost
> impossible to track with the upstream. It would be better to add the whole
> package. Did you find the official source?
>
> To add the package, we need to add a separate set of cfg for netinet and
> then add a reference in the ptpd cfg so that it builds before ptpd. qemu or
> qemu-couverture can be examples of how to add a github repository to rsb
> and build it. Please have a look at them and feel free to ask if you don't
> understand something (maybe in a separate thread :) )
>
> Also, please post the source of the package that you want to add, so that
> there's no objection with the source later.
>
>
> Chris commented about possible errors in the script, you might have to
> follow up with him to fix the issue so that you don't face any problems
> later.
>
> Best regards,
> Vijay
>
> Thank you so much for your help and guidance. I will work out as told and
revert. Sure, I will discuss once I am done adding netinet

Thanks
Mritunjay

> Or there's way to add just this file. I have tried finding netinet tar
>> package but have to satisfy myself with
>> just a github repo? Can it be added as source in cfg file?
>>
>> Thanks,
>> Mritunjay
>>
>>>
>>> I have tried in this course. Have to still execute. Chris is telling
>>> there is a problem with Canadian Cross
>>> Compiling this. Is it allowed here to implement?
>>>
>>>>
>>>> > Attaching the log file as well.
>>>> > - Mritunjay
>>>>
>>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

On Thu, May 21, 2020 at 1:07 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

>
>
> On Wed, May 20, 2020 at 1:46 AM Vijay Kumar Banerjee 
> wrote:
>
>> On Wed, May 20, 2020 at 1:27 AM Mritunjay Sharma
>>  wrote:
>> >
>> >> Thanks for the log files. From a quick look, there is one obvious
>> >> error, the linker can't find libbsd most probably because it is not
>> >> there. So, you need to remove the -lbsd option from ptpd-2-1.cfg file
>> >> LIBS value. Another thing to be noted is that there are a few errors
>> >> due to failed version checking of the sparc-rtems5-gcc, this can
>> >> probably ignored for now if removing the -lbsd option fixes your
>> >> issue.
>> >>
>> > Thank you so much! Removing the lbsd from cfg file resloved the earlier
>> > compiler issue but now another error is coming up and it is somewhat
>> like this:
>> >  "Makefile:502: recipe for target 'all-recursive' failed
>> > make[1]: Leaving directory
>> '/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc'
>> > make[1]: *** [all-recursive] Error 1
>> > Makefile:412: recipe for target 'all' failed
>> > make: *** [all] Error 2
>> > shell cmd failed: /bin/sh -ex
>> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/do-build
>> > error: building ptpd-2.3.1-sparc-rtems5-1"
>> >
>>
>> The error is generally at the end of the log file. In this case, it is:
>> ```
>>
>> In file included from ../../ptpd-2.3.1/src/arith.c:53:0:
>> ../../ptpd-2.3.1/src/ptpd.h:93:10: fatal error: netinet/ip.h: No such
>> file or directory
>>  #include 
>>   ^~
>> compilation terminated.
>> ```
>> This header file isn't there in the include directory. Is netinet a
>> dependency fo ptpd? If so, you'll have to find the package that
>> provides netinet, and add that to rsb in a similar manner as in ptpd,
>> then you'll have to add it in the ptpd.bset .
>>
>
Hi, I am attaching netinet/ip.h file, do we need to add entire netinet
package as ptpd?
Or there's way to add just this file. I have tried finding netinet tar
package but have to satisfy myself with
just a github repo? Can it be added as source in cfg file?

Thanks,
Mritunjay

>
> I have tried in this course. Have to still execute. Chris is telling there
> is a problem with Canadian Cross
> Compiling this. Is it allowed here to implement?
>
>>
>> > Attaching the log file as well.
>> > - Mritunjay
>>
>
/*-
 * Copyright (c) 1982, 1986, 1990, 1993
 *	The Regents of the University of California.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 * 4. Neither the name of the University nor the names of its contributors
 *may be used to endorse or promote products derived from this software
 *without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 *	@(#)in.h	8.3 (Berkeley) 1/3/94
 * $FreeBSD$
 */

#ifndef _NETINET_IN_H_
#define	_NETINET_IN_H_

#include 
#include 
#include 

/* Protocols common to RFC 1700, POSIX, and X/Open. */
#define	IPPROTO_IP		0		/* dummy for IP */
#define	IPPROTO_ICMP		1		/* control message protocol */
#define	IPPROTO_TCP		6		/* tcp */
#define	IPPROTO_UDP		17		/* user datagram protocol */

#define	INADDR_ANY		(u_int32_t)0x
#define	INADDR_BROADCAST	(u_int32_t)0x	/* must be masked *

Re: [rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

On Wed, May 20, 2020 at 1:46 AM Vijay Kumar Banerjee 
wrote:

> On Wed, May 20, 2020 at 1:27 AM Mritunjay Sharma
>  wrote:
> >
> >> Thanks for the log files. From a quick look, there is one obvious
> >> error, the linker can't find libbsd most probably because it is not
> >> there. So, you need to remove the -lbsd option from ptpd-2-1.cfg file
> >> LIBS value. Another thing to be noted is that there are a few errors
> >> due to failed version checking of the sparc-rtems5-gcc, this can
> >> probably ignored for now if removing the -lbsd option fixes your
> >> issue.
> >>
> > Thank you so much! Removing the lbsd from cfg file resloved the earlier
> > compiler issue but now another error is coming up and it is somewhat
> like this:
> >  "Makefile:502: recipe for target 'all-recursive' failed
> > make[1]: Leaving directory
> '/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc'
> > make[1]: *** [all-recursive] Error 1
> > Makefile:412: recipe for target 'all' failed
> > make: *** [all] Error 2
> > shell cmd failed: /bin/sh -ex
> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/do-build
> > error: building ptpd-2.3.1-sparc-rtems5-1"
> >
>
> The error is generally at the end of the log file. In this case, it is:
> ```
>
> In file included from ../../ptpd-2.3.1/src/arith.c:53:0:
> ../../ptpd-2.3.1/src/ptpd.h:93:10: fatal error: netinet/ip.h: No such
> file or directory
>  #include 
>   ^~
> compilation terminated.
> ```
> This header file isn't there in the include directory. Is netinet a
> dependency fo ptpd? If so, you'll have to find the package that
> provides netinet, and add that to rsb in a similar manner as in ptpd,
> then you'll have to add it in the ptpd.bset .
>

I have tried in this course. Have to still execute. Chris is telling there
is a problem with Canadian Cross
Compiling this. Is it allowed here to implement?

>
> > Attaching the log file as well.
> > - Mritunjay
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

On Wed, May 20, 2020 at 5:42 AM Chris Johns  wrote:

> On 20/5/20 5:57 am, Mritunjay Sharma wrote:
> > On Wed, May 20, 2020 at 1:15 AM Vijay Kumar Banerjee  > <mailto:vi...@rtems.org>> wrote:
> >
> > On Wed, May 20, 2020 at 12:52 AM Mritunjay Sharma
> > mailto:mritunjaysharma...@gmail.com>>
> > wrote:
> >  >
> >  >
> >  >
> >  > On Tue, May 19, 2020 at 10:09 PM Vijay Kumar Banerjee
> > mailto:vi...@rtems.org>> wrote:
> >  >>
> >  >> On Tue, May 19, 2020 at 7:42 PM Mritunjay Sharma
> >  >>  > <mailto:mritunjaysharma...@gmail.com>> wrote:
> >  >> >
> >  >> > Hello everyone,
> >  >> >
> >  >> > Starting this thread to discuss and give a detail of my
> > progress in relation to
> >  >> > my GSoC 2020 project "BSP Buildset for EPICS".
> >  >> >
> >  >> > It is to tell that I have worked on adding ptp2 support as
> > suggested by mentors
> >  >> > The implementation that I found could work was ptp2 daemon and
> > so worked with
> >  >> > it.
> >  >> >
> >  >> > I added these files:
> >  >> > rsb/rtems/config/net/ptpd-2.3-1.cfg
> >  >> > rsb/rtems/config/net/ptpd.bset
> >  >> > rsb/source-builder/config/ptpd-2.1.cfg
> >  >> >
> >  >> > I am attaching the .diff file and the bug that I have
> > encountered in the
> >  >> > respective txt file and will like the help of mentors in
> > trying to help me
> >  >> > fix it.
>
> I am seeing in the RSB log this ...
>
> + pwd
> +
>
> build_top=/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1
> + test x86_64-linux-gnu != sparc-rtems5
> + test -z  -o sparc-rtems5 ==
> /home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/do-build:
>
> 102: test: sparc-rtems5: unexpected operator
>
> Is there a shell script error here?
>
> It is not clear to me why this error did not stop the build?
>
> Please add --trace to the RSB command line. It does create lots of
> output but it does help debug these things.
>

Have added and attached. Please have a look. Thanks
-Mritunjay


> >  >> >
> >  >> Hi Mritrynjay,
> >  >>
> >  >> The error your are facing is here:
> >  >> ```
> >  >> checking whether the C compiler works... no
> >  >> configure: error: in
> >  >>
> >
>  
> `/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc':
> >  >> configure: error: C compiler cannot create executables
> >  >> ```
> >  >> Looks like it's not able to find the CC properly. If I remember
> >  >> correctly, you had a similar problem before. Do you remember how
> you
> >  >> fixed that or what was missing?
> >  >>
> >  > Thank you so much for the help, Vijay. However, the thing that
> > was working last time is not
> >  > helping me this time. I am attaching the config.log as well. Hope
> > it will help with debugging.
> >
> > Thanks for the log files. From a quick look, there is one obvious
> > error, the linker can't find libbsd most probably because it is not
> > there. So, you need to remove the -lbsd option from ptpd-2-1.cfg file
> > LIBS value. Another thing to be noted is that there are a few errors
> > due to failed version checking of the sparc-rtems5-gcc, this can
> > probably ignored for now if removing the -lbsd option fixes your
> > issue.
> >
> > Thank you so much! Removing the lbsd from cfg file resloved the earlier
> > compiler issue but now another error is coming up and it is somewhat
> > like this:
> >   "Makefile:502: recipe for target 'all-recursive' failed
> > make[1]: Leaving directory
> >
> '/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc'
>
> This looks like a Canadian Cross compile and this does not seem right.
> It may be related to the shell script error above.
>
> Chris
>
RTEMS Tools Project - Source Builder Error Report
 Build: error: building ptpd-2.3.1-sparc-rtems5-1
 Command Line: ../source-builder/sb-set-builder --log=log_sis_net_snmp 
--prefix=/home/m

Re: [rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

On Tue, May 19, 2020 at 10:09 PM Vijay Kumar Banerjee 
wrote:

> On Tue, May 19, 2020 at 7:42 PM Mritunjay Sharma
>  wrote:
> >
> > Hello everyone,
> >
> > Starting this thread to discuss and give a detail of my progress in
> relation to
> > my GSoC 2020 project "BSP Buildset for EPICS".
> >
> > It is to tell that I have worked on adding ptp2 support as suggested by
> mentors
> > The implementation that I found could work was ptp2 daemon and so worked
> with
> > it.
> >
> > I added these files:
> > rsb/rtems/config/net/ptpd-2.3-1.cfg
> > rsb/rtems/config/net/ptpd.bset
> > rsb/source-builder/config/ptpd-2.1.cfg
> >
> > I am attaching the .diff file and the bug that I have encountered in the
> > respective txt file and will like the help of mentors in trying to help
> me
> > fix it.
> >
> Hi Mritrynjay,
>
> The error your are facing is here:
> ```
> checking whether the C compiler works... no
> configure: error: in
>
> `/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1/build-cxc':
> configure: error: C compiler cannot create executables
> ```
> Looks like it's not able to find the CC properly. If I remember
> correctly, you had a similar problem before. Do you remember how you
> fixed that or what was missing?
>
> Thank you so much for the help, Vijay. However, the thing that was working
last time is not
helping me this time. I am attaching the config.log as well. Hope it will
help with debugging.

>
> Also, there's another warning in the log:
>
> configure: WARNING: unrecognized options: --disable-embedded-perl,
> --without-openssl
>
> You can just remove these options from the cfg file.
>

Thank you so much, I have removed them now and will update on the GitHub as
well.

- Mritunjay

>
> Best regards,
> Vijay
>
> > I will also be uploading the files on my GitHub repo as well which can
> be accessed from here:
> > https://github.com/mritunjaysharma394/rtems-source-builder
> >
> > Thanks,
> > Mritunjay
> >
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
>
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by ptpd configure 2.3.1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ../ptpd-2.3.1/configure --host=sparc-rtems5 --prefix=/home/mritunjay/development/rtems/5 --bindir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/bin --exec_prefix=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32 --includedir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/lib/include --libdir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/lib --libexecdir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/libexec --mandir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/share/man --infodir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/share/info --datadir=/home/mritunjay/development/rtems/5/sparc-rtems5/erc32/share --disable-shared --without-openssl --disable-statistics --enable-slave-only --disable-posix-timers --with-max-unicast-destinations=[16...2048] --enable-experimental-options

## - ##
## Platform. ##
## - ##

hostname = mritunjay-XPS-15-9570
uname -m = x86_64
uname -r = 5.3.0-51-generic
uname -s = Linux
uname -v = #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /home/mritunjay/development/rtems/5/bin
PATH: /home/mritunjay/development/rtems/rsb/source-builder
PATH: /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-cxc/net/ptpd/home/mritunjay/development/rtems/5/bin
PATH: /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000/net/ptpd/home/mritunjay/development/rtems/5/bin
PATH: /home/mritunjay/.local/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games
PATH: /snap/bin


## --- ##
## Core tests. ##
## --- ##

configure:2627: checking for a BSD-compatible install
configure:2695: result: /usr/bin/install -c
configure:2706: checking whether build environment is sane
configure:2761: result: yes
configure:2820: checking for sparc-rtems5-strip
configure:2836: found /home/mritunjay/development/rtems/5/bin/sparc-rtems5-strip
configure:2847: result: sparc-rtems5-strip
configure:2912: checking for a thread-safe 

[rtems/rsb]: Adding PTP support to RSB [GSoC 2020]

[Mritunjay Sharma]

Hello everyone,

Starting this thread to discuss and give a detail of my progress in
relation to
my GSoC 2020 project "BSP Buildset for EPICS".

It is to tell that I have worked on adding ptp2 support as suggested by
mentors
The implementation that I found could work was ptp2 daemon and so worked
with
it.

I added these files:
rsb/rtems/config/net/ptpd-2.3-1.cfg
rsb/rtems/config/net/ptpd.bset
rsb/source-builder/config/ptpd-2.1.cfg

I am attaching the .diff file and the bug that I have encountered in the
respective txt file and will like the help of mentors in trying to help me
fix it.

I will also be uploading the files on my GitHub repo as well which can be
accessed from here:
https://github.com/mritunjaysharma394/rtems-source-builder

Thanks,
Mritunjay
RTEMS Tools Project - Source Builder Error Report
 Build: error: building ptpd-2.3.1-sparc-rtems5-1
 Command Line: ../source-builder/sb-set-builder --log=log_sis_net_snmp 
--prefix=/home/mritunjay/development/rtems/5 
--with-tools=/home/mritunjay/development/rtems/5 --host=sparc-rtems5 
--with-rtems-bsp=erc32 net/ptpd
 Python: 2.7.17 (default, Apr 15 2020, 17:20:14) [GCC 7.5.0]
 
git://git.rtems.org/rtems-source-builder.git/origin/96cdedce58e32f07c174966676e8b7e8c6620634
 Linux mritunjay-XPS-15-9570 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 
14:27:18 UTC 2020 x86_64
Tail of the build log:
script: 21: SB_CFLAGS="${SB_BUILD_CFLAGS} "
script: 22: SB_CXXFLAGS="${SB_BUILD_CXXFLAGS} "
script: 23: SB_ARCH="sparc"
script: 24: SB_OS="linux"
script: 25: export SB_SOURCE_DIR SB_BUILD_DIR SB_ARCH SB_OS
script: 26: export SB_HOST_CPPFLAGS SB_HOST_CFLAGS SB_HOST_CXXFLAGS 
SB_HOST_LDFLAGS SB_HOST_LIBS
script: 27: export SB_BUILD_CFLAGS SB_BUILD_CXXFLAGS SB_BUILD_LDFLAGS 
SB_BUILD_LIBS
script: 28: export SB_CFLAGS SB_CXXFLAGS
script: 29: # Documentation
script: 30: SB_DOC_DIR="/home/mritunjay/development/rtems/5/share/doc"
script: 31: export SB_DOC_DIR
script: 32: # Packages
script: 33: SB_PACKAGE_NAME="ptpd-2.3.1-sparc-rtems5-1"
script: 34: SB_PACKAGE_BUILDNAME="ptpd-2.3.1-sparc-rtems5-1"
script: 35: SB_PACKAGE_VERSION="2.3.1"
script: 36: SB_PACKAGE_RELEASE="1"
script: 37: export SB_PACKAGE_NAME SB_PACKAGE_VERSION SB_PACKAGE_RELEASE
script: 38: # Build directories
script: 39: export SB_PREFIX
script: 40: 
SB_BUILD_DIR="/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1"
script: 41: 
SB_BUILD_ROOT="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/ptpd-2.3.1-sparc-rtems5-1-1000"
script: 42: 
SB_BUILD_ROOT_BINDIR="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/ptpd-2.3.1-sparc-rtems5-1-1000/${SB_PREFIX_CLEAN}/bin"
script: 43: export SB_BUILD_ROOT SB_BUILD_DIR SB_BUILD_ROOT_BINDIR
script: 44: 
SB_BUILD_CXC_DIR="/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1-cxc"
script: 45: 
SB_BUILD_CXC_ROOT="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/ptpd-2.3.1-sparc-rtems5-1-1000-cxc"
script: 46: 
SB_BUILD_CXC_ROOT_BINDIR="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/ptpd-2.3.1-sparc-rtems5-1-1000-cxc/${SB_PREFIX_CLEAN}/bin"
script: 47: export SB_BUILD_CXC_ROOT SB_BUILD_CXC_DIR SB_BUILD_CXC_ROOT_BINDIR
script: 48: 
SB_TMPROOT="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000/net/ptpd"
script: 49: 
SB_TMPPREFIX="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000/net/ptpd/${SB_PREFIX_CLEAN}"
script: 50: 
SB_TMPBINDIR="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000/net/ptpd/${SB_PREFIX_CLEAN}/bin"
script: 51: export SB_TMPROOT SB_TMPPREFIX SB_TMPBINDIR
script: 52: 
SB_TMPCXCROOT="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000/net/ptpd"
script: 53: 
SB_TMPCXCPREFIX="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-cxc/net/ptpd/${SB_PREFIX_CLEAN}"
script: 54: 
SB_TMPCXCBINDIR="/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-cxc/net/ptpd/${SB_PREFIX_CLEAN}/bin"
script: 55: export SB_TMPCXCROOT SB_TMPCXCPREFIX SB_TMPCXCBINDIR
script: 56: # Extra path support
script: 57: SB_EXTRAPATH="/home/mritunjay/development/rtems/rsb/source-builder"
script: 58: # The compiler flags
script: 59: 
script: 60: 
script: 61: export CFLAGS_FOR_TARGET
script: 62: export CXXFLAGS_FOR_TARGET
script: 63: # Set up the path. Put the CXC path first.
script: 64: if test -n "${SB_TMPBINDIR}" ; then
script: 65:  PATH="${SB_TMPBINDIR}:$PATH"
script: 66: fi
script: 67: if test -n "${SB_TMPCXCBINDIR}" ; then
script: 68:  PATH="${SB_TMPCXCBINDIR}:$PATH"
script: 69: fi
script: 70: if test -n "${SB_EXTRAPATH}" ; then
script: 71:  PATH="${SB_EXTRAPATH}:$PATH"
script: 72: fi
script: 73: PATH="/home/mritunjay/development/rtems/5/bin:$PATH"
script: 74: 
script: 75: export PATH
script: 76: # Default environment set up.
script: 77: LANG=C
script: 78: export LANG
script: 79: unset DISPLAY || :
script: 80: umask 022
script: 81: cd 
"/home/mritunjay/development/rtems/rsb/rtems/build/ptpd-2.3.1-sparc-rtems5-1"
script: 82: echo "=> ptpd-2.3.1-sparc-rtems5-1: CLEAN"
scr

Re: source builder, bsp arch settings

[Mritunjay Sharma]

Hello everyone!

Apologies for breaking the chain of this conversation.
I have also been working (read struggling) on adding libbsd and ntp support
for RTEMS+EPICS on xilinx_zynq_a9_qemu and trying
to figure out what files in /rtems/rtems-libbsd and
/rtems/rsb/source-builder/, I have to begin with.

In the rtems/rtems-libbsd, I am attempting to change libbsd.py file,
While in rtems/rsb/source-builder/, I have worked on ntp-4-1.cfg.

However, I will really appreciate if this beginner can get some useful
resources or past works to get on the right track to progress ahead.

Thank you so much!

On Thu, Apr 30, 2020 at 3:49 PM Heinz Junkes 
wrote:

> Hello, Chris,
> thanks for testing it right away. It was a stupid mistake on my part, of
> course.
>
> To get around the build error I had to define macros in the build-script.
> “-DHAVE_MKTIME -DHAVE_TIMEGM”
>
> Unfortunately, configure --extra-cflags does not work as expected
> So I set CFLAGS before the call to configure and forgot to append the
> existing flags ${CFLAGS} :-(
>
> Heinz
>
>
> > On 30. Apr 2020, at 01:33, Chris Johns  wrote:
> >
> > On 29/4/20 8:03 pm, Heinz Junkes wrote:
> >> unfortunately i can't really get along with the
> source-builder/sb-set-builder.
> >
> > Can you build the package by manually? This is the recommended first
> step. The RSB is just a means to capture those manual steps.
> >
> >> For example, I want to build ntp for xilinx_zynq_a9_qemu using the
> command line:
> >> (in rtems-source-builder-5.0.0-m2003/rtems)
> >
> > This is a snapshot release which means it can break. While we try as
> best we can there is no guarantee a release snapshot will work. Having said
> that I am pleased you are testing it and reporting problems.
> >
> >> ../source-builder/sb-set-builder —log=log_ntp_arm.txt
> —prefix=/home/h1/GSOC/RTEMS/5.0.0-m2003 \
> >> —host=arm=rtems5 —with-rtems-bsp=xilinx_zynq_a9_qemu net/ntp
> >
> > I have attempted to build net/ntp for the same BSP from the RSB master
> and I am seeing this following error:
> >
> > ../../ntp-4.2.6p5/libntp/mktime.c:67:2: error:
> > #error libntp supplied mktime()/timegm() do not support 64-bit time_t
> >
> > Do you have something else you are building?
> >
> >> I have assumed that the compiler flags for xilinx_zynq_a9_qemu are
> taken over by the specification for which BSP
> >> I want to build this.
> >> E.g. “-march-armv7-a”
> >
> > Do you mean "-march=armv7-a"?
> >
> >> Unfortunately, the compilation of ntp does not work, because __ARM_ARCH
> is not set to “7"
> >> but remains defined at the default value of "4”.
> >> Because of the missing CFLAGS for the  xilinx_zynq_a9_qemu architecture?
> >
> > Are you saying the compile command line flags do not have the correct
> `-march=armv7-a` option?
> >
> > The build I just did that failed has the correct set of machine flags
> for a Zynq (Cortex-A9):
> >
> > -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard -mtune=cortex-a9
> >
> > And this gives me:
> >
> > $ arm-rtems5-gcc -dM -E -march=armv7-a -mthumb -mfpu=neon \
> >   -mfloat-abi=hard -mtune=cortex-a9 - < /dev/null | grep '__ARM_ARCH '
> > #define __ARM_ARCH 7
> >
> > Chris
>
> ___
> users mailing list
> us...@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Build Error while setting up RTEMS ARM BSP xilinx_zynq for qemu

[Mritunjay Sharma]

Yes, thank you so much! Will keep it in mind from now on.

On Tue, Apr 28, 2020 at 2:11 AM Vijay Kumar Banerjee 
wrote:

>
>
> On Tue, Apr 28, 2020 at 2:03 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >
> > Update: It is working now.
> >
> Great! Looks like the error was a basic one ( C Compiler was absent.).
> Most of the
> time going to the log files give a good insight of the issue.
> > Thank you so much!
> >
> > On Tue, Apr 28, 2020 at 1:54 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>
> >> Thank you so much Vijay,
> >>
> >> I am attaching the txt file as well as looking into it to find the
> error and
> >> solution. Thanks for the help!
> >>
> >> Regards,
> >> Mritunjay
> >>
> >> On Tue, Apr 28, 2020 at 1:50 AM Vijay Kumar Banerjee 
> wrote:
> >>>
> >>>
> >>>
> >>> On Tue, Apr 28, 2020, 1:45 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
> >>>>
> >>>> Hello everyone,
> >>>>
> >>>> This in reference to Ticket #3855 and my proposal for GSoC.
> >>>> As I have already cross-compiled and built EPICS7
> >>>> with RTEMS-5 for mvme6100, now I was trying to do the
> >>>> same for qemu/xilinx_zynq.
> >>>>
> >>>> However, while building with the below command:
> >>>> '''../source-builder/sb-set-builder
> --prefix=/home/mritunjay/development/rtems/5 \
> >>>> --host=arm-rtems5 --with-rtems-bsp=xilinx_zynq_a9_qemu 5/rtems-arm'''
> >>>>
> >>>> I encountered this error:
> >>>> '''RTEMS Source Builder - Set Builder, 5 (96cdedce58e3)
> >>>> Build Set: 5/rtems-arm
> >>>> Build Set: 5/rtems-autotools.bset
> >>>> Build Set: 5/rtems-autotools-internal.bset
> >>>> config: tools/rtems-autoconf-2.69-1.cfg
> >>>> package: autoconf-2.69-arm-rtems5-1
> >>>> building: autoconf-2.69-arm-rtems5-1
> >>>> sizes: autoconf-2.69-arm-rtems5-1: 7.501MB (installed: 0.000B)
> >>>> cleaning: autoconf-2.69-arm-rtems5-1
> >>>> config: tools/rtems-automake-1.12.6-1.cfg
> >>>> package: automake-1.12.6-arm-rtems5-1
> >>>> building: automake-1.12.6-arm-rtems5-1
> >>>> sizes: automake-1.12.6-arm-rtems5-1: 8.085MB (installed: 0.000B)
> >>>> cleaning: automake-1.12.6-arm-rtems5-1
> >>>> cleaning: autoconf-2.69-arm-rtems5-1
> >>>> cleaning: automake-1.12.6-arm-rtems5-1
> >>>> Build Sizes: usage: 8.085MB total: 144.775MB (sources: 144.756MB,
> patches: 19.412KB, installed 0.000B)
> >>>> Build Set: Time 0:00:10.271869
> >>>> Build Set: 5/rtems-autotools-base.bset
> >>>> config: tools/rtems-autoconf-2.69-1.cfg
> >>>> package: autoconf-2.69-arm-rtems5-1
> >>>> building: autoconf-2.69-arm-rtems5-1
> >>>> sizes: autoconf-2.69-arm-rtems5-1: 10.532MB (installed: 3.034MB)
> >>>> cleaning: autoconf-2.69-arm-rtems5-1
> >>>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
> autoconf-2.69-arm-rtems5-1.txt
> >>>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
> autoconf-2.69-arm-rtems5-1.xml
> >>>> config: tools/rtems-automake-1.12.6-1.cfg
> >>>> package: automake-1.12.6-arm-rtems5-1
> >>>> building: automake-1.12.6-arm-rtems5-1
> >>>> sizes: automake-1.12.6-arm-rtems5-1: 10.348MB (installed: 2.265MB)
> >>>> cleaning: automake-1.12.6-arm-rtems5-1
> >>>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
> automake-1.12.6-arm-rtems5-1.txt
> >>>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
> automake-1.12.6-arm-rtems5-1.xml
> >>>> staging: autoconf-2.69-arm-rtems5-1 ->
> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
> >>>> staging: automake-1.12.6-arm-rtems5-1 ->
> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
> >>>> cleaning: autoconf-2.69-arm-rtems5-1
> >>>> cleaning: automake-1.12.6-arm-rtems5-1
> >>>> Build Sizes: usage: 15.830MB total: 150.073MB (sources: 144.756MB,
> patches: 19.412KB, installed 5.298MB)
> >>>> Build Set: Time 0:00:13.777473
> >>>> Build Set: Time 0:00:24.056142
> >>>> config: devel/expat-2.1.0-1.cfg
> >>>> package: expat-2.1.0-arm-rtems5-1
> >>>> building: expat-2.1.0-arm-rtems5-1
> >>>> error: building expat-2.1.0-arm-rtems5-1
> >>>> Build FAILED
> >>>>   See error report: rsb-report-expat-2.1.0-arm-rtems5-1.txt
> >>>
> >>> Hi Mritunjay,
> >>>
> >>>
> >>> Please see in this txt file, the error is visible there. You can
> attach this file in the mail and send so we can see it and try to figure
> out a solution
> >>>
> >>>
> >>> Best regards,
> >>> Vijay
> >>>
> >>>
> >>>> error: building expat-2.1.0-arm-rtems5-1
> >>>> Build Set: Time 0:00:24.851451
> >>>> Build FAILED
> >>>> '''
> >>>>
> >>>> Please help me if any configuration changes have to be made,
> >>>>
> >>>> Thanks
> >>>> Mritunjay
> >>>> ___
> >>>> 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: Build Error while setting up RTEMS ARM BSP xilinx_zynq for qemu

[Mritunjay Sharma]

Update: It is working now.

Thank you so much!

On Tue, Apr 28, 2020 at 1:54 AM Mritunjay Sharma <
mritunjaysharma...@gmail.com> wrote:

> Thank you so much Vijay,
>
> I am attaching the txt file as well as looking into it to find the error
> and
> solution. Thanks for the help!
>
> Regards,
> Mritunjay
>
> On Tue, Apr 28, 2020 at 1:50 AM Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>> On Tue, Apr 28, 2020, 1:45 AM Mritunjay Sharma <
>> mritunjaysharma...@gmail.com> wrote:
>>
>>> Hello everyone,
>>>
>>> This in reference to Ticket #3855 and my proposal for GSoC.
>>> As I have already cross-compiled and built EPICS7
>>> with RTEMS-5 for mvme6100, now I was trying to do the
>>> same for qemu/xilinx_zynq.
>>>
>>> However, while building with the below command:
>>> '''../source-builder/sb-set-builder
>>> --prefix=/home/mritunjay/development/rtems/5 \
>>> --host=arm-rtems5 --with-rtems-bsp=xilinx_zynq_a9_qemu 5/rtems-arm'''
>>>
>>> I encountered this error:
>>> '''RTEMS Source Builder - Set Builder, 5 (96cdedce58e3)
>>> Build Set: 5/rtems-arm
>>> Build Set: 5/rtems-autotools.bset
>>> Build Set: 5/rtems-autotools-internal.bset
>>> config: tools/rtems-autoconf-2.69-1.cfg
>>> package: autoconf-2.69-arm-rtems5-1
>>> building: autoconf-2.69-arm-rtems5-1
>>> sizes: autoconf-2.69-arm-rtems5-1: 7.501MB (installed: 0.000B)
>>> cleaning: autoconf-2.69-arm-rtems5-1
>>> config: tools/rtems-automake-1.12.6-1.cfg
>>> package: automake-1.12.6-arm-rtems5-1
>>> building: automake-1.12.6-arm-rtems5-1
>>> sizes: automake-1.12.6-arm-rtems5-1: 8.085MB (installed: 0.000B)
>>> cleaning: automake-1.12.6-arm-rtems5-1
>>> cleaning: autoconf-2.69-arm-rtems5-1
>>> cleaning: automake-1.12.6-arm-rtems5-1
>>> Build Sizes: usage: 8.085MB total: 144.775MB (sources: 144.756MB,
>>> patches: 19.412KB, installed 0.000B)
>>> Build Set: Time 0:00:10.271869
>>> Build Set: 5/rtems-autotools-base.bset
>>> config: tools/rtems-autoconf-2.69-1.cfg
>>> package: autoconf-2.69-arm-rtems5-1
>>> building: autoconf-2.69-arm-rtems5-1
>>> sizes: autoconf-2.69-arm-rtems5-1: 10.532MB (installed: 3.034MB)
>>> cleaning: autoconf-2.69-arm-rtems5-1
>>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
>>> autoconf-2.69-arm-rtems5-1.txt
>>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
>>> autoconf-2.69-arm-rtems5-1.xml
>>> config: tools/rtems-automake-1.12.6-1.cfg
>>> package: automake-1.12.6-arm-rtems5-1
>>> building: automake-1.12.6-arm-rtems5-1
>>> sizes: automake-1.12.6-arm-rtems5-1: 10.348MB (installed: 2.265MB)
>>> cleaning: automake-1.12.6-arm-rtems5-1
>>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
>>> automake-1.12.6-arm-rtems5-1.txt
>>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
>>> automake-1.12.6-arm-rtems5-1.xml
>>> staging: autoconf-2.69-arm-rtems5-1 ->
>>> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
>>> staging: automake-1.12.6-arm-rtems5-1 ->
>>> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
>>> cleaning: autoconf-2.69-arm-rtems5-1
>>> cleaning: automake-1.12.6-arm-rtems5-1
>>> Build Sizes: usage: 15.830MB total: 150.073MB (sources: 144.756MB,
>>> patches: 19.412KB, installed 5.298MB)
>>> Build Set: Time 0:00:13.777473
>>> Build Set: Time 0:00:24.056142
>>> config: devel/expat-2.1.0-1.cfg
>>> package: expat-2.1.0-arm-rtems5-1
>>> building: expat-2.1.0-arm-rtems5-1
>>> error: building expat-2.1.0-arm-rtems5-1
>>> Build FAILED
>>>   See error report: rsb-report-expat-2.1.0-arm-rtems5-1.txt
>>>
>> Hi Mritunjay,
>>
>>
>> Please see in this txt file, the error is visible there. You can attach
>> this file in the mail and send so we can see it and try to figure out a
>> solution
>>
>>
>> Best regards,
>> Vijay
>>
>>
>> error: building expat-2.1.0-arm-rtems5-1
>>> Build Set: Time 0:00:24.851451
>>> Build FAILED
>>> '''
>>>
>>> Please help me if any configuration changes have to be made,
>>>
>>> Thanks
>>> Mritunjay
>>> ___
>>> 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: Build Error while setting up RTEMS ARM BSP xilinx_zynq for qemu

[Mritunjay Sharma]

Thank you so much Vijay,

I am attaching the txt file as well as looking into it to find the error and
solution. Thanks for the help!

Regards,
Mritunjay

On Tue, Apr 28, 2020 at 1:50 AM Vijay Kumar Banerjee 
wrote:

>
>
> On Tue, Apr 28, 2020, 1:45 AM Mritunjay Sharma <
> mritunjaysharma...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> This in reference to Ticket #3855 and my proposal for GSoC.
>> As I have already cross-compiled and built EPICS7
>> with RTEMS-5 for mvme6100, now I was trying to do the
>> same for qemu/xilinx_zynq.
>>
>> However, while building with the below command:
>> '''../source-builder/sb-set-builder
>> --prefix=/home/mritunjay/development/rtems/5 \
>> --host=arm-rtems5 --with-rtems-bsp=xilinx_zynq_a9_qemu 5/rtems-arm'''
>>
>> I encountered this error:
>> '''RTEMS Source Builder - Set Builder, 5 (96cdedce58e3)
>> Build Set: 5/rtems-arm
>> Build Set: 5/rtems-autotools.bset
>> Build Set: 5/rtems-autotools-internal.bset
>> config: tools/rtems-autoconf-2.69-1.cfg
>> package: autoconf-2.69-arm-rtems5-1
>> building: autoconf-2.69-arm-rtems5-1
>> sizes: autoconf-2.69-arm-rtems5-1: 7.501MB (installed: 0.000B)
>> cleaning: autoconf-2.69-arm-rtems5-1
>> config: tools/rtems-automake-1.12.6-1.cfg
>> package: automake-1.12.6-arm-rtems5-1
>> building: automake-1.12.6-arm-rtems5-1
>> sizes: automake-1.12.6-arm-rtems5-1: 8.085MB (installed: 0.000B)
>> cleaning: automake-1.12.6-arm-rtems5-1
>> cleaning: autoconf-2.69-arm-rtems5-1
>> cleaning: automake-1.12.6-arm-rtems5-1
>> Build Sizes: usage: 8.085MB total: 144.775MB (sources: 144.756MB,
>> patches: 19.412KB, installed 0.000B)
>> Build Set: Time 0:00:10.271869
>> Build Set: 5/rtems-autotools-base.bset
>> config: tools/rtems-autoconf-2.69-1.cfg
>> package: autoconf-2.69-arm-rtems5-1
>> building: autoconf-2.69-arm-rtems5-1
>> sizes: autoconf-2.69-arm-rtems5-1: 10.532MB (installed: 3.034MB)
>> cleaning: autoconf-2.69-arm-rtems5-1
>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
>> autoconf-2.69-arm-rtems5-1.txt
>> reporting: tools/rtems-autoconf-2.69-1.cfg ->
>> autoconf-2.69-arm-rtems5-1.xml
>> config: tools/rtems-automake-1.12.6-1.cfg
>> package: automake-1.12.6-arm-rtems5-1
>> building: automake-1.12.6-arm-rtems5-1
>> sizes: automake-1.12.6-arm-rtems5-1: 10.348MB (installed: 2.265MB)
>> cleaning: automake-1.12.6-arm-rtems5-1
>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
>> automake-1.12.6-arm-rtems5-1.txt
>> reporting: tools/rtems-automake-1.12.6-1.cfg ->
>> automake-1.12.6-arm-rtems5-1.xml
>> staging: autoconf-2.69-arm-rtems5-1 ->
>> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
>> staging: automake-1.12.6-arm-rtems5-1 ->
>> /home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
>> cleaning: autoconf-2.69-arm-rtems5-1
>> cleaning: automake-1.12.6-arm-rtems5-1
>> Build Sizes: usage: 15.830MB total: 150.073MB (sources: 144.756MB,
>> patches: 19.412KB, installed 5.298MB)
>> Build Set: Time 0:00:13.777473
>> Build Set: Time 0:00:24.056142
>> config: devel/expat-2.1.0-1.cfg
>> package: expat-2.1.0-arm-rtems5-1
>> building: expat-2.1.0-arm-rtems5-1
>> error: building expat-2.1.0-arm-rtems5-1
>> Build FAILED
>>   See error report: rsb-report-expat-2.1.0-arm-rtems5-1.txt
>>
> Hi Mritunjay,
>
>
> Please see in this txt file, the error is visible there. You can attach
> this file in the mail and send so we can see it and try to figure out a
> solution
>
>
> Best regards,
> Vijay
>
>
> error: building expat-2.1.0-arm-rtems5-1
>> Build Set: Time 0:00:24.851451
>> Build FAILED
>> '''
>>
>> Please help me if any configuration changes have to be made,
>>
>> Thanks
>> Mritunjay
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>
RTEMS Tools Project - Source Builder Error Report
 Build: error: building expat-2.1.0-arm-rtems5-1
 Command Line: ../source-builder/sb-set-builder 
--prefix=/home/mritunjay/development/rtems/5 --host=arm-rtems5 
--with-rtems-bsp=xilinx_zynq_a9_qemu 5/rtems-arm
 Python: 2.7.17 (default, Apr 15 2020, 17:20:14) [GCC 7.5.0]
 
git://git.rtems.org/rtems-source-builder.git/origin/96cdedce58e32f07c174966676e8b7e8c6620634
 Linux mritunjay-XPS-15-9570 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 
04:17:56 UTC 2020 x86_64
Tail of the build log:
script:140: export CC CXX CPPFLAGS CFLAGS CXXFLA

Build Error while setting up RTEMS ARM BSP xilinx_zynq for qemu

[Mritunjay Sharma]

Hello everyone,

This in reference to Ticket #3855 and my proposal for GSoC.
As I have already cross-compiled and built EPICS7
with RTEMS-5 for mvme6100, now I was trying to do the
same for qemu/xilinx_zynq.

However, while building with the below command:
'''../source-builder/sb-set-builder
--prefix=/home/mritunjay/development/rtems/5 \
--host=arm-rtems5 --with-rtems-bsp=xilinx_zynq_a9_qemu 5/rtems-arm'''

I encountered this error:
'''RTEMS Source Builder - Set Builder, 5 (96cdedce58e3)
Build Set: 5/rtems-arm
Build Set: 5/rtems-autotools.bset
Build Set: 5/rtems-autotools-internal.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-arm-rtems5-1
building: autoconf-2.69-arm-rtems5-1
sizes: autoconf-2.69-arm-rtems5-1: 7.501MB (installed: 0.000B)
cleaning: autoconf-2.69-arm-rtems5-1
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-arm-rtems5-1
building: automake-1.12.6-arm-rtems5-1
sizes: automake-1.12.6-arm-rtems5-1: 8.085MB (installed: 0.000B)
cleaning: automake-1.12.6-arm-rtems5-1
cleaning: autoconf-2.69-arm-rtems5-1
cleaning: automake-1.12.6-arm-rtems5-1
Build Sizes: usage: 8.085MB total: 144.775MB (sources: 144.756MB, patches:
19.412KB, installed 0.000B)
Build Set: Time 0:00:10.271869
Build Set: 5/rtems-autotools-base.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-arm-rtems5-1
building: autoconf-2.69-arm-rtems5-1
sizes: autoconf-2.69-arm-rtems5-1: 10.532MB (installed: 3.034MB)
cleaning: autoconf-2.69-arm-rtems5-1
reporting: tools/rtems-autoconf-2.69-1.cfg -> autoconf-2.69-arm-rtems5-1.txt
reporting: tools/rtems-autoconf-2.69-1.cfg -> autoconf-2.69-arm-rtems5-1.xml
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-arm-rtems5-1
building: automake-1.12.6-arm-rtems5-1
sizes: automake-1.12.6-arm-rtems5-1: 10.348MB (installed: 2.265MB)
cleaning: automake-1.12.6-arm-rtems5-1
reporting: tools/rtems-automake-1.12.6-1.cfg ->
automake-1.12.6-arm-rtems5-1.txt
reporting: tools/rtems-automake-1.12.6-1.cfg ->
automake-1.12.6-arm-rtems5-1.xml
staging: autoconf-2.69-arm-rtems5-1 ->
/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
staging: automake-1.12.6-arm-rtems5-1 ->
/home/mritunjay/development/rtems/rsb/rtems/build/tmp/sb-1000-staging
cleaning: autoconf-2.69-arm-rtems5-1
cleaning: automake-1.12.6-arm-rtems5-1
Build Sizes: usage: 15.830MB total: 150.073MB (sources: 144.756MB, patches:
19.412KB, installed 5.298MB)
Build Set: Time 0:00:13.777473
Build Set: Time 0:00:24.056142
config: devel/expat-2.1.0-1.cfg
package: expat-2.1.0-arm-rtems5-1
building: expat-2.1.0-arm-rtems5-1
error: building expat-2.1.0-arm-rtems5-1
Build FAILED
  See error report: rsb-report-expat-2.1.0-arm-rtems5-1.txt
error: building expat-2.1.0-arm-rtems5-1
Build Set: Time 0:00:24.851451
Build FAILED
'''

Please help me if any configuration changes have to be made,

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

Re: [PATCH v2] user/bsps: Moving all other M68K BSPs from Wiki to User Manual

[Mritunjay Sharma]

Hi all,

Hope you all are well. I guess this patch was missed for review.
Requesting you to please provide more feedback as I continue
to work to close #3905.
I built the doc locally and it was working fine.

Thanks
Mritunjay

On Tue, Apr 14, 2020 at 12:39 AM Mritunjay 
wrote:

> Tried to fix the patch as per suggestions. Please review.
> ---
>  user/bsps/bsps-m68k.rst | 1048 ++-
>  1 file changed, 924 insertions(+), 124 deletions(-)
>
> diff --git a/user/bsps/bsps-m68k.rst b/user/bsps/bsps-m68k.rst
> index bdb516b..5ca9079 100644
> --- a/user/bsps/bsps-m68k.rst
> +++ b/user/bsps/bsps-m68k.rst
> @@ -8,7 +8,22 @@ m68k (Motorola 68000 / ColdFire)
>  av5282
>  ==
>
> -TODO.
> +Overview
> +
> +
> +The Freescale ColdFire Evaluation Board provides a reference platform for
> +engineers to develop a variety of embedded processing applications
> requiring
> +networking connectivity. The board hosts all the necessary hardware and
> firmware
> +needed to implement a networked interface using the Freescale MCF5282
> processor.
> +By including all the necessary physical layer (PHY) devices, memory and
> external
> +expansion capability the designer can implement any bridging application
> that
> +requires 10/100 Ethernet, UARTs, CAN interface, QSPI, analog inputs and/or
> +memory-mapped peripherals. The AvBus expansion connector allows for user
> defined
> +add-on hardware, or can be utilized with over 20 compatible evaluation and
> +development boards from Avnet Electronics Marketing. These boards can be
> mixed
> +and matched to provide a variety of additional hardware and firmware
> capability
> +from PCI and PCI-X connectivity, RapidIO, memory and communications and
> +video/audio functions.
>
>  csb360
>  ==
> @@ -18,27 +33,365 @@ TODO.
>  gen68340
>  
>
> -TODO.
> +Overview
> +
> +
> +The MC68340 is a high-performance 32-bit integrated processor with direct
> memory
> +access (DMA), combining an enhanced M68000-compatible processor, 32-bit
> DMA, and
> +other peripheral subsystems on a single integrated circuit. The MC68340
> CPU32
> +delivers 32-bit CISC processor performance from a lower cost 16-bit memory
> +system. The combination of peripherals offered in the MC68340 can be
> found in a
> +diverse range of microprocessor-based systems.Systems requiring very
> high-speed
> +block transfers of data can benefit from the MC68340.
> +
> +Organization
> +
> +
> +The M68300 family of integrated processors and controllers is built on an
> M68000
> +core processor, an on-chip bus, and a selection of intelligent peripherals
> +appropriate for a set of applications. The CPU32 is a powerful central
> +processor with nearly the performance of the MC68020. A system integration
> +module incorporates the external bus interface and many of the smaller
> circuits
> +that typically surround a microprocessor for address decoding, wait-state
> +insertion, interrupt prioritization, clock generation, arbitration,
> watchdog
> +timing, and power-on reset timing. Each member of the M68300 family is
> +distinguished by its selection of peripherals. Peripherals are chosen to
> address
> +specific applications but are often useful in a wide variety of
> applications.
> +The peripherals may be highly sophisticated timing or protocol engines
> that have
> +their own processors, or they may be more traditional peripheral
> functions, such
> +as UARTs and timers. Since each major function is designed in a standalone
> +module, each module might be found in many different M68300 family parts.
> +
> +Architecture
> +
> +
> +The CPU32 is upward source- and object-code compatible with the MC68000
> and
> +MC68010. It is downward source- and object-code compatible with the
> MC68020.
> +Within the M68000 family, architectural differences are limited to the
> +supervisory operating state. User state programs can be executed
> unchanged on
> +upward-compatible devices. The major CPU32 features are as follows:
> +
> +* 32-Bit Internal Data Path and Arithmetic Hardware
> +* 32-Bit Address Bus Supported by 32-Bit Calculations
> +* Rich Instruction Set
> +* Eight 32-Bit General-Purpose Data Registers
> +* Seven 32-Bit General-Purpose Address Registers
> +* Separate User and Supervisor Stack Pointers
> +* Separate User and Supervisor State Address Spaces
> +* Separate Program and Data Address Spaces
> +* Many Data Types
> +* Flexible Addressing Modes
> +* Full Interrupt Processing
> +* Expansion Capability
> +
> +The CPU32 is an M68000 family processor specially designed for use as a
> 32-bit
> +core processor and for operation over the intermodule bus (IMB).
> Designers used
> +the MC68020 as a model and included advances of the later M68000 family
> +processors, resulting in an instruction execution performance of 4 MIPS
> +(VAX-equivalent) at 25.16 MHz. The powerful and flexible M68000
> architecture is
> +the basis of the CPU32. MC68000 (including the MC68