Re: RSB create report error

Hello, the GDB error is: https://sourceware.org/pipermail/gdb/2020-July/048772.html This -fno-common default in GCC 10 can be also an issue for some RTEMS BSPs. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

RSB create report error

Hello, I tried to build the latest RTEMS 6 tools via RSB on Linux, but there was a failure in GDB. Unfortunately, the report generation failed: error: building powerpc-rtems6-gdb-4e394b2-x86_64-linux-gnu-1 Build FAILED error: failure to create error report Build Set: Time 0:01:32.511549

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

e as follows: > > "configure.ac:28: installing './compile' > configure.ac:16: installing './install-sh' > configure.ac:16: installing './missing' > configure.ac:13: error: required file 'config.h.in' not found > src/Makefile.am: installing './depcomp' > shell cmd failed: /bin/sh

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

onfig/ptpd-2-1.cfg -> add the hash line ../source-builder/sb-set-builder --log log.ptpd.txt --with-rtems-bsp=xilinx_zynq_a9_qemu --host=arm-rtems5 --prefix /home/h1/GSOC/RTEMS/5.0.0-m2003 net/ptpd tail -200 rsb-report-ptpd-master-arm-rtems5-1.txt -> now on a real error ;-) the ptpd-2-1.c

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

> -Original Message- > From: Chris Johns [mailto:chr...@rtems.org] > Sent: Thursday, June 11, 2020 2:26 AM > To: Sommer, Jan; mritunjaysharma...@gmail.com > Cc: rtems-de...@rtems.org > Subject: Re: GSoC 2020: [rtems/rsb]: Error while adding ptp support. Th

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

On 5/6/20 6:03 pm, jan.som...@dlr.de wrote: > We came across the PPSi library for PTP support some time ago: > https://ohwr.org/project/ppsi > In their documentation its says they started with ptpd and then made an > overhaul of the source code. Interesting. Did you check the licenses and

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

github. Then I found this: https://artfiles.org/openbsd/OpenNTPD/openntpd-6.2p3.tar.gz Now I have made a "standard" config file for rsb: # # OpenNTPd 6.2p3 Version 1. # # This configuration file configure's, make's and install's OpenNTPd. # %if %{release} == %{nil} %define

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

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

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

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

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

iday, June 5, 2020 6:09 AM > To: Mritunjay Sharma > Cc: RTEMS Devel > Subject: Re: GSoC 2020: [rtems/rsb]: Error while adding ptp support. This > time building for xilinx_zynq_a9_qemu > > On 04/06/2020 20:29, Mritunjay Sharma wrote: > > > > > > &

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

On 04/06/2020 20:29, Mritunjay Sharma wrote: On Thu, Jun 4, 2020 at 11:07 PM Sebastian Huber > wrote: On 04/06/2020 16:22, Gedare Bloom wrote: >>> In the github version this code is conditional on sys/cpuset.h being present. >>>

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

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 lik

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

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

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

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

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

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

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

On 2020-06-04 16:22, Gedare Bloom wrote: On Thu, Jun 4, 2020 at 7:58 AM Mritunjay Sharma wrote: 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

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

On Thu, Jun 4, 2020 at 7:58 AM Mritunjay Sharma wrote: > > > > 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

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

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

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

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

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

eeds to be compiled with libbsd somehow? or picking up its header files... > 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

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

) 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

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

Although the last few lines tell you to look somewhere else for details, the error is pretty clear from your log. + cd 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

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

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

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

t;> > 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 >

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

y 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 >>> l

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

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

RSB PC BSP packages fail on building curl (libbsd related)

Hi Appears to be something with the probe for gethostbyname. It fails with this: configure:19546: i386-rtems5-gcc -o conftest -qrtems -B/home/joel/rtems-cron-5/rtems-source-builder/rtems/build/tmp/sb-1001-staging/i386-rtems5/lib/

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

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

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

iscuss 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 > > suggeste

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

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

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

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-

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

t; > 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-builde

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

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

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

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

Re: RSB fails to build qemu.bset

On 04/05/20 00:29, Chris Johns wrote: > On 3/5/20 4:33 am, Joel Sherrill wrote: >> >> On Sat, May 2, 2020, 12:42 PM Cláudio Maia > > wrote: >> >> Hello everyone, >> >> I'm trying to build the toolchain for the build set devel/qemu.bset >> with the goal of

Re: RSB fails to build qemu.bset

943.0 bytes of 943.0 bytes (100%) building: qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 error: building qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 Build FAILED   See error report: rsb-report-qemu-42d58e7c6760cb9c55627c28ae538e27dcf

Re: RSB fails to build qemu.bset

; Unescaped left brace in regex is illegal here in regex; marked by <-- > HERE in m/^\@strong{ <-- HERE (.*)}$/ at > /home/crrm/Documents/projects/rtems/rsb/rtems/build/qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1/qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144/

Re: RSB fails to build qemu.bset

-terminate-qemu-process-upon-receiving-a-hal.patch - > 943.0 bytes of 943.0 bytes (100%) > building: qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 > error: building > qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 > Build FAILED > See er

RSB fails to build qemu.bset

c-terminate-qemu-process-upon-receiving-a-hal.patch - 943.0 bytes of 943.0 bytes (100%) building: qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 error: building qemu-42d58e7c6760cb9c55627c28ae538e27dcf2f144-x86_64-linux-gnu-1 Build FAILED   See error

Re: [PATCH 1/1] user/rsb/configuration.rst: Complete review on the text

It would be great to get the DTC corrections also, to close the ticket. On Wed, Apr 8, 2020 at 10:56 AM wrote: > > From: Cláudio Maia > > --- > user/rsb/configuration.rst | 424 +++-- > 1 file changed, 215 insertions(+), 209 deletions(-) >

Re: [PATCH 0/1] user/rsb/configuration.rst: Complete review on the text

Dear all, I’ve sent this patch last week but I didn’t receive any feedback on it. Could please someone review the patch? Regards, Cláudio > On 8 Apr 2020, at 17:55, Cláudio Maia (clrrm) wrote: > > From: Cláudio Maia > > This patch proposes several fixes in the rsb/configu

Re: [PATCH RSB 3/4] source-builder: Add capstone

> > +%include %{_configdir}/bare-config.cfg > > + > > +# > > +# Capstone Version. > > +# > > +%define capstone_version 4.0.1 > > + > > +# > > +# Set sou

Re: [PATCH RSB 3/4] source-builder: Add capstone

. +# +%define capstone_version 4.0.1 + +# +# Set source from github. +# +%source set capstone --rsb-file=capstone-%{capstone_version}.tar.gz https://github.com/aquynh/capstone/archive/%{capstone_version}.tar.gz +%hash sha512 capstone-%{capstone_version}.tar.gz

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

389922f4e7672b6bc5deae71 >>> > +%define qemu_version 03a7fbcce52e0bca7f033ccba79e7856e82bb437 >>> > >>> > # >>> > # Couverture QEMU disables for this version. >>> > @@ -23,21 +23,15 @@ >>> > # >>> > # Couverture

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

rsion. >> > # >> > -%define qemu_archs >> arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu >> > +%define qemu_archs arm-softmmu,i386-softmmu,ppc

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

; # > > -%define qemu_archs > arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu > > +%define qemu_archs arm-softmmu,i386-softmmu,ppc-softmmu,sparc-softmmu > > > > # > > # Set Couverture-Qemu source from github. > >

Re: [PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

version. > # > -%define qemu_archs > arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu > +%define qemu_archs arm-softmmu,i386-softmmu,ppc-softmmu,sparc-softmmu > > # > # Set Couverture-Qemu source from github. > # > %source set q

[PATCH RSB 4/4] qemu-couverture: update to qemu-stable-4.0.0

# # Set Couverture-Qemu source from github. # %source set qemu --rsb-file=qemu-couverture-%{qemu_version}.tar.gz https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz -%hash sha512 qemu-couverture-%{qemu_version}.tar.gz

[PATCH RSB 1/4] bare/glib-2.48.2: Add patches to suppress null string warning

--- bare/config/devel/glib-2.48.2-1.cfg | 7 +++ 1 file changed, 7 insertions(+) diff --git a/bare/config/devel/glib-2.48.2-1.cfg b/bare/config/devel/glib-2.48.2-1.cfg index 9e85fce..38b6d93 100644 --- a/bare/config/devel/glib-2.48.2-1.cfg +++ b/bare/config/devel/glib-2.48.2-1.cfg @@ -14,6

[PATCH RSB 2/4] bare/config: Add devel/dtc-1.6.0

--- bare/config/devel/dtc-1.6.0-1.cfg | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 bare/config/devel/dtc-1.6.0-1.cfg diff --git a/bare/config/devel/dtc-1.6.0-1.cfg b/bare/config/devel/dtc-1.6.0-1.cfg new file mode 100644 index 000..f293f12 --- /dev/null +++

[PATCH RSB 3/4] source-builder: Add capstone

@@ +# +# Capstone from Git +# + +%if %{release} == %{nil} + %define release 1 +%endif + +%include %{_configdir}/base.cfg + +%include %{_configdir}/bare-config.cfg + +# +# Capstone Version. +# +%define capstone_version 4.0.1 + +# +# Set source from github. +# +%source set capstone --rsb-file

Re: [PATCH 2/2] rsb: Bump DTC to 1.4 version

Push both of these and if needed change spike to this as indicated in other thread. On Wed, Apr 8, 2020, 4:00 AM Hesham Almatary wrote: > --- > bare/config/devel/dtc.bset | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/bare/config/devel/dtc.bset

Re: [PATCH] rsb: Fix Spike build

Is the dtc version in spike hardcoded? If so would you update it to use the dtc redirect instead? On Wed, Apr 8, 2020, 4:18 AM Hesham Almatary wrote: > Joel and Christian, > > Thanks for your review. > > Spike bset was already using dtc-1.4.1. I submitted patches to bump > dtc.bset itself. Are

[PATCH 0/1] user/rsb/configuration.rst: Complete review on the text

From: Cláudio Maia This patch proposes several fixes in the rsb/configuration.rst file. The document was reviewed from top to bottom with the following modifications being proposed: - moved the paragraph describing the %source directive closer to where the directive is introduced in the text

[PATCH 1/1] user/rsb/configuration.rst: Complete review on the text

From: Cláudio Maia --- user/rsb/configuration.rst | 424 +++-- 1 file changed, 215 insertions(+), 209 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 4b21dee..561ae60 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb

Re: [PATCH] rsb: Fix Spike build

Joel and Christian, Thanks for your review. Spike bset was already using dtc-1.4.1. I submitted patches to bump dtc.bset itself. Are there any other patches I should apply? Cheers, Hesham On Wed, 8 Apr 2020 at 10:18, Christian Mauderer wrote: > > Hello Hesham and Joel, > > On 07/04/2020

[PATCH 1/2] rsb: Fix Spike build

* There is no all$ target in Spike * There is no longer --with-fesvr flag since fesvr is source-inlined by default --- source-builder/config/spike-1-1.cfg | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/source-builder/config/spike-1-1.cfg

[PATCH 2/2] rsb: Bump DTC to 1.4 version

--- bare/config/devel/dtc.bset | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bare/config/devel/dtc.bset b/bare/config/devel/dtc.bset index d701f93..54521f6 100644 --- a/bare/config/devel/dtc.bset +++ b/bare/config/devel/dtc.bset @@ -4,4 +4,4 @@ %define release 1

Re: [PATCH] rsb: Fix Spike build

Hello Hesham and Joel, On 07/04/2020 16:01, Joel Sherrill wrote: > Please apply your Christian's and your patch. I haven't created a patch for 1.4 yet. But it's quite straightforward. So maybe just create one instead of applying mine. Best regards Christian > > Also bump the dtc base

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Wed, Apr 8, 2020 at 4:10 AM Chris Johns wrote: > On 2020-04-07 23:58, Vijay Kumar Banerjee wrote: > > --- > > bare/config/devel/glib-2.39.3-1.cfg | 4 > > 1 file changed, 4 insertions(+) > > > > diff --git a/bare/config/devel/glib-2.39.3-1.cfg > b/bare/config/devel/glib-2.39.3-1.cfg >

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On 2020-04-07 23:58, Vijay Kumar Banerjee wrote: --- bare/config/devel/glib-2.39.3-1.cfg | 4 1 file changed, 4 insertions(+) diff --git a/bare/config/devel/glib-2.39.3-1.cfg b/bare/config/devel/glib-2.39.3-1.cfg index 9ff7af5..bd5770a 100644 --- a/bare/config/devel/glib-2.39.3-1.cfg

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Wed, Apr 8, 2020, 2:46 AM Gedare Bloom wrote: > On Tue, Apr 7, 2020 at 2:06 PM Vijay Kumar Banerjee > wrote: > > > > > > > > On Wed, Apr 8, 2020 at 12:49 AM Gedare Bloom wrote: > >> > >> On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee > wrote: > >> > > >> > > >> > > >> > On Tue, Apr

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Wed, Apr 8, 2020 at 12:49 AM Gedare Bloom wrote: > On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee > wrote: > > > > > > > > On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote: > >> > >> > >> > >> On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote: > >>> > >>> > >>> I'm not sure what

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee wrote: > > > > On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote: >> >> >> >> On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote: >>> >>> >>> I'm not sure what error this is fixing, is there a ticket open for the >>> warning? >> >> >> No

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote: > > > On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote: > >> >> I'm not sure what error this is fixing, is there a ticket open for the >> warning? >> > > No idea on this. > >> >> Is there a fix for the warning besides squelching it? >> > >

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote: > > I'm not sure what error this is fixing, is there a ticket open for the > warning? > No idea on this. > > Is there a fix for the warning besides squelching it? > I think these are the warnings that are build failures on some hosts. > >

Re: [PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

I'm not sure what error this is fixing, is there a ticket open for the warning? Is there a fix for the warning besides squelching it? How permanent is that gitlab? Should we just pluck these patches ourselves? On Tue, Apr 7, 2020, 7:59 AM Vijay Kumar Banerjee wrote: > --- >

Re: [PATCH] rsb: Fix Spike build

Please apply your Christian's and your patch. Also bump the dtc base package version number. I thought we settled on 1.4. --joel On Tue, Apr 7, 2020 at 3:56 AM Hesham Almatary wrote: > * There is no all$ target in Spike > * There is no longer --with-fesvr flag since fesvr is source-inlined >

[PATCH RSB] bare/glib-2.39.3-1: Add patches to suppress string literal warning

--- bare/config/devel/glib-2.39.3-1.cfg | 4 1 file changed, 4 insertions(+) diff --git a/bare/config/devel/glib-2.39.3-1.cfg b/bare/config/devel/glib-2.39.3-1.cfg index 9ff7af5..bd5770a 100644 --- a/bare/config/devel/glib-2.39.3-1.cfg +++ b/bare/config/devel/glib-2.39.3-1.cfg @@ -14,6

[PATCH] rsb: Fix Spike build

* There is no all$ target in Spike * There is no longer --with-fesvr flag since fesvr is source-inlined by default --- source-builder/config/spike-1-1.cfg | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/source-builder/config/spike-1-1.cfg

Re: [PATCH] rsb: replace asciidoc with rst formatting

On 2020-04-06 07:06, Gedare Bloom wrote: I pushed all my pending docs patches Thank you for reviewing and updating the documentation. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] rsb: replace asciidoc with rst formatting

I pushed all my pending docs patches On Sun, Apr 5, 2020 at 2:48 PM Gedare Bloom wrote: > > --- > user/rsb/commands.rst | 10 +- > user/rsb/configuration.rst | 10 +- > 2 files changed, 10 insertions(+), 10 deletions(-) > > diff --git a/user/rsb/co

Re: Review on user/rsb/configuration.rst

On Sun, Apr 5, 2020 at 11:07 AM Cláudio Maia wrote: > > Hello everyone, > > I have reviewed the file user/rsb/configuration.rst and I want to send a > patch with my proposed changes. However, before doing that I would like to > clarify some aspects before sending

[PATCH] rsb: replace asciidoc with rst formatting

--- user/rsb/commands.rst | 10 +- user/rsb/configuration.rst | 10 +- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/user/rsb/commands.rst b/user/rsb/commands.rst index b85692d..b4787aa 100644 --- a/user/rsb/commands.rst +++ b/user/rsb/commands.rst

[PATCH] user/rsb/configuration: fix typo xy to xz

--- user/rsb/configuration.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 2b45a84..541b3fd 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst @@ -113,8 +113,8 @@ supported compression

[PATCH v2] rsb/configuration: fix broken link to _configdir

--- user/rsb/configuration.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 8c8c87f..2b45a84 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst @@ -329,8 +329,9 @@ changes update only

Re: [PATCH] rsb/configuration: fix broken link to _configdir

Ignore this, the ref is broken. On Sun, Apr 5, 2020 at 2:26 PM Gedare Bloom wrote: > > --- > user/rsb/configuration.rst | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst > index 8c

[PATCH] rsb/configuration: fix broken link to _configdir

--- user/rsb/configuration.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 8c8c87f..fbeb30a 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst @@ -329,8 +329,9 @@ changes update only

Review on user/rsb/configuration.rst

Hello everyone, I have reviewed the file user/rsb/configuration.rst and I want to send a patch with my proposed changes. However, before doing that I would like to clarify some aspects before sending the patch, namely: - In the section 13.5.7 it is mentioned the following "The Device

[PATCH] user/rsb: describe how to create configuration reports

Closes #3629. --- user/rsb/configuration.rst | 21 ++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb/configuration.rst index 8c8c87f..7ad58ed 100644 --- a/user/rsb/configuration.rst +++ b/user/rsb/configuration.rst

[PATCH RSB v2 1/2] Add clean-cfg.sh script to find and remove unused cfg files

Updates #3273. --- clean-cfg.sh | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 clean-cfg.sh diff --git a/clean-cfg.sh b/clean-cfg.sh new file mode 100644 index 000..eb3a82b --- /dev/null +++ b/clean-cfg.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +for f in `find . -name

Re: [PATCH RSB 1/2] Add clean-cfg.sh script to find and remove unused cfg files

On Sat, Apr 4, 2020 at 1:29 PM Gedare Bloom wrote: > > Closes #3273. > --- > clean-cfg.sh | 11 +++ > 1 file changed, 11 insertions(+) > create mode 100644 clean-cfg.sh > > diff --git a/clean-cfg.sh b/clean-cfg.sh > new file mode 100644 > index 000..cad678b > --- /dev/null > +++

[PATCH RSB 0/2] RSB removed used tools configuration files.

These two patches demonstrate a bash script approach to automate the removal of unused configuration (*.cfg) files within the RSB. See https://devel.rtems.org/ticket/3273 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo

[PATCH RSB 1/2] Add clean-cfg.sh script to find and remove unused cfg files

Closes #3273. --- clean-cfg.sh | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 clean-cfg.sh diff --git a/clean-cfg.sh b/clean-cfg.sh new file mode 100644 index 000..cad678b --- /dev/null +++ b/clean-cfg.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +for f in `find . -name "*.cfg"

Re: [PATCH rtems-docs] user/rsb: Fix typos (#3922)

Pushed. Thanks. Chris On 2020-04-02 19:18, Mritunjay wrote: Closes #3922 --- user/rsb/configuration.rst| 14 +++--- user/rsb/cross-canadian-cross.rst | 2 +- user/rsb/project-sets.rst | 2 +- user/rsb/third-party-packages.rst | 2 +- 4 files changed, 10

[PATCH rtems-docs] user/rsb: Fix typos (#3922)

Closes #3922 --- user/rsb/configuration.rst| 14 +++--- user/rsb/cross-canadian-cross.rst | 2 +- user/rsb/project-sets.rst | 2 +- user/rsb/third-party-packages.rst | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/user/rsb/configuration.rst b

[PATCH] Fix typos in (master)rtems-docs/user/rsb

--- user/rsb/configuration.rst| 14 +++--- user/rsb/cross-canadian-cross.rst | 2 +- user/rsb/project-sets.rst | 2 +- user/rsb/third-party-packages.rst | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb

Re: [PATCH] Fix typos in rtems-docs-4.11/rsb

t; > > > Hi Gedare, > > > > Apologies as I missed that rsb is moved to user/rsb in the master. After > going > > through it, I have found that files: > > rsb/hosts.rst > > rsb/quick-start.rst > > are no longer there in the master branch. However, most of the typos a

Re: [PATCH] Fix typos in rtems-docs-4.11/rsb

Can you send a patch to fix the typos in Master? we can also apply to 4.11, but would like to fix them in master for sure. On Tue, Mar 31, 2020 at 11:16 AM Mritunjay Sharma wrote: > > Hi Gedare, > > Apologies as I missed that rsb is moved to user/rsb in the master. After going >

Re: [PATCH] Fix typos in rtems-docs-4.11/rsb

Hi Gedare, Apologies as I missed that rsb is moved to user/rsb in the master. After going through it, I have found that files: rsb/hosts.rst rsb/quick-start.rst are no longer there in the master branch. However, most of the typos are still there in other remaining files. On Tue, Mar 31, 2020

Re: [PATCH] Fix typos in rtems-docs-4.11/rsb

Hi Mritunjay, Are these all fixed already in master branch? these docs moved to user/rsb/* On Tue, Mar 31, 2020 at 4:22 AM Mritunjay wrote: > > --- > > This patch fixes typos encountered while going through the documentation > of rtems-docs-4.11/rsb. > > rsb/configur

[PATCH] Fix typos in rtems-docs-4.11/rsb

--- This patch fixes typos encountered while going through the documentation of rtems-docs-4.11/rsb. rsb/configuration.rst| 24 rsb/cross-canadian-cross.rst | 2 +- rsb/hosts.rst| 4 ++-- rsb/project-sets.rst | 4 ++-- rsb/quick

Re: RSB Release source download is broken ...

On 2020-03-27 09:21, Chris Johns wrote: On 2020-03-27 09:12, Chris Johns wrote: Anyone know what this is about and able to help? This patch moves a config file and it still referenced ... https://git.rtems.org/rtems-source-builder/commit/?id=f93fcef875560f6a8ac7a3a541e4a96f73751553 I

Re: RSB Release source download is broken ...

On 2020-03-27 09:12, Chris Johns wrote: Anyone know what this is about and able to help? This patch moves a config file and it still referenced ... https://git.rtems.org/rtems-source-builder/commit/?id=f93fcef875560f6a8ac7a3a541e4a96f73751553 Chris

RSB Release source download is broken ...

Hi, The RSB download of source for a release is broken here: Build Set: Time 0:00:03.530061 Build Set: devel/qemu-couverture for solaris error: devel/qemu-couverture:23: cannot find file: devel/glib-2.39.3-1 Build Set: Time 0:00:00.000958 Build FAILED Anyone know what this is about and able

Re: riscv BSPs on Spike due to weird RSB side-effect

I got feedback on this issue with the Spike project and just sent them a pull request to fix this and add more files to their .gitignore. Once those are settled, I will update the RSB and close our ticket (I hope). --joel On Sat, Mar 21, 2020 at 1:56 PM Gedare Bloom wrote: > On Sat, Mar

Re: riscv BSPs on Spike due to weird RSB side-effect

rtems.org/pipermail/build/2020-March/02.html >>> >>> Does spike work if there isn't this problem? >>> >>> I can poke at the host exes to see if the dtc path is hard-coded. >>> Otherwise, this seems very strange. >> >> >> I can confirm that spi

Re: riscv BSPs on Spike due to weird RSB side-effect

ron-5/tools/5/bin/dtc: >> No such file or directory >> ] Child dtb process failed >> >> https://lists.rtems.org/pipermail/build/2020-March/02.html >> >> Does spike work if there isn't this problem? >> >> I can poke at the host exes to see if

Re: riscv BSPs on Spike due to weird RSB side-effect

ms.org/pipermail/build/2020-March/02.html > > Does spike work if there isn't this problem? > > I can poke at the host exes to see if the dtc path is hard-coded. Otherwise, > this seems very strange. > > I can confirm that spike built with the RSB has the hard-coded

riscv BSPs on Spike due to weird RSB side-effect

Hi I think something is wrong with the build of spike that ends up with a hard-coded path to inside a build tree: Result: invalidTime: 0:00:01.197748 mimfs_fslink.exe => run: spike --isa=RV32IAC ./riscv-rtems5/c/rv32iac/testsuites/fstests/mimfs_fslink.exe ] Failed to run

<    1   2   3   4   5   6   7   8   9   10   >