Re: RSB build failure

t up the sparc/erc32 bsp on a new system and was > following the quickstart on the user manual. Though I have successfully > done this before, this time its throwing an error. PFA the rsb log file > with the error report. I was doing this to run the trace buff

Re: RSB build failure

.com> > wrote: > > Hello! > > I was trying to set up the sparc/erc32 bsp on a new system and was > following the quickstart on the user manual. Though I have successfully > done this before, this time its throwing an error. PFA the rsb log file > with the error report. I

Re: RSB build failure

; I was trying to set up the sparc/erc32 bsp on a new system and was following the quickstart on the user manual. Though I have successfully done this before, this time its throwing an error. PFA the rsb log file with the error report. I was doing this to run the trace buffering examples. > Why i

RSB build failure

Hello! I was trying to set up the sparc/erc32 bsp on a new system and was following the quickstart on the user manual. Though I have successfully done this before, this time its throwing an error. PFA the rsb log file with the error report. I was doing this to run the trace buffering examples

Re: RSB valid status check (was: Contribute to project)

Sir, I request you to please guide me whether I have done the task correctly or not and if something more is to be modified in this. If this is done correctly, please tell me how should I proceed further for the memory management project, which I was discussing earlier. Thanks and Regards

Re: RSB valid status check (was: Contribute to project)

Sir, I have tried to incorporate the changes suggested by you. I request you to please check the new patch file and guide me if some more improvement is needed to be done. Thanks and Regards Abhinav Jain On Tue, Feb 20, 2018 at 8:27 PM, Abhinav Jain wrote: > Sir, > >

Re: RSB valid status check (was: Contribute to project)

Sir, I will edit the current patch accordingly and will take care of this in the future. Thanks and Regards Abhinav Jain On Tue, Feb 20, 2018 at 7:31 PM, Gedare Bloom wrote: > Oops, I should read my mail better. Thanks for breaking this out Chris. > Abhinav, > > On Tue, Feb

[PATCH] rsb: Add '--patchdir' option description

According to commit d30be3129e9681a74efc80ce241aaf3c3a5b0efe in rtems-source-builder repo. Signed-off-by: Maksim E. Kozlov <maksim.e.koz...@gmail.com> --- rsb/commands.rst | 7 +++ 1 file changed, 7 insertions(+) diff --git a/rsb/commands.rst b/rsb/commands.rst index 3ef7772..ab338c1

Re: RSB valid status check (was: Contribute to project)

Oops, I should read my mail better. Thanks for breaking this out Chris. Abhinav, On Tue, Feb 20, 2018 at 1:12 AM, Abhinav Jain wrote: > Sir, > > I have attached the patch file with this mail. I have tried to follow all > the conventions that were listed in the User Git

Re: RSB valid status check (was: Contribute to project)

Sir, I have attached the patch file with this mail. I have tried to follow all the conventions that were listed in the User Git page. I request you to please check and guide me whether I have done it correctly or not or whether something more is to be done. Thanks and Regards Abhinav Jain On

Re: RSB valid status check (was: Contribute to project)

On 19/02/2018 21:19, Abhinav Jain wrote: > I have made the changes suggested by you in the code and hopefully, the issue > will be resolved as if the .git file is not found in the directory, the > process > will not go ahead and hence the wrong git repository will not be changed. Excellent.

Re: RSB valid status check (was: Contribute to project)

> > def valid(self): > > if path.exists(self.path): > > if path.exists(path.join(self.path, ".git")): > >ec, output = self._run(['status']) > >return ec == 0 > > return False > > I request you to please guide me wheth

RSB valid status check (was: Contribute to project)

me whether I proceeded in a right way or not. I am a little confused by the situation that leads to this happening. If the RSB is being run from a git repo and the build references a git repo the RSB will clone and update the repo so a 'valid' check to repo within the RSB's clone should not fail. Th

[PATCH] gcc: Use the RSB release for released tools.

Using the RSB release version for the gcc version string means the tools have a version string that matches the release. Close #3294 --- rtems/config/rtems-base.bset | 3 ++- source-builder/config/gcc-common-1.cfg | 9 + 2 files changed, 11 insertions(+), 1 deletion(-) diff

[PATCH] gcc: Use the RSB release for released tools.

Using the RSB release version for the gcc version string means the tools have a version string that matches the release. Close #3293 --- rtems/config/rtems-base.bset | 3 ++- source-builder/config/gcc-common-1.cfg | 9 + 2 files changed, 11 insertions(+), 1 deletion(-) diff

[PATCH] gcc: Use the RSB release for released tools.

Using the RSB release version for the gcc version string means the tools have a version string that matches the release. Close #3074 --- rtems/config/rtems-base.bset | 3 ++- source-builder/config/gcc-common-1.cfg | 9 + 2 files changed, 11 insertions(+), 1 deletion(-) diff

[PATCH] rsb: Minor fixes.

Close #2910 --- rsb/hosts.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rsb/hosts.rst b/rsb/hosts.rst index ba565d5..a4226f3 100644 --- a/rsb/hosts.rst +++ b/rsb/hosts.rst @@ -156,7 +156,7 @@ Mavericks The RSB works on Mavericks and the GNU tools can be built

[PATCH] sb: Backport from 4.11 the --rsb-file with releases fixes.

+ 1:] log.trace('url_file: %s' %(url_file)) for base in url_bases: +# +# Hack to fix #3064 where --rsb-file is being used. This code is a +# mess and should be refactored. +# +if version.released() and base == rtems_release_

[PATCH 4.10] Backport --rsb-file support for releases.

Add for long term support. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[4.11] RSB Fixes to fetch GCC parts from GNU's FTP server

Hi, These patches fix the initial patch to move to GNU's FTP site for the GGC parts used to build GCC. The patches back port from master the orphans check plus some SB modules needed to support the checker. It also includes the removal of unused RTEMS tools configurations and finally all

Re: RSB release's default mode for building kernels

On 16/01/18 23:35, Joel Sherrill wrote: On Tue, Jan 16, 2018 at 4:27 PM, Chris Johns > wrote: Hi, The current mode on all release branches is to build the RTEMS kernel. The purpose was to have a single command that builds the tools

Re: RSB release's default mode for building kernels

On Tue, Jan 16, 2018 at 4:27 PM, Chris Johns wrote: > Hi, > > The current mode on all release branches is to build the RTEMS kernel. The > purpose was to have a single command that builds the tools and RTEMS. > However > this means all BSPs for an architecture are built and

RSB release's default mode for building kernels

Hi, The current mode on all release branches is to build the RTEMS kernel. The purpose was to have a single command that builds the tools and RTEMS. However this means all BSPs for an architecture are built and this is not practical because it slows a build and uses a larger amount of disk space

[PATCH] Change RSB version from 4.12 to 5

--- source-builder/sb/version.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source-builder/sb/version.py b/source-builder/sb/version.py index da6aa02..0148614 100644 --- a/source-builder/sb/version.py +++ b/source-builder/sb/version.py @@ -35,7 +35,7 @@ import sources #

[PATCH] RSB - RISC-V: Add scripts to build RISC-V's simulator

Update #3109 --- bare/config/devel/spike-1.1.0.cfg | 21 bare/config/devel/spike.bset| 7 source-builder/config/spike-1-1.cfg | 64 + 3 files changed, 92 insertions(+) create mode 100644 bare/config/devel/spike-1.1.0.cfg create

Re: [PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain v2

On Fri, Oct 27, 2017 at 5:55 PM, Chris Johns <chr...@rtems.org> wrote: > On 27/10/2017 16:45, Sebastian Huber wrote: >> Thanks, committed. Even the Ada support works: >> >> riscv64-rtems4.12-gnat --version >> GNAT 7.2.0 20170814 (RTEMS 4.12, RSB >> 5

Re: [PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain v2

On 27/10/2017 16:45, Sebastian Huber wrote: > Thanks, committed. Even the Ada support works: > > riscv64-rtems4.12-gnat --version > GNAT 7.2.0 20170814 (RTEMS 4.12, RSB 5bd4aa6bb33872b0f0fb243e7fc2f0784e69ab81, > Newlib 2.5.0.20170922) > Copyright (C) 1996-2017, Free Softwa

Re: [PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain v2

Thanks, committed. Even the Ada support works: riscv64-rtems4.12-gnat --version GNAT 7.2.0 20170814 (RTEMS 4.12, RSB 5bd4aa6bb33872b0f0fb243e7fc2f0784e69ab81, Newlib 2.5.0.20170922) Copyright (C) 1996-2017, Free Software Foundation, Inc. This is free software; see the source for copying

[PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain v2

Update #3109 --- rtems/config/4.12/rtems-riscv64.bset | 16 1 file changed, 16 insertions(+) create mode 100644 rtems/config/4.12/rtems-riscv64.bset diff --git a/rtems/config/4.12/rtems-riscv64.bset b/rtems/config/4.12/rtems-riscv64.bset new file mode 100644 index

[PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain

From: Hesham Almatary Update #3109 --- rtems/config/4.12/rtems-riscv64.bset | 16 1 file changed, 16 insertions(+) create mode 100644 rtems/config/4.12/rtems-riscv64.bset diff --git a/rtems/config/4.12/rtems-riscv64.bset

Re: [PATCH] RSB: Update gdb-7.12 config to pull in latest sis patches

On 07/31/2017 02:21 PM, Sebastian Huber wrote: > On 31/07/17 14:18, Jiri Gaisler wrote: > >> Sorry - previous post had the wrong patch. Here is the correct one. > > Ok, could you please check that it is now all right. > It's perfect - thanks! Jiri.

Re: [PATCH] RSB: Update gdb-7.12 config to pull in latest sis patches

On 31/07/17 14:18, Jiri Gaisler wrote: Sorry - previous post had the wrong patch. Here is the correct one. Ok, could you please check that it is now all right. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax :

Re: [PATCH] RSB: Update gdb-7.12 config to pull in latest sis patches

Sorry - previous post had the wrong patch. Here is the correct one. Jiri. >From a5462f874eef326d47753abeffd2043034bccecf Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Sun, 30 Jul 2017 21:27:38 +0200 Subject: [PATCH] Update gdb-7.12 config to pull in latest sis patches. *

[PATCH] RSB: Update gdb-7.12 config to pull in latest sis patches

Please merge. >From b14821b4ac72913139cc1758e9757443f697a642 Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Sun, 30 Jul 2017 21:27:38 +0200 Subject: [PATCH] Update gdb-7.12 config to pull in latest sis patches. * Will make sure sis uses LMA rather than VMA when loading elf

rtems microblaze rsb build failure in 4.12

I try to build tools of microblaze by rsb, but I get failure when build newlib libm, the log is: /opt/rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.3.0-newlib-2.5.0.20170323-i686-linux-gnu-1/build/./gcc/xgcc -B/opt/rtems-source-builder/rtems/build/microblaze-rtems4.12-gcc-6.3.0

Re: [PATCH 1/1] RSB: Update gdb-7.12 config to pull in latest sis patches.

Sorry, forgot to add the patch. Should not be doing this on a Friday night ... :-) On 07/21/2017 10:24 PM, Jiri Gaisler wrote: > Can somebody review and merge this to RSB? > > Thanks, Jiri. > >From ae34bb8a2dedcff60ca25a83786c09d7bac3b794 Mon Sep 17 00:00:00 2001 From:

[PATCH 1/1] RSB: Update gdb-7.12 config to pull in latest sis patches.

Can somebody review and merge this to RSB? Thanks, Jiri. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: RSB Architecture request: aarch64, x86_64, risc-v

On Mon, Jun 26, 2017 at 8:39 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 26/06/17 02:28, Hesham Almatary wrote: > > On Mon, Jun 26, 2017 at 10:11 AM, Chris Johns wrote: >> >>> On 26/06/2017 10:03, Hesham Almatary wrote: >>> I've already submitted

Re: RSB Architecture request: aarch64, x86_64, risc-v

On 26/06/17 02:28, Hesham Almatary wrote: On Mon, Jun 26, 2017 at 10:11 AM, Chris Johns wrote: On 26/06/2017 10:03, Hesham Almatary wrote: I've already submitted a patch for riscv32 here [1]. Thanks. My reading of the thread there are some unresolved questions. What is

Re: RSB Architecture request: aarch64, x86_64, risc-v

Hi Chris, On Mon, Jun 26, 2017 at 10:11 AM, Chris Johns wrote: > On 26/06/2017 10:03, Hesham Almatary wrote: >> >> I've already submitted a patch for riscv32 here [1]. >> > > Thanks. My reading of the thread there are some unresolved questions. > > What is the status? >

Re: RSB Architecture request: aarch64, x86_64, risc-v

On 26/06/2017 10:03, Hesham Almatary wrote: > > I've already submitted a patch for riscv32 here [1]. > Thanks. My reading of the thread there are some unresolved questions. What is the status? Thanks Chris > [1] https://lists.rtems.org/pipermail/devel/2017-May/017951.html.

Re: RSB Architecture request: aarch64, x86_64, risc-v

4.12/rtems-all so these > tools > are always built when regression testing tool set changes. This change makes > sure the tools are in a suitable state for those looking to add support for > these architectures. > > To add RISC-V I need the architecture adde

RSB Architecture request: aarch64, x86_64, risc-v

the architecture added to the RSB. Could those working with this architecture to please considering post patches to this list list for review that adds this architecture. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: RSB Couverture-Qemu build queries

nload the patches. Let me know if > you need help merging them. > > Jiri. Great! I'll get to work on the patches today. Thanks Jiri. > >> >>> On 06/16/2017 03:13 PM, Cillian O'Donnell wrote: >>>> Hi, >>>> >>>> I am getting the RSB to bu

Re: RSB Couverture-Qemu build queries

up again, so you can download the patches. Let me know if you need help merging them. Jiri. > >> On 06/16/2017 03:13 PM, Cillian O'Donnell wrote: >>> Hi, >>> >>> I am getting the RSB to build Couverture-Qemu and I just want to check >>> a few things

Re: RSB Couverture-Qemu build queries

couverture-qemu > RTEMS Source Builder - Set Builder, 4.12 (14a801b3ceaa modified) > Build Set: devel/couverture-qemu > Build Set: devel/autotools-internal.bset > config: devel/autoconf-2.69-1.cfg > package: autoconf-2.69-x86_64-linux-gnu-1 > See error report: rsb-report-autoconf-2.69-x

Re: RSB Couverture-Qemu build queries

On 18 June 2017 at 03:23, Chris Johns <chr...@rtems.org> wrote: > On 17/6/17 6:38 am, Joel Sherrill wrote: >> >> >> On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell <cpodonne...@gmail.com >> <mailto:cpodonne...@gmail.com>> wrote: >> >>

Re: RSB Couverture-Qemu build queries

Joel, I've been talking with Fabien Chouteau from the Couverture project, I'll reach out to him with the patches and cc you and Chris and thanks Gedare for the info. > > On 06/16/2017 03:13 PM, Cillian O'Donnell wrote: >> Hi, >> >> I am getting the RSB to build Couverture-Qemu

Re: RSB Couverture-Qemu build queries

will try to sort it out. Jiri. On 06/16/2017 03:13 PM, Cillian O'Donnell wrote: > Hi, > > I am getting the RSB to build Couverture-Qemu and I just want to check > a few things I have done so far. > > 1. There are about 5 patches applied to the current qemu build. Only >

Re: RSB Couverture-Qemu build queries

On Fri, Jun 16, 2017 at 4:38 PM, Joel Sherrill <j...@rtems.org> wrote: > > > On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell <cpodonne...@gmail.com> > wrote: >> >> Hi, >> >> I am getting the RSB to build Couverture-Qemu and I just want to c

Re: RSB Couverture-Qemu build queries

On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > Hi, > > I am getting the RSB to build Couverture-Qemu and I just want to check > a few things I have done so far. > > 1. There are about 5 patches applied to the current qemu build. Onl

RSB Couverture-Qemu build queries

Hi, I am getting the RSB to build Couverture-Qemu and I just want to check a few things I have done so far. 1. There are about 5 patches applied to the current qemu build. Only one of which applies cleanly to the Couverture build. Do you want me to try and fix these up, comment them out

[PATCH 4/7] sb: Backport from master the '--rsb-file=' option.

: +url += [sp] +if len(url) == 0: +raise error.general('source URL not found: %s' % (' '.join(args))) +# +# Look for --rsb-file as an option we use as a local file name. +# This can be used if a URL has no reasonable

Re: rsb only download option

On 14/06/2017 01:18, punit vara wrote: > > Is there any way to download packages for rsb and then build locally > rather than downloading while installing rsb ? > > If there is no option for only download , I would suggest to provide > something like download all the package

Re: [PATCH] docs/rsb/configuration.rst: Fix typos, grammar.

On 14/06/2017 04:17, Cillian O'Donnell wrote: > --- > rsb/configuration.rst | 56 > +-- > 1 file changed, 28 insertions(+), 28 deletions(-) Pushed. Thank you. Chris ___ devel mailin

[PATCH] docs/rsb/configuration.rst: Fix typos, grammar.

--- rsb/configuration.rst | 56 +-- 1 file changed, 28 insertions(+), 28 deletions(-) diff --git a/rsb/configuration.rst b/rsb/configuration.rst index 62fc073..b2745a5 100644 --- a/rsb/configuration.rst +++ b/rsb/configuration.rst @@ -115,18

rsb only download option

Hi Is there any way to download packages for rsb and then build locally rather than downloading while installing rsb ? If there is no option for only download , I would suggest to provide something like download all the packages required for rsb and then developer can install it locally. Last

[PATCH 2/2] docs/rsb/quick-start.rst: Fix typos, hard coded paths, version

--- rsb/quick-start.rst | 242 ++-- 1 file changed, 121 insertions(+), 121 deletions(-) diff --git a/rsb/quick-start.rst b/rsb/quick-start.rst index f39c0a6..387ab61 100644 --- a/rsb/quick-start.rst +++ b/rsb/quick-start.rst @@ -42,13 +42,13

Re: GSOC: building RSB

Yes, it is not mandatory to use the RSB. However, the RSB helps ensure consistency across the community, and is easier to maintain and support than the variety of roll-your-own build scripts that each developer used to keep independently. On Sun, Apr 2, 2017 at 10:57 AM, faizan khan <faiza

GSOC: building RSB

I am using ubuntu and I have almost all the tools necessary. Can't I just build the RTEMS and run it via gdb on a target or QEMU... cheers, Faizan ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: qemu RSB bset with gcc 6.3.0

ch the patch link, the file names are of the form: > > gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7 > 52ecda6335add96494a178186bf7d490 > > And the RSB is fetching both as "gdate.c" > > How do I fetch these patches and specify the md5 sum? > > %patch ad

Re: qemu RSB bset with gcc 6.3.0

52ecda6335add96494a178186bf7d490 And the RSB is fetching both as "gdate.c" How do I fetch these patches and specify the md5 sum? %patch add glib https://git.gnome.org/browse/glib/patch/glib/gdate.c?id=0817af40e8c74c721c30f6ef482b1f53d12044c7 %hash md5 gdate.c?id=0817af40e8c74c721c30f6ef482b1f

Re: qemu RSB bset with gcc 6.3.0

On 15/02/2017 04:00, Joel Sherrill wrote: Hi Helping someone using Debian unstable which uses gcc 6.3.0. glib has code using strftime() which is now flagged and glib is compiled with -Werror. gdate.c:2497 in glib 2.39. On the glib master at github, it is line 2500 and the code is fixed with a

qemu RSB bset with gcc 6.3.0

Hi Helping someone using Debian unstable which uses gcc 6.3.0. glib has code using strftime() which is now flagged and glib is compiled with -Werror. gdate.c:2497 in glib 2.39. On the glib master at github, it is line 2500 and the code is fixed with a blame/comment in 2002. My first thought was

Re: Building toolset for Beaglebone with RSB fails (for me).

/gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-20160526.tar.bz2>: > error: No such file or directory> > error: downloading > ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-20160526.tar.bz2 > <ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-2

Re: Building toolset for Beaglebone with RSB fails (for me).

On 11/2/17 7:27 am, Alan Cudmore wrote: > I need to do the same for the Pi. I also noticed the Pi BSP Readme is > out of date. > Joel, where would we put instructions in the Sphinx documentation for > the Pi and BB? Please add a page under https://devel.rtems.org/wiki/Boards. Create a page such

Re: Building toolset for Beaglebone with RSB fails (for me).

t; ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-20160526.tar.bz2: >>> error: >> file or directory> >>> error: downloading >>> ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-20160526.tar.bz2: all >>> paths have failed, giving up >>>

Re: Building toolset for Beaglebone with RSB fails (for me).

2 >> download: ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-2016052 >> 6.tar.bz2: error: > pub/gcc/snapshots/6-20160526: No such file or directory> >> error: downloading ftp://gcc.gnu.org/pub/gcc/snap >> shots/6-20160526/gcc-6-20160526.tar.bz2: all paths have failed

Re: Building toolset for Beaglebone with RSB fails (for me).

ts/6-20160526/gcc-6- > 20160526.tar.bz2: error: pub/gcc/snapshots/6-20160526: No such file or directory> > error: downloading ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6- > 20160526.tar.bz2: all paths have failed, giving up > Build FAILED > See error report: rsb-report-

Building toolset for Beaglebone with RSB fails (for me).

ror report: rsb-report-arm-rtems4.12-gcc-6-20160526-newlib-2.4.0.20160527-x86_64-linux-gnu-1.txt error: downloading ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160526/gcc-6-20160526.tar.bz2: all paths have failed, giving up Build Set: Time 0:01:46.366099 Build FAILED Probably, the link is bro

Re: PATCH for RSB/gdb

ave attached the correct patch. > > Jiri. > > > On 14/11/16 13:58, Jiri Gaisler wrote: > > I have attached a patch for RSB/gdb-7.11 that brings the sis simulator > > up to date and adds support for leon2/3 emulation. Some seg-faults have > > also been fixed, a

Re: PATCH for RSB/gdb

The previous patch also contained a non-related fix to binutils, sorry for that. I have attached the correct patch. Jiri. On 14/11/16 13:58, Jiri Gaisler wrote: > I have attached a patch for RSB/gdb-7.11 that brings the sis simulator > up to date and adds support for leon2/3 emulation. So

PATCH for RSB/gdb

I have attached a patch for RSB/gdb-7.11 that brings the sis simulator up to date and adds support for leon2/3 emulation. Some seg-faults have also been fixed, and breakpoints and watchpoints work correctly with gdb and DDD now. The patch is pulled in from gaisler.org, and consists

Re: 4.10 RSB h8300 tools on CentOS 7

I should have mentioned. This is using the 4.10 branch of the RSB and not the rc1 candidate. I started doing this before you cut that. On Sun, Sep 4, 2016 at 7:02 PM, Chris Johns <chr...@rtems.org> wrote: > On 05/09/2016 04:46, Joel Sherrill wrote: > >> Hi >> >> &g

4.10 RSB h8300 tools on CentOS 7

Hi The h8300 tools fail to build on CentOS 7: /data/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/h8300-rtems4.10-gcc-4.4.7-newlib-1.18.0-x86_64-linux-gnu-1/build/./gcc/xgcc

Re: FYI - RSB tools and binutils 2.27

P.S. you may like to see if there is a recent newlib snapshot available or request one. On Thu, Aug 25, 2016 at 3:29 PM, Gedare Bloom wrote: > Sebastian has more than once suggested we bump to gcc6 snapshot > > On Thu, Aug 25, 2016 at 3:27 PM, Joel Sherrill

Re: FYI - RSB tools and binutils 2.27

Sebastian has more than once suggested we bump to gcc6 snapshot On Thu, Aug 25, 2016 at 3:27 PM, Joel Sherrill wrote: > Hi > > Just a note that I am testing updating the binutils version to this now. > > Is there a gcc bump needed also? > > --joel > >

FYI - RSB tools and binutils 2.27

Hi Just a note that I am testing updating the binutils version to this now. Is there a gcc bump needed also? --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[PATCH] Add Windows Subsystem for Linux to RSB Doc

+https://msdn.microsoft.com/en-us/commandline/wsl/install_guide + +Once WSL is installed, using the RTEMS Source Builder is nearly the same as +as using it on Ubuntu Linux 14.04. I had to install the following packages +to allow RSB to work on WSL + +--

Re: RSB toolchain builds on Windows 10/Windows Subsystem for Linux

hought I would try the new Windows Subsystem for Linux to see how the >> RSB toolchain build would go. >> WSL is a port of the Ubuntu 14.04 user space binaries to the windows 10 >> kernel: >> https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux >> >> The RSB

Corrected a typo in RSB docs

From 1ddfd35822be6c99cee644ed62a716f3cb371ddb Mon Sep 17 00:00:00 2001 From: Sambeet Panigrahi <b313...@iiit-bh.ac.in> Date: Mon, 1 Aug 2016 16:43:26 +0530 Subject: [PATCH] Corrected another typo in RSB Documentation --- doc/source-builder.txt | 2 +- 1 file changed, 1 insertion(+), 1 de

Re: [PATCH] RSB: update newlib version built with gcc-4.9.3

On 08/06/2016 23:51, Sebastian Huber wrote: Given the file name rtems-gcc-4.9.3-newlib-2.4.0-1.cf, how does this fit to the new file content? We have this *-N.cfg pattern throughout. What is the rule for the N? Is it useful at all? This was present when we had no branching in the repo to help

Re: [PATCH] RSB: update newlib version built with gcc-4.9.3

On 08/06/16 00:49, Hesham Almatary wrote: --- rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg b/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg index

[PATCH] RSB: update newlib version built with gcc-4.9.3

--- rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg b/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg index 596a4a7..42f6cfa 100644 ---

Re: rsb to build 4.10 tools with modern compilers (ie under MSYS2)

On 28/05/2016 1:04 AM, Worth Burruss wrote: Chris, If you would prefer this as a ticket let me know. Yes a ticket would be good. Thanks. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

rsb to build 4.10 tools with modern compilers (ie under MSYS2)

and ajusted it for 4.4.7 as attached. The second for GDB is a windows only patch where a function is defined twice under windows. The last patch adjusts the rsb to apply the patches and fix a missing checksum. I am sorry if these have been put up here before, but I could find no references through

Re: Skip Building a few packages by RSB

if adding or changing something for Rock to work. Say if RTEMS is missing something. --joel On May 27, 2016 5:43 AM, "Sambeet Panigrahi" <sambeet161...@gmail.com> wrote: Hi, I am working on porting Rock to RTEMS as a Summer of code project.I have to modify the code and build RTEMS

Skip Building a few packages by RSB

Hi, I am working on porting Rock to RTEMS as a Summer of code project.I have to modify the code and build RTEMS using RSB a lot many times. RSB is designed to clean install every time but building newlib and gcc each time is a very time consuming task. Is there a way I can select what packages

Re: RSB Git modified status

On Mon, Apr 18, 2016 at 5:31 PM, Chris Johns <chr...@rtems.org> wrote: > On 19/04/2016 02:34, Gedare Bloom wrote: >> >> I didn't quite follow. Is this to determine whether RSB should do >> something? > > > I am sorry, I should have provided more of a context.

Re: RSB Git modified status

modifies tracked files (short of a user hacking Makefile.in and configure files, too). This is what I also think. The RSB is unique because you can add a new file or a few files and use those but they would tend to result in different version numbers showing up in other parts. I will push a patc

Re: RSB Git modified status

On 19/04/2016 02:34, Gedare Bloom wrote: I didn't quite follow. Is this to determine whether RSB should do something? I am sorry, I should have provided more of a context. I guess this is caused by some bootstrap or configure that creates untracked files in a repo? Yes. What does

Re: RSB Git modified status

I didn't quite follow. Is this to determine whether RSB should do something? I guess this is caused by some bootstrap or configure that creates untracked files in a repo? What does it matter? On Sun, Apr 17, 2016 at 7:55 PM, Chris Johns <chr...@rtems.org> wrote: > Hi, > > At the

RSB Git modified status

Hi, At the moment the RSB says untracked files in a git repo is modified. Is this valid or this is a distraction? For example if I have 'x' as a file in the repo it is seen as untracked and so modified and nothing in the RSB has been changed. I am currently leaning to not modified. Chris

Re: [PATCH] [RSB] use updated newlib revision for or1k

.@rtems.org> wrote: > >> >> On Apr 10, 2016 7:11 PM, "Hesham Almatary" <heshamelmat...@gmail.com> >> wrote: >> > >> > This is the patch. It would conflict with Joel's [PATCH 3/5] >> 4.12/rtems-or1k.bset: Update newlib to 2.4.0, so we can c

Re: [PATCH] [RSB] use updated newlib revision for or1k

nflict with Joel's [PATCH 3/5] > 4.12/rtems-or1k.bset: Update newlib to 2.4.0, so we can choose either > according to the current RSB convention (releases or git revisions). > > The ports need to get to newlib 2.4.0. If I don't merge my patch, can you > bump the newlib version

Re: [PATCH] [RSB] use updated newlib revision for or1k

This is the patch. It would conflict with Joel's [PATCH 3/5] 4.12/rtems-or1k.bset: Update newlib to 2.4.0, so we can choose either according to the current RSB convention (releases or git revisions). On Wed, Mar 30, 2016 at 4:48 PM Stefan Wallentowitz <ste...@wallentowitz.de> wrote: > -

Re: [PATCH] [RSB] use updated newlib revision for or1k

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30.03.2016 07:29, Sebastian Huber wrote: > > > On 30/03/16 07:26, Stefan Wallentowitz wrote: >> there is also a GCC-6 snapshot available: >> https://github.com/openrisc/newlib/releases/tag/gcc6-preview >> >> This was the GCC version used in the

Re: [PATCH] [RSB] use updated newlib revision for or1k

On 30/03/16 07:26, Stefan Wallentowitz wrote: there is also a GCC-6 snapshot available: https://github.com/openrisc/newlib/releases/tag/gcc6-preview This was the GCC version used in the other architectures last week, so maybe it makes sense to bump to this GCC version, too. Are there any

Re: [PATCH] [RSB] use updated newlib revision for or1k

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Hesham, there is also a GCC-6 snapshot available: https://github.com/openrisc/newlib/releases/tag/gcc6-preview This was the GCC version used in the other architectures last week, so maybe it makes sense to bump to this GCC version, too. Best,

Re: [PATCH] [RSB] use updated newlib revision for or1k

b version is outdated (March 2015). >> >> Then this will fix one of the two repeating BSP build failures. :) > > If you can fix the sh4 BSP, then another gets knocked off. lol > > I guess the fix won't be the same. I checked RSB rtems-sh.bset and it's already using the latest gcc-6 and new

<    4   5   6   7   8   9   10   11   >