Re: [PATCH] Bump RSB to the latest rtems-tools to get mkimage.py

On 2020-03-04 18:02 -0600, Joel Sherrill wrote: > I think this is OK.?? > > I will bump the newlib hash as soon as my patch to newlib is merged. Great, thanks! Amar. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] Bump RSB to the latest rtems-tools to get mkimage.py

I think this is OK. I will bump the newlib hash as soon as my patch to newlib is merged. --joel On Wed, Mar 4, 2020 at 6:01 PM Amar Takhar wrote: > --- > rtems/config/tools/rtems-tools-5-1.cfg | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

[PATCH] Bump RSB to the latest rtems-tools to get mkimage.py

--- rtems/config/tools/rtems-tools-5-1.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rtems/config/tools/rtems-tools-5-1.cfg b/rtems/config/tools/rtems-tools-5-1.cfg index da22b4c..0c67901 100644 --- a/rtems/config/tools/rtems-tools-5-1.cfg +++

Re: RSB build failed.

Hi Chris Yes??It works??thanks?? iPhone -- Original -- From: Chris Johns https://git.rtems.org/rtems-source-builder/commit/?id=591deae6d7411af04fd31d2a68dee9520b33c657 ... however this option does not help. It is not clear to me what is wrong with

Re: RSB build failed.

jameszxj, I have pushed changes to the RSB that I hope fixes the build. Please update and see if this fixes things for you. Thanks Chris On 10/2/20 11:53 am, Chris Johns wrote: > On 10/2/20 10:36 am, Chris Johns wrote: >> I think clang or gcc has some links that fail but I thought I

Re: RSB build failed.

On 10/2/20 10:36 am, Chris Johns wrote: > I think clang or gcc has some links that fail but I thought I had a fix for > this > where bsdtar is run a second time on windows. I cannot seem to find it. I have found the fix I added when adding clang support ...

Re: RSB build failed.

On 10/2/20 10:19 am, Joel Sherrill wrote: > > > On Sun, Feb 9, 2020, 5:07 PM Chris Johns <mailto:chr...@rtems.org>> wrote: > > On 10/2/20 9:40 am, Chris Johns wrote: > > On 10/2/20 8:25 am, Chris Johns wrote: > >> On 9/2/20 2:18 pm, jameszx

Re: RSB build failed.

On Sun, Feb 9, 2020, 5:07 PM Chris Johns wrote: > On 10/2/20 9:40 am, Chris Johns wrote: > > On 10/2/20 8:25 am, Chris Johns wrote: > >> On 9/2/20 2:18 pm, jameszxj wrote: > >>> Hi, > >>>RSB failed when build gdb on MINGW64. > >>> >

Re: RSB build failed.

On 10/2/20 9:40 am, Chris Johns wrote: > On 10/2/20 8:25 am, Chris Johns wrote: >> On 9/2/20 2:18 pm, jameszxj wrote: >>> Hi, >>>    RSB failed when build gdb on MINGW64. >>> >>> error messages: >>> >>> D:/msys64/mingw64/bin/../lib/

Re: RSB build failed.

On 10/2/20 8:25 am, Chris Johns wrote: > On 9/2/20 2:18 pm, jameszxj wrote: >> Hi, >>    RSB failed when build gdb on MINGW64. >> >> error messages: >> >> D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: >

Re: RSB build failed.

On 9/2/20 2:18 pm, jameszxj wrote: > Hi, >    RSB failed when build gdb on MINGW64. > > error messages: > > D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: > ada-tasks.o: in function `memcpy': > D:/msys64/mingw64/x8

RSB build failed.

Hi, RSB failed when build gdb on MINGW64. error messages: D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ada-tasks.o: in function `memcpy': D:/msys64/mingw64/x86_64-w64-mingw32/include/string.h:202: undefined reference to `__memcpy_chk' D

Re: [PATCH v2] [rsb] Update Spike build

>From my perspective, yes. If it breaks something else, we can fix that. On Wed, Oct 30, 2019 at 9:47 AM Hesham Almatary < hesham.almat...@cl.cam.ac.uk> wrote: > OK to push? > > On Tue, 29 Oct 2019 at 09:25, Hesham Almatary > wrote: > > > > On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote: >

Re: [PATCH v2] [rsb] Update Spike build

OK to push? On Tue, 29 Oct 2019 at 09:25, Hesham Almatary wrote: > > On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote: > > > > > > > > On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary > > wrote: > >> > >> On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote: > >> > > >> > > >> > > >> > On

Re: [PATCH v2] [rsb] Update Spike build

On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote: > > > > On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary > wrote: >> >> On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote: >> > >> > >> > >> > On 28/10/19 9:21 am, Hesham Almatary wrote: >> > > >> > > >> > > On Sun, 27 Oct 2019 at 20:54, Chris

Re: [PATCH v2] [rsb] Update Spike build

On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary < hesham.almat...@cl.cam.ac.uk> wrote: > On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote: > > > > > > > > On 28/10/19 9:21 am, Hesham Almatary wrote: > > > > > > > > > On Sun, 27 Oct 2019 at 20:54, Chris Johns > > > wrote:

Re: [PATCH v2] [rsb] Update Spike build

On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote: > > > > On 28/10/19 9:21 am, Hesham Almatary wrote: > > > > > > On Sun, 27 Oct 2019 at 20:54, Chris Johns > > wrote: > > > > On 27/10/19 9:37 pm, Hesham Almatary wrote: > > > Yeah fesvr is now part of Spike

Re: RSB Qemu Leon3 patches error

On 10/25/19 4:01 PM, Joel Sherrill wrote: > Hi > > I am not sure what's up with the Leon patches but I am getting a checksum > error and wanted to see if Jiri or someone else knowledgeable could > investigate and fix. > > warning: checksum error: 0001-LEON3-Add-emulation-of-AMBA-plug-play.patch

Re: [PATCH v2] [rsb] Update Spike build

On 28/10/19 9:21 am, Hesham Almatary wrote: > > > On Sun, 27 Oct 2019 at 20:54, Chris Johns > wrote: > > On 27/10/19 9:37 pm, Hesham Almatary wrote: > > Yeah fesvr is now part of Spike in-tree. I didn't like it had to be > > built separately either [1]. >

Re: [PATCH v2] [rsb] Update Spike build

On Sun, 27 Oct 2019 at 20:54, Chris Johns wrote: > On 27/10/19 9:37 pm, Hesham Almatary wrote: > > Yeah fesvr is now part of Spike in-tree. I didn't like it had to be > > built separately either [1]. > > > > Joel, AFAIR, dtc was always needed. > > Please have the package build FDT if it is

Re: [PATCH v2] [rsb] Update Spike build

On 27/10/19 9:37 pm, Hesham Almatary wrote: > Yeah fesvr is now part of Spike in-tree. I didn't like it had to be > built separately either [1]. > > Joel, AFAIR, dtc was always needed. Please have the package build FDT if it is needed. Do no rely on it being installed as some hosts do not have a

Re: [PATCH v2] [rsb] Update Spike build

Yeah fesvr is now part of Spike in-tree. I didn't like it had to be built separately either [1]. Joel, AFAIR, dtc was always needed. [1] https://github.com/riscv/riscv-isa-sim/issues/254 On Fri, 25 Oct 2019 at 14:59, Joel Sherrill wrote: > > Thanks for updating this. > > When building on a

RSB Qemu Leon3 patches error

Hi I am not sure what's up with the Leon patches but I am getting a checksum error and wanted to see if Jiri or someone else knowledgeable could investigate and fix. warning: checksum error: 0001-LEON3-Add-emulation-of-AMBA-plug-play.patch warning: removing:

Re: [PATCH v2] [rsb] Update Spike build

Thanks for updating this. When building on a very clean machine, dtc needs to be referenced and in the PATH. hecking for dtc... no configure: error: device-tree-compiler not found Is this working for you when dtc is not installed before building spike? On Thu, Oct 24, 2019 at 4:39 PM Chris

Re: [PATCH v2] [rsb] Update Spike build

On 24/10/19 7:57 pm, Hesham Almatary wrote: > Latest Spike integrated fesvr in its source directory, so there > is no separate fesvr anymore. Nice. Building and installing fesvr was a little unusual. Chris ___ devel mailing list devel@rtems.org

[PATCH v2] [rsb] Update Spike build

8ff52bfde488c93e847696714b5fef5d2a97ec78582c4ad2d9800cfe4772facba10b685cdc6d51fbeeef47b4d781678285ffb691d2ec82ea8fbd09f0c244d2c5 - -# RISC-V's front-end server (fesvr) -%hash sha512 %{fesvr_version}.tar.gz 62979227fc67e3c03a14de2ad29523addd032333979a5fe9765aaacd0265d3de92e345367c637b1c907378b6e84e521361922bfb87830659d2476f500f2f3ff1 - -%patch add spike --rsb-file=spike-include-permissions.patch https://devel.rtems.org/raw

Re: [PATCH] [rsb] Update Spike build

On Tue, 22 Oct 2019 at 16:08, Joel Sherrill wrote: > > Did you see my previous patch where Chris had helped simplify things. > No, I must have missed that. What's the patch subject? > Also does this hash include the fix for the permissions issue I reported? > Yes as per the commit message, the

Re: [PATCH] [rsb] Update Spike build

Did you see my previous patch where Chris had helped simplify things. Also does this hash include the fix for the permissions issue I reported? On Tue, Oct 22, 2019, 9:56 AM Hesham Almatary wrote: > Latest Spike integrated fesvr in its source directory, so there > is no separate fesvr anymore.

[PATCH] [rsb] Update Spike build

Latest Spike integrated fesvr in its source directory, so there is no separate fesvr anymore. Also use a revision of Spike that fixes the file permissions when getting installed. --- bare/config/devel/spike-1.1.0.cfg | 5 + source-builder/config/spike-1-1.cfg | 19 +-- 2

[PATCH] Update Spike RSB recipe and correct installed permissions

9b5ec44723fd96a961d93d369e50e6aeb327341b2dc42c17ed340d1bc0425511deb23fcf1e7c5926486c2a10bfc3cc6d6f4ceb0cda63590d46468db0ee2b1d3b +%hash sha512 %{fesvr_version}.tar.gz 62979227fc67e3c03a14de2ad29523addd032333979a5fe9765aaacd0265d3de92e345367c637b1c907378b6e84e521361922bfb87830659d2476f500f2f3ff1 + +%patch add spike --rsb-file=spike-include-permissions.patch https://devel.rtems.org/raw

[PATCH] user/rsb: Update 3rd party package build and add packaging details.

From: Chris Johns --- user/rsb/configuration.rst| 6 +- user/rsb/cross-canadian-cross.rst | 27 +- user/rsb/index.rst| 84 ++-- user/rsb/project-sets.rst | 144 +++ user/rsb/third-party-packages.rst | 635 ++ user/start

[PATCH] [rsb] Update Spike build

Latest Spike integrated fesvr in its source directory, so there is no separate fesvr anymore. --- bare/config/devel/spike-1.1.0.cfg | 5 + source-builder/config/spike-1-1.cfg | 19 +-- 2 files changed, 6 insertions(+), 18 deletions(-) diff --git

Re: RSB do not build rtems-tools any more?

Chris Johns"; Date: Sun, Sep 29, 2019 12:20 PM To: "jameszxj"; Cc: "devel"; Subject: Re: RSB do not build rtems-tools any more? On 29 Sep 2019, at 12:11 pm, jameszxj wrote: I build from rtems-source-builder version(abbcc5d8c6b4de60f83aaece5a9f4feef4c251c9) on MSYS2,

Re: RSB do not build rtems-tools any more?

> On 29 Sep 2019, at 12:11 pm, jameszxj wrote: >I build from rtems-source-builder > version(abbcc5d8c6b4de60f83aaece5a9f4feef4c251c9) on MSYS2, > command is "../source-builder/sb-set-builder --log=l-arm.txt > --prefix=/opt/rtems/5.1 5/rtems-arm" but rtems-tools was not build. Can you

RSB do not build rtems-tools any more?

HI, I build from rtems-source-builder version(abbcc5d8c6b4de60f83aaece5a9f4feef4c251c9) on MSYS2, command is "../source-builder/sb-set-builder --log=l-arm.txt --prefix=/opt/rtems/5.1 5/rtems-arm" but rtems-tools was not build.___ devel mailing list

Re: RSB LLVM Package (chr...@rtems.org)

ng built newlib This patch is a step as it gives more developers easier access to the tool chain. Note, gcc support will be maintain and a core focus because it supports more architectures than clang. Also adding LLVM as a package to the RSB means we can grow the support in rtems-tools and depreca

Re: RSB LLVM Package (chr...@rtems.org)

Hi, Chris, It’s great to hear about rtems has made some progress on LLVM. I’m quite new to rtems, so I have questions about the rtems-llvm packages 1. Can I use rtems-llvm clang compiler build application c code? 2. Does rtems code and newlib still need use arm gcc toolchain? mko_io

RSB LLVM Package

. There are some changes to the RSB build code to handle downloading but not installing a source package. - LLVM lldb is not built on MacOS by default. You can override the default by adding --with-llvm-lldb. If you do this you will need to have a self signed codesign certificate in your keyring

Re: [PATCH RSB] Add gdb-8.3 as default debugger

On 21/8/19 5:33 pm, Jiri Gaisler wrote: > I suggest that we switch to gdb-8.3 for targets that currently use 8.2.1. The > update is relatively minor but allows building without any patches. Tested > for SPARC and RISC-V targets. I am OK with this happening. Please push. Thanks Chris

[PATCH RSB] Add gdb-8.3 as default debugger

I suggest that we switch to gdb-8.3 for targets that currently use 8.2.1. The update is relatively minor but allows building without any patches. Tested for SPARC and RISC-V targets. Jiri. >From 5b12c03d184d6cea7019636fc134e06d25a94d9f Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Wed, 21

Re: [RSB PATCH] Added qemu 4.1.0 as bare target

On 20/8/19 4:59 pm, Jiri Gaisler wrote: > > On 8/20/19 12:44 AM, Chris Johns wrote: >> On 20/8/19 6:53 am, Jiri Gaisler wrote: >>> This patch will add QEMU-4.1.0 as RSB target devel/qemu4. >> Looks good. >> >>> The current devel/qemu target will be p

Re: [RSB PATCH] Added qemu 4.1.0 as bare target

On 8/20/19 12:44 AM, Chris Johns wrote: > On 20/8/19 6:53 am, Jiri Gaisler wrote: >> This patch will add QEMU-4.1.0 as RSB target devel/qemu4. > Looks good. > >> The current devel/qemu target will be preserved. > Should devel/qemu just point to qemu4? I am OK with this

Re: [RSB PATCH] Added qemu 4.1.0 as bare target

On 20/8/19 6:53 am, Jiri Gaisler wrote: > This patch will add QEMU-4.1.0 as RSB target devel/qemu4. Looks good. > The current devel/qemu target will be preserved. Should devel/qemu just point to qemu4? I am OK with this happening. > Builds and installs fine on ubuntu 18.04 x86_

[RSB PATCH] Added qemu 4.1.0 as bare target

This patch will add QEMU-4.1.0 as RSB target devel/qemu4. The current devel/qemu target will be preserved. Builds and installs fine on ubuntu 18.04 x86_64. Build scripts might need tweaks for other platforms. A few patches are still pulled in, currently hosted on gaisler.org but could be moved

Re: RSB build error (MSYS2)

On 12/8/19 11:19 am, jameszxj wrote: > Hi, > I tried to update the compiler to RSB master, and encountered an error. > command line: >    ../source-builder/sb-set-builder --dry-run --with-download 5/rtems-arm > > error messgae: > > config: tools/rtems-gdb-8.2.1-1.cfg >

RSB build error (MSYS2)

Hi, I tried to update the compiler to RSB master, and encountered an error. command line: ../source-builder/sb-set-builder --dry-run --with-download 5/rtems-arm error messgae: config: tools/rtems-gdb-8.2.1-1.cfg error: shell macro failed: sh -c "/mingw64/bin/python2-config --ldflags

Re: Problem: RSB does no longer install stand-alone sis

problem but I cannot remember what. :) OK. I ran RSB on Freebsd, MacOSX, ubuntu 18.04 and WSL before pushing the revert to minimize the likelihood of me breaking anything. > > I would prefer we have the configs in the RSB use `%{host_build_flags}` > because > in that expanded macro is

Re: Problem: RSB does no longer install stand-alone sis

e have the configs in the RSB use `%{host_build_flags}` because in that expanded macro is the logic that handles all hosts and situations we have found over the years. > If I revert that, installation works again. If nobody > objects, I will push a revert in about an hour and we can debug this at >

Re: Problem: RSB does no longer install stand-alone sis

am, Gedare Bloom wrote: >> On Thu, Aug 8, 2019 at 3:53 PM Gedare Bloom wrote: >>> I can confirm something is wrong. The install step does copy something >>> though, I get a tree like this: >>> /share/rtems/rsb: >>> sis-2.17-x86_64-linux-gnu-1.txt sis-2.1

Re: Problem: RSB does no longer install stand-alone sis

On 9/8/19 7:59 am, Gedare Bloom wrote: > On Thu, Aug 8, 2019 at 3:53 PM Gedare Bloom wrote: >> >> I can confirm something is wrong. The install step does copy something >> though, I get a tree like this: >> /share/rtems/rsb: >> sis-2.17-x86_64-linux-gnu-1.txt

Re: [RSB PATCH v2] Disable built-in sis in gdb.

On Thu, Aug 8, 2019, 5:06 PM Jiri Gaisler wrote: > > On 8/8/19 11:48 PM, Joel Sherrill wrote: > > Unless it causes an issue, I would really like to leave sis enabled inside > gdb. It really is such a nice environment to debug. > > Stand-alone sis has a gdb server, so the gdb debug environment

Re: [RSB PATCH v2] Disable built-in sis in gdb.

On 8/8/19 11:48 PM, Joel Sherrill wrote: > Unless it causes an issue, I would really like to leave sis enabled inside > gdb. It really is such a nice environment to debug. Stand-alone sis has a gdb server, so the gdb debug environment should be identical. In gdb, just do target extended-remote

Re: Problem: RSB does no longer install stand-alone sis

On Thu, Aug 8, 2019 at 3:53 PM Gedare Bloom wrote: > > I can confirm something is wrong. The install step does copy something > though, I get a tree like this: > /share/rtems/rsb: > sis-2.17-x86_64-linux-gnu-1.txt sis-2.17-x86_64-linux-gnu-1.xml > > I gave --log option to

Re: Problem: RSB does no longer install stand-alone sis

I can confirm something is wrong. The install step does copy something though, I get a tree like this: /share/rtems/rsb: sis-2.17-x86_64-linux-gnu-1.txt sis-2.17-x86_64-linux-gnu-1.xml I gave --log option to sb-set-builder. I can see the build compiled. It looks like %clean is running before

Re: [RSB PATCH v2] Disable built-in sis in gdb.

Unless it causes an issue, I would really like to leave sis enabled inside gdb. It really is such a nice environment to debug. On Thu, Aug 8, 2019, 4:47 PM Jiri Gaisler wrote: > This time it also works on RISC-V ... :-) > > ___ > devel mailing list >

[RSB PATCH v2] Disable built-in sis in gdb.

This time it also works on RISC-V ... :-) >From e5460e9ecb9995298319653460fab8852274c211 Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Thu, 8 Aug 2019 22:20:39 +0200 Subject: [PATCH] Disable built-in sis in gdb. * Avoid building problems on Cygwin et al. * Avoid mix-up with more recent

Problem: RSB does no longer install stand-alone sis

RSB does not longer install the stand-alone version of sis. Even though the RSB log claims is does, the binary is not copied to the install location: installing: sis-2.17-x86_64-linux-gnu-1 -> /opt/rtems/5    does nothing There has been a few commits that changes the RSB install scri

Re: [RSB PATCH] Disable built-in sis in gdb.

OK, this patch kills building gdb for RISC-V - I will resubmit with a proper fix ... Jiri. On 8/8/19 10:45 PM, Jiri Gaisler wrote: > Small patch for RSB  to disable building sis inside gdb. > > I will follow up with a patch for rtems-tools to clean up rtems-test targets > for sis

[RSB PATCH] Disable built-in sis in gdb.

Small patch for RSB  to disable building sis inside gdb. I will follow up with a patch for rtems-tools to clean up rtems-test targets for sis ... Jiri. >From 9165334d3ffe9996276de9c7843998124890c3e3 Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Thu, 8 Aug 2019 22:20:39 +0200 Subj

Re: Spike fails to build with RSB

mmy_rocc.pc' > Build Set: Time 0:00:19.604209 > Build FAILED > > Any ideas why this fails? > > FWIW I have never been able to build spike with the RSB and have reported > it before. It would be nice if it got fixed. > > Thanks. > > --joel > l-spike.txt.bz2 D

Spike fails to build with RSB

are/build/tmp/sb-joel/devel/spike/home/joel/rtems-work/tools/5/lib/pkgconfig/riscv-dummy_rocc.pc' Build Set: Time 0:00:19.604209 Build FAILED Any ideas why this fails? FWIW I have never been able to build spike with the RSB and have reported it before. It would be nice if it got fixed. Tha

[PATCH 1/3] user/rsb/deployment.rst: Fix typo.

--- user/rsb/deployment.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/user/rsb/deployment.rst b/user/rsb/deployment.rst index ad5dd57..afbf13a 100644 --- a/user/rsb/deployment.rst +++ b/user/rsb/deployment.rst @@ -81,7 +81,7 @@ A build set tar file is created by adding

Re: GSoC 2019 | POSIX Compliance - RSB patch generated ndbm library (lib_a-ndbm.o) successfully in RTEMS Toolchain

Jul 11, 2019 at 2:12 AM Vaibhav Gupta > wrote: > >>> > >>> Hello, > >>> After Joel pointed out in an offlist discussion, > >>> I made a new patch for ndbm port. > >>> . > >>> To send the changes to Newlib, i had to place `n

Re: GSoC 2019 | POSIX Compliance - RSB patch generated ndbm library (lib_a-ndbm.o) successfully in RTEMS Toolchain

ter Joel pointed out in an offlist discussion, >>> I made a new patch for ndbm port. >>> . >>> To send the changes to Newlib, i had to place `ndbm.h` , `ndbm.c` in their >>> respective places and make changes in Makefile.am. >>> Before, I applied

Re: GSoC 2019 | POSIX Compliance - RSB patch generated ndbm library (lib_a-ndbm.o) successfully in RTEMS Toolchain

To send the changes to Newlib, i had to place `ndbm.h` , `ndbm.c` in >> their respective places and make changes in Makefile.am. >> Before, I applied same patch to RSB hence ndbm library was not generated. >> . >> > In my local build yesterday, I saw the symbols in the installe

Re: GSoC 2019 | POSIX Compliance - RSB patch generated ndbm library (lib_a-ndbm.o) successfully in RTEMS Toolchain

le.am. > Before, I applied same patch to RSB hence ndbm library was not generated. > . > In my local build yesterday, I saw the symbols in the installed libc.a. I have not run the tests. > . > This time I also added files generated by `autoreconf -fvi` in the patch. > . >

GSoC 2019 | POSIX Compliance - RSB patch generated ndbm library (lib_a-ndbm.o) successfully in RTEMS Toolchain

Hello, After Joel pointed out in an offlist discussion, I made a new patch for ndbm port. . To send the changes to Newlib, i had to place `ndbm.h` , `ndbm.c` in their respective places and make changes in Makefile.am. Before, I applied same patch to RSB hence ndbm library was not generated

[PATCH] user/rsb: Update 3rd party package build and add details.

From: Chris Johns --- user/rsb/configuration.rst| 6 +- user/rsb/index.rst| 51 +-- user/rsb/third-party-packages.rst | 545 ++ 3 files changed, 439 insertions(+), 163 deletions(-) diff --git a/user/rsb/configuration.rst b/user/rsb

Re: Add newlib patch to RTEMS RSB

going? >> >> I have placed ndbm.h in newlib/libc/includedirectory. >> . >> ndbm.h requiresdb.h (named as db_local.h in newlib), which is >> present innewlib/libc/search directory. >> This directory also contains hash.h and hash.c which

Re: Add newlib patch to RTEMS RSB

;> >> >> Great! How is the testing going? >> > I have placed ndbm.h in newlib/libc/includedirectory. > . > ndbm.h requiresdb.h (named as db_local.h in newlib), which is > present innewlib/libc/search directory. > This directory also contains

Re: Add newlib patch to RTEMS RSB

> > . > > Here is the new git-diff. This got compiled successfully > > diff --git a/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > b/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > > index b28a4b1..5c5c346 100644 > > --- a/rtems/config/tools/rte

Re: Add newlib patch to RTEMS RSB

got compiled successfully > diff --git a/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > b/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > index b28a4b1..5c5c346 100644 > --- a/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > +++ b/rtems/config/tools

Re: Add newlib patch to RTEMS RSB

t innewlib/libc/search directory. This directory also contains hash.h and hash.c which is required byndbm.c . So gedare suggested me to placendbm.c in this libc/search directory. . Here, when I compiled newlib for sparc, it was successful and generates function symbols. .

Re: Add newlib patch to RTEMS RSB

inrtems-gcc-7.4.0-newlib-1d35a003f.cfg. Also, I had put > "%patch setup" statement before "%patch add" . > . > . > . > Here is the new git-diff. This got compiled successfully > Great! How is the testing going? For the RSB until the patch is m

Re: [PATCH v1] port newlib ndbm patch to rtems rsb 01

On 21/6/19 6:29 am, Vaibhav Gupta wrote: > --- > rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git a/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > b/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg > index

Re: Add newlib patch to RTEMS RSB

On 21/6/19 4:43 am, Gedare Bloom wrote: > On Thu, Jun 20, 2019 at 11:32 AM Vaibhav Gupta > wrote: >> + /bin/cat >> /home/varodek/development/rtems/rsb/rtems/patches/0001-Port-ndbm.patch >> + /usr/bin/patch -p3 > > This is the problem, the -p3 is wrong. I don't kn

Re: Add newlib patch to RTEMS RSB

Chris. can you provide some patch and RSB guidance? Please On Thu, Jun 20, 2019 at 2:07 PM Vaibhav Gupta wrote: > > > On Fri, Jun 21, 2019 at 12:13 AM Gedare Bloom wrote: > >> On Thu, Jun 20, 2019 at 11:32 AM Vaibhav Gupta >> wrote: >> > >> > I checke

[PATCH v1] port newlib ndbm patch to rtems rsb 01

--- rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg | 6 ++ 1 file changed, 6 insertions(+) diff --git a/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg b/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg index b28a4b1..b8fa829 100644 ---

Re: Add newlib patch to RTEMS RSB

On Fri, Jun 21, 2019 at 12:13 AM Gedare Bloom wrote: > On Thu, Jun 20, 2019 at 11:32 AM Vaibhav Gupta > wrote: > > > > I checked that erc32 is using rtems-sparc.bset file > > Inside it i found, it is using > rsb/rtems/config/tools/rtems-gcc-7.4.0-newlib-1

Re: Add newlib patch to RTEMS RSB

On Thu, Jun 20, 2019 at 11:32 AM Vaibhav Gupta wrote: > > I checked that erc32 is using rtems-sparc.bset file > Inside it i found, it is using > rsb/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f file > . > I added following lines to > rsb/rtems/c

Add newlib patch to RTEMS RSB

I checked that erc32 is using rtems-sparc.bset file Inside it i found, it is using rsb/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f file . I added following lines to rsb/rtems/config/tools/rtems-gcc-7.4.0-newlib-1d35a003f.cfg %prep %patch setup newlib -p1 . . . %patch add

Re: [RSB PATCH 0/2] Add standalone SIS as build target

On 15/6/19 8:00 am, Jiri Gaisler wrote: > Two patches to add standalone SIS as bare target, and to build it for > SPARC and RISC-V tool-chains. Look good. Please check in. Thank you for this. Chris ___ devel mailing list devel@rtems.org

[RSB PATCH 1/2] Add bare target to build standalone sis (devel/sis)

--- bare/config/devel/sis-2-1.cfg | 18 + bare/config/devel/sis.bset| 8 source-builder/config/sis-2-1.cfg | 66 +++ 3 files changed, 92 insertions(+) create mode 100644 bare/config/devel/sis-2-1.cfg create mode 100644

[RSB PATCH 0/2] Add standalone SIS as build target

Two patches to add standalone SIS as bare target, and to build it for SPARC and RISC-V tool-chains. Jiri Gaisler (2): Add bare target to build standalone sis (devel/sis) Build standalone sis for SPARC and RISC-V targets bare/config/devel/sis-2-1.cfg | 18 +

[RSB PATCH 2/2] Build standalone sis for SPARC and RISC-V targets

--- rtems/config/5/rtems-riscv.bset | 1 + rtems/config/5/rtems-sparc.bset | 2 ++ 2 files changed, 3 insertions(+) diff --git a/rtems/config/5/rtems-riscv.bset b/rtems/config/5/rtems-riscv.bset index 99f0754..6e9de99 100644 --- a/rtems/config/5/rtems-riscv.bset +++

[PATCH v3 4/8] rtemstoolkit/path: Merge RSB changes.

From: Chris Johns --- rtemstoolkit/path.py | 294 ++- 1 file changed, 233 insertions(+), 61 deletions(-) diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py index 845dfe8..9401e99 100644 --- a/rtemstoolkit/path.py +++ b/rtemstoolkit/path.py @@

[PATCH v2 4/8] rtemstoolkit/path: Merge RSB changes.

From: Chris Johns --- rtemstoolkit/path.py | 294 ++- 1 file changed, 233 insertions(+), 61 deletions(-) diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py index 845dfe8..9401e99 100644 --- a/rtemstoolkit/path.py +++ b/rtemstoolkit/path.py @@

[PATCH 4/7] rtemstoolkit/path: Merge RSB changes.

From: Chris Johns --- rtemstoolkit/path.py | 294 ++- 1 file changed, 233 insertions(+), 61 deletions(-) diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py index 845dfe8..9401e99 100644 --- a/rtemstoolkit/path.py +++ b/rtemstoolkit/path.py @@

Re: RSB SPARC gdb 8.2.1 Build Issue on MSYS2 (64-bit)

ild? > > > > Is it supposed to be disabled and the host is not properly detected by > > the RSB? > > > > Not sure which way to push on the fix. > > Did you catch any specific error output from the build? > I didn't save it but recall something used uint as a type and

Re: RSB SPARC gdb 8.2.1 Build Issue on MSYS2 (64-bit)

On 6/4/19 12:59 AM, Joel Sherrill wrote: > Hi > > I was trying to build the sparc tools on MSYS2 today. SIS was enabled > by default and failed to build.  > > Is it expected to build? > > Is it supposed to be disabled and the host is not properly detected by > the

RSB SPARC gdb 8.2.1 Build Issue on MSYS2 (64-bit)

Hi I was trying to build the sparc tools on MSYS2 today. SIS was enabled by default and failed to build. Is it expected to build? Is it supposed to be disabled and the host is not properly detected by the RSB? Not sure which way to push on the fix. Thanks. --joel

Re: [PATCH] RSB: upgrade to sis 2.13 (was: Issue with sis and Leon3)

Jiri.. can't you push this yourself? :) FWIW The hash on rtems-tools needs a bump if it doesn't reflect the mailer fix I committed. Might as well have the next tools to catch both. On Sat, Mar 2, 2019, 2:50 PM Jiri Gaisler wrote: > The attached patch for RSB solves the problem of out

[PATCH] RSB: upgrade to sis 2.13 (was: Issue with sis and Leon3)

The attached patch for RSB solves the problem of output not being flushed in gdb/sis and run/sis.  Note that I would discourage the use of run as it cannot run the SMP tests. I have also experienced some random hangs in rtems-test when using run, but never with sis. Jiri. On 3/1/19 4:53 PM, Joel

Re: autotools build fail from rsb

-1/do-build error: building automake-1.12.6-x86_64-linux-gnu-1 See error report: rsb-report-automake-1.12.6-x86_64-linux-gnu-1.txt $ help2man --version GNU help2man 1.47.6 Copyright (C) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016

Re: autotools build fail from rsb

On 11/2/19 9:21 am, Gedare Bloom wrote: > It seems to be happening during Debian / Ubuntu builds of Qemu using RSB. Thanks for confirming this. I will take a look. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listi

Re: autotools build fail from rsb

It seems to be happening during Debian / Ubuntu builds of Qemu using RSB. On Sat, Feb 9, 2019 at 7:19 PM Joel Sherrill wrote: > What hosts and packages trip it best? Sorry. Just need a level set. > > On Sat, Feb 9, 2019, 6:14 PM Gedare Bloom >> Did we ever resolve this? >

Re: autotools build fail from rsb

What hosts and packages trip it best? Sorry. Just need a level set. On Sat, Feb 9, 2019, 6:14 PM Gedare Bloom Did we ever resolve this? > > Some students are encountering this again. > > On Mon, Mar 19, 2018 at 1:46 AM Chris Johns wrote: > >> On 19/03/2018 03:23, Vijay Kumar Banerjee wrote: >>

Re: autotools build fail from rsb

Did we ever resolve this? Some students are encountering this again. On Mon, Mar 19, 2018 at 1:46 AM Chris Johns wrote: > On 19/03/2018 03:23, Vijay Kumar Banerjee wrote: > > I have tried > > perl-5.24.3 > > On FreeBSD I have: > > ruru rtems $ type perl > perl is a tracked alias for

Re: [PATCH] RSB/gdb: upgrade sis to 2.11

On 5/2/19 9:17 pm, Jiri Gaisler wrote: > On 2/5/19 5:21 AM, Chris Johns wrote: >> On 4/2/19 9:49 pm, Jiri Gaisler wrote: >>> These two patches should be applied to gdb-8.2.1 to build sis for SPARC and >>> RISC-V: >> Thanks. >> >>> https://gaisler.se/gdb/gdb-8.2.1-riscv-config.patch >>> >>>

Re: [PATCH] RSB/gdb: upgrade sis to 2.11

On 2/5/19 5:21 AM, Chris Johns wrote: > On 4/2/19 9:49 pm, Jiri Gaisler wrote: >> These two patches should be applied to gdb-8.2.1 to build sis for SPARC and >> RISC-V: > Thanks. > >> https://gaisler.se/gdb/gdb-8.2.1-riscv-config.patch >> >> https://gaisler.se/gdb/gdb-8.2.1-sis-2.11.patch > I

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