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

On Tue, Mar 29, 2016 at 6:08 PM, Hesham Almatary wrote: > Building RTEMS without this patch will fail with some nfs and rpc libs > since newlib version is outdated (March 2015). > > Then this will fix one of the two repeating BSP build failures. :) If you can fix the

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

Building RTEMS without this patch will fail with some nfs and rpc libs since newlib version is outdated (March 2015). On Wed, Mar 30, 2016 at 10:03 AM Joel Sherrill wrote: > I am OK with this if you want to push it. > > I guess you saw that I plan/hope to bump the newlib and gcc

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

I am OK with this if you want to push it. I guess you saw that I plan/hope to bump the newlib and gcc versions on all targets I can when the next newlib snapshot comes out. --joel On Tue, Mar 29, 2016 at 5:23 PM, Hesham Almatary wrote: > --- >

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

--- rtems/config/4.12/rtems-or1k.bset | 2 +- rtems/config/tools/rtems-gcc-4.9.3-newlib-git-1.cfg | 13 + 2 files changed, 14 insertions(+), 1 deletion(-) create mode 100644 rtems/config/tools/rtems-gcc-4.9.3-newlib-git-1.cfg diff --git

Re: AW: [PATCH] RSB fix host argument to waf for Cxc builds

On 26/03/2016 2:05 AM, mario.gru...@space.unibe.ch wrote: Not that I'm aware of. The PR is here: https://devel.rtems.org/ticket/2578 Thanks for the reminder. I have assigned the ticket to me. I will check Cxc builds next week. We need to have Cxc working for 4.11. Chris

AW: [PATCH] RSB fix host argument to waf for Cxc builds

gt; Cc: devel@rtems.org; Chris Johns <chr...@rtems.org> Betreff: Re: [PATCH] RSB fix host argument to waf for Cxc builds Was this resolved? On Fri, Jan 8, 2016 at 3:17 AM, Mario Gruber <mario.gru...@space.unibe.ch> wrote: > --- > rtems/config/tools/rtems-tools-common-1.cfg | 2

Re: [PATCH] RSB fix host argument to waf for Cxc builds

Was this resolved? On Fri, Jan 8, 2016 at 3:17 AM, Mario Gruber wrote: > --- > rtems/config/tools/rtems-tools-common-1.cfg | 2 +- > rtems/config/tools/rtems-tools-git-1.cfg| 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

On 25/03/2016 9:25 AM, Hesham Almatary wrote: On Thu, Mar 24, 2016 at 2:39 PM, Chris Johns wrote: On 23/03/2016 04:55, Gedare Bloom wrote: You can check them in. Let Joel/Chris know as they have been release testing 4.11 Hesham, sorry I have lost track of what is

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

On Fri, Mar 25, 2016 at 7:19 AM, Gedare Bloom wrote: > I checked them in. > Thanks Gedare > On Wed, Mar 23, 2016 at 11:39 PM, Chris Johns wrote: >> On 23/03/2016 04:55, Gedare Bloom wrote: >>> >>> >>> You can check them in. Let Joel/Chris know as they have

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

On Thu, Mar 24, 2016 at 2:39 PM, Chris Johns wrote: > On 23/03/2016 04:55, Gedare Bloom wrote: >> >> >> You can check them in. Let Joel/Chris know as they have been release >> testing 4.11 >> > > Hesham, sorry I have lost track of what is needed. Do clean patches exist to > make

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

I checked them in. On Wed, Mar 23, 2016 at 11:39 PM, Chris Johns wrote: > On 23/03/2016 04:55, Gedare Bloom wrote: >> >> >> You can check them in. Let Joel/Chris know as they have been release >> testing 4.11 >> > > Hesham, sorry I have lost track of what is needed. Do clean

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

On 23/03/2016 04:55, Gedare Bloom wrote: You can check them in. Let Joel/Chris know as they have been release testing 4.11 Hesham, sorry I have lost track of what is needed. Do clean patches exist to make the required changes for 4.11 and master? Thanks Chris

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22.03.2016 03:09, Hesham Almatary wrote: > Thanks Gedare. Both work fine with or1ksim and qemu. Hi, I have recently moved GCC forward to the GCC 6 snapshot the other architectures use. Should or1k also keep up with the most recent GCC development

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

Thanks Gedare. Both work fine with or1ksim and qemu. On Tue, Mar 22, 2016 at 11:30 AM, Gedare Bloom wrote: > Hi Hesham, > > I think the 4.12 patch is there. (updates 2669) > > On Mon, Mar 21, 2016 at 6:49 PM, Hesham Almatary > wrote: >> The patch

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

Hi Hesham, I think the 4.12 patch is there. (updates 2669) On Mon, Mar 21, 2016 at 6:49 PM, Hesham Almatary wrote: > The patch works fine for 4.11 branches on both or1ksim and qemu. 4.12 > patch will be really appreciated. > > On Mon, Mar 21, 2016 at 8:34 AM, Hesham

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

The patch works fine for 4.11 branches on both or1ksim and qemu. 4.12 patch will be really appreciated. On Mon, Mar 21, 2016 at 8:34 AM, Hesham Almatary wrote: > On Mon, Mar 21, 2016 at 8:24 AM, Stefan Wallentowitz > wrote: >> -BEGIN PGP

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

On Mon, Mar 21, 2016 at 8:24 AM, Stefan Wallentowitz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 20.03.2016 22:17, Hesham Almatary wrote: >> Hi Stefan, >> >> Thanks you! The gcc-4.8 patch was aging, so updating it is great. >> >> Have you had a chance

Re: [PATCH] [RSB 4.11] Bump OpenRISC versions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20.03.2016 22:17, Hesham Almatary wrote: > Hi Stefan, > > Thanks you! The gcc-4.8 patch was aging, so updating it is great. > > Have you had a chance to build the or1k BSP and run ticker or hello > on or1ksim with those new patches? > > Cheers,

[PATCH] [RSB 4.11] Bump OpenRISC versions

Bump the OpenRISC toolchain to newer versions. * Binutils to 2.26 * GCC to 4.9.3 * GDB to 7.9 updates #2668 --- rtems/config/4.11/rtems-or1k.bset | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/rtems/config/4.11/rtems-or1k.bset

[PATCH] [RSB 4.12/master] Bump OpenRISC versions

Bump the OpenRISC toolchain to newer versions. * Binutils to 2.26 * GCC to 4.9.3 * GDB to 7.11 updates #2669 --- rtems/config/4.12/rtems-or1k.bset | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/rtems/config/4.12/rtems-or1k.bset

[PATCH] [RSB] Bump OpenRISC versions

Hi all, the following patch bumps the tools in the OpenRISC toolchain to more recent versions. Beside this is replaces the patch sets to be applied to GCC and GDB with official releases from the OpenRISC Github repository. The patch should preferably go into branch 4.11 and the current

Re: Policy for RSB branches for 4.9, 4.10 and 4.11

On 28/02/16 00:07, Chris Johns wrote: Hi, Should we create branches for 4.9 and 4.10 in the RSB repo? Should the 4.9, 4.10 and 4.11 build set files and config scripts be removed from master? I do not see the point of maintaining the branches for releases and the master and I can see

Re: Policy for RSB branches for 4.9, 4.10 and 4.11

On 29/02/2016 01:48, Gedare Bloom wrote: I'm in favor, because I have observed new users building the 4.11 tools and not knowing they have to branch to 4.11 in rtems.git. Having to "branch" to get the 4.11 tools should help make the look-and-feel be consistent. Thanks for the feedback (and

Re: Policy for RSB branches for 4.9, 4.10 and 4.11

ms.org> wrote: > > On Feb 27, 2016 5:08 PM, "Chris Johns" <chr...@rtems.org> wrote: >> >> Hi, >> >> Should we create branches for 4.9 and 4.10 in the RSB repo? >> >> Should the 4.9, 4.10 and 4.11 build set files and config scripts be >> re

Re: Policy for RSB branches for 4.9, 4.10 and 4.11

On Feb 27, 2016 5:08 PM, "Chris Johns" <chr...@rtems.org> wrote: > > Hi, > > Should we create branches for 4.9 and 4.10 in the RSB repo? > > Should the 4.9, 4.10 and 4.11 build set files and config scripts be > removed from master? As long as we keep branches

Policy for RSB branches for 4.9, 4.10 and 4.11

Hi, Should we create branches for 4.9 and 4.10 in the RSB repo? Should the 4.9, 4.10 and 4.11 build set files and config scripts be removed from master? I do not see the point of maintaining the branches for releases and the master and I can see a situation where the 4.11 build on master, ie

Re: [PATCH] [RSB] update newlib git revision to get RTEMS dependency

Ok to commit. Thanks. On 25/02/2016 03:25, Hesham Almatary wrote: --- rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg | 2 +- rtems/config/tools/rtems-gcc-4.9.2-newlib-git-1.cfg | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] [RSB] update newlib git revision to get RTEMS dependency

--- rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg | 2 +- rtems/config/tools/rtems-gcc-4.9.2-newlib-git-1.cfg | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg b/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg

Re: RSB Quick Start Distributing and Archiving?

pre-built tools. This is not a typical use case for us as developers or self-supporting students. > [1] https://docs.rtems.org/rsb/#_distributing_and_archiving_a_build > > Gedare > ___ > devel mailing list > d

RSB Quick Start Distributing and Archiving?

Any particularly good reason for including the section "Distributing and Archiving A Build" [1] in the quick start? This seems to me to belong in its own section unrelated to a typical user's needs to just get a working tool chain. [1] https://docs.rte

Update gcc-version rsb for 4.11

Hi, The current version of the rsb loads the gcc-4.9.3 sources to build gcc. However as discussed previously Ada-support in this version is broken for RTEMS. The current 4.9-branch has a fix. Would it be possible to use a recent snapshot of this branch for the source builder until 4.9.4

Re: Update gcc-version rsb for 4.11

you, that seems to be a better way (I just overwrote the gcc-tarball of rsb with my own). However, I meant to suggest that we such a patch upstream in general. The current situation is that you can build a toolchain with Ada-support using the rsb, it will compile, but the programs it creates wil

Re: Update gcc-version rsb for 4.11

e you have to make the same change in your bset. >> > > Thank you, that seems to be a better way (I just overwrote the gcc-tarball of > rsb with my own). > However, I meant to suggest that we such a patch upstream in general. The > current situation is that you can bui

[PATCH] RSB fix host argument to waf for Cxc builds

--- rtems/config/tools/rtems-tools-common-1.cfg | 2 +- rtems/config/tools/rtems-tools-git-1.cfg| 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/rtems/config/tools/rtems-tools-common-1.cfg b/rtems/config/tools/rtems-tools-common-1.cfg index 60aa5c1..ae88021 100644 ---

Re: RSB rtems-4.12 gcc-6 dependent package version numbers.

On 5/01/2016 5:03 PM, Sebastian Huber wrote: > > I used the versions of the contrib/download_prerequisites script of the > GCC. The page https://gcc.gnu.org/install/prerequisites.html indicates later versions can be used. I cannot remember the reason these are selected. It may have been

Re: RSB rtems-4.12 gcc-6 dependent package version numbers.

On 05/01/16 09:45, Chris Johns wrote: On 5/01/2016 5:03 PM, Sebastian Huber wrote: > >I used the versions of the contrib/download_prerequisites script of the >GCC. The pagehttps://gcc.gnu.org/install/prerequisites.html indicates later versions can be used. I cannot remember the reason these

Re: RSB rtems-4.12 gcc-6 dependent package version numbers.

On 5/01/2016 7:48 PM, Sebastian Huber wrote: > On 05/01/16 09:45, Chris Johns wrote: >> On 5/01/2016 5:03 PM, Sebastian Huber wrote: >>> > >>> >I used the versions of the contrib/download_prerequisites script of the >>> >GCC. >> The pagehttps://gcc.gnu.org/install/prerequisites.html indicates

Re: RSB rtems-4.12 gcc-6 dependent package version numbers.

Hello Chris, I used the versions of the contrib/download_prerequisites script of the GCC. On 05/01/16 00:23, Chris Johns wrote: Hi Sebastian, Looking at 4.12 build in the RSB I see: mpfr2.4.2 mpc0.8.1 gmp4.3.2 The 4.11 gcc-4.9.3 is using: mpfr3.0.1 mpc

RSB rtems-4.12 gcc-6 dependent package version numbers.

Hi Sebastian, Looking at 4.12 build in the RSB I see: mpfr 2.4.2 mpc0.8.1 gmp4.3.2 The 4.11 gcc-4.9.3 is using: mpfr 3.0.1 mpc0.8.2 gmp5.0.5 4.12/rtems-arm builds on FreeBSD. Ok to update to the 4.11 versions? Chris

RSB release BSPs to build.

Hi, The RC1 of 4.11.0 builds all the BSPs for an arch by default. I am thinking of adding an option you can use to specify a list of BSPs to build. If a list is not provided should it default to them all? I am ok with this happening. Chris ___

[PATCH] [RSB] or1k: use newlib snapshot for rtems4.11

--- rtems/config/4.11/rtems-or1k.bset | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtems/config/4.11/rtems-or1k.bset b/rtems/config/4.11/rtems-or1k.bset index 2e6fb01..e600700 100644 --- a/rtems/config/4.11/rtems-or1k.bset +++ b/rtems/config/4.11/rtems-or1k.bset @@ -38,6

Re: [PATCH] [RSB] or1k: use newlib snapshot for rtems4.11

Pushed onto 4.11. Thanks. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Graphics RSB patches Was: GSoC - What's left to do?

Hello Qiao Yang, I have successfully tested RSB graphic with your patches for pc686 run in QEMU with minor tweak for source versions. RSB build setup ../source-builder/sb-set-builder \ --log=graphic-build-log.txt \ --prefix=/opt/rtems4.11 \ --rtems-bsp=i386/pc686 \ --with-rtems

Re: Trouble creating RSB Package: error copying tree

On 28/08/2015 3:01 am, Isaac Gutekunst wrote: > Hi Devel, > > I've been working on porting CANFestival to RTEMS. I ended up creating > some changes to CANFestival to allow it to be built against an RTEMS BSP. > > All was going well except a strange ldconfig error, when I tried to fix > it by

[PATCH] [RSB] gcc-4.8.3: Update newlib revision to catch include

--- rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg b/rtems/config/tools/rtems-gcc-4.8.3-newlib-git-1.cfg index 3a9e094..8456024 100644 ---

Broken link in RSB documentation

Hi, I found a broken link in the source builder documentation: https://docs.rtems.org/rsb/#_windows The ready to go windows tools link doesn't work. Hope this helps, Mohammed Khoory ___ devel mailing list devel@rtems.org http://lists.rtems.org

Trouble creating RSB Package: error copying tree

Hi Devel, I've been working on porting CANFestival to RTEMS. I ended up creating some changes to CANFestival to allow it to be built against an RTEMS BSP. All was going well except a strange ldconfig error, when I tried to fix it by removing the build directory

[PATCH 0/6] RSB Recipes for Add-On Packages

Hi I recently committed changes to update some of the contents of the rtems-addon-packages and get it all building again. This was the first step of migrating these into the RSB. Once I had them building as a baseline, I could write RSB recipes. In this patch series, they run the gamut from typo

[PATCH] [RSB] doc: zlib1g-dev package needs to be installed on Linux Mint

--- doc/source-builder.txt | 10 ++ 1 file changed, 10 insertions(+) diff --git a/doc/source-builder.txt b/doc/source-builder.txt index b5c7e3c..fa75fe1 100644 --- a/doc/source-builder.txt +++ b/doc/source-builder.txt @@ -3150,6 +3150,16 @@ The RTEMS Source Builder has been tested on

Re: RSB Ubuntu 15.04 64 bit fails to build.

On 12/08/2015 3:18 pm, punit vara wrote: I am facing problem with python .I installed python but don't know why still same problem .Can anybody tell me how to solve python dependencies in Ubuntu 15.04 64 bit. please find the attachment of error report.

Re: [RSB] port graphic libraries into rsb

Pisa, On Jul 19, 2015, at 10:35 PM, Pavel Pisa p...@cmp.felk.cvut.cz wrote: Hello Chris and Qiao Yang, On Monday 20 of July 2015 01:12:33 Chris Johns wrote: On 20/07/2015 6:55 am, QIAO YANG wrote: I've ported the graphic libraries into rsb so that we can build them much easier. All Build

Re: [RSB] port graphic libraries into rsb

Johns wrote: On 20/07/2015 6:55 am, QIAO YANG wrote: I've ported the graphic libraries into rsb so that we can build them much easier. All Build passed, tested on arm with raspberrypi and i386 with pc386. Fantastic and thank you. I use system wide prefix for my RTEMS install. When I

Re: [RSB] port graphic libraries into rsb

ported the graphic libraries into rsb so that we can build them much easier. All Build passed, tested on arm with raspberrypi and i386 with pc386. Fantastic and thank you. I use system wide prefix for my RTEMS install. When I specified that --prefix=/opt/rtems4.11 When I

[RSB] port graphic libraries into rsb

Hi Pavel Pisa, On Jul 19, 2015, at 10:35 PM, Pavel Pisa p...@cmp.felk.cvut.cz wrote: Hello Chris and Qiao Yang, On Monday 20 of July 2015 01:12:33 Chris Johns wrote: On 20/07/2015 6:55 am, QIAO YANG wrote: I've ported the graphic libraries into rsb so that we can build them much easier

Re: [RSB] port graphic libraries into rsb

On 20/07/2015 7:34 pm, Pavel Pisa wrote: Hello Chris and Qiao Yang, On Monday 20 of July 2015 01:12:33 Chris Johns wrote: On 20/07/2015 6:55 am, QIAO YANG wrote: I've ported the graphic libraries into rsb so that we can build them much easier. All Build passed, tested on arm

[PATCH 6/6] RSB: add nxlib bset

--- rtems/config/4.11/graphics/nxlib.bset | 20 ++ rtems/config/graphics/nxlib-0.47-dev-1.cfg | 19 + source-builder/config/nxlib-1.cfg | 62 ++ 3 files changed, 101 insertions(+) create mode 100644 rtems/config/4.11/graphics/nxlib.bset

[PATCH 5/6] RSB: add nanoX bset

--- rtems/config/4.11/graphics/microwindows.bset | 20 +++ rtems/config/graphics/microwindows-0.93-dev-1.cfg | 19 ++ source-builder/config/microwindows-1.cfg | 71 +++ 3 files changed, 110 insertions(+) create mode 100644

Re: [RSB] port graphic libraries into rsb

On 20/07/2015 6:55 am, QIAO YANG wrote: I've ported the graphic libraries into rsb so that we can build them much easier. All Build passed, tested on arm with raspberrypi and i386 with pc386. Fantastic and thank you. the libraries can be built with the command like: ../source

[PATCH 1/6] RSB : add libpng bset

rtems/config/4.11/graphics/libpng.bset| 20 ++ rtems/config/graphics/libpng-1.5.22-1.cfg | 22 +++ source-builder/config/libpng-1.cfg| 63 +++ 3 files changed, 105 insertions(+) create mode 100644 rtems/config/4.11/graphics/libpng.bset create

[PATCH 4/6] RSB: add t1lib bset (patch url should be changed after it is merged into rtems git server)

--- rtems/config/4.11/graphics/t1lib.bset | 20 ++ rtems/config/graphics/t1lib-5.1.2-1.cfg | 21 ++ source-builder/config/t1lib-1.cfg | 69 + 3 files changed, 110 insertions(+) create mode 100644 rtems/config/4.11/graphics/t1lib.bset create

[RSB Graphics Library] add patch for library source

Hi, I'm now working on moving the graphic libraries from rtems-graphic-tool-kits into rsb, based on the existing work for libjpeg and the rtems-graphic-tool-kits's buid script. The port of libpng, libtiff, freetype2 can be review on my github: https://github.com/yangqiao/rtems-source-builder

Re: [RSB Graphics Library] add patch for library source

Chris, Have we documented how to get custom patches working in RSB? I CC'ed Hesham too, since he has done this recently, he might have some advice. Gedare On Tue, Jun 30, 2015 at 3:24 AM, QIAO YANG yangqiao0...@me.com wrote: Hi, I'm now working on moving the graphic libraries from rtems

Re: [RSB Graphics Library] add patch for library source

On 6/30/2015 11:54 AM, Gedare Bloom wrote: Chris, Have we documented how to get custom patches working in RSB? I CC'ed Hesham too, since he has done this recently, he might have some advice. I don't know if it is documented. But if the upstage doesn't have a patch retrieval system

Re: [RSB Graphics Library] add patch for library source

On Tue, Jun 30, 2015 at 5:54 PM Gedare Bloom ged...@gwu.edu wrote: Chris, Have we documented how to get custom patches working in RSB? I CC'ed Hesham too, since he has done this recently, he might have some advice. There were two ways I used to get RSB fetch the patches: 1) An absolute

Re: [RSB Graphics Library] add patch for library source

On 1/07/2015 4:35 am, Joel Sherrill wrote: On 6/30/2015 11:54 AM, Gedare Bloom wrote: Chris, Have we documented how to get custom patches working in RSB? I CC'ed Hesham too, since he has done this recently, he might have some advice. I don't know if it is documented. But if the upstage

Re: [PATCH] [RSB] rtems-all.bset: add rtems-epiphany

On Fri, May 15, 2015 at 9:02 PM, Gedare Bloom ged...@gwu.edu wrote: What about h8300? Don't know about it and why it's not there, I can add it if that won't cause a problem. On Fri, May 15, 2015 at 7:51 AM, Hesham ALMatary heshamelmat...@gmail.com wrote: --- rtems/config/4.11/rtems-all.bset

RSB: Targets missing in rtems/config/4.11/rtems-all.bset

Hello, the following targets are missing in rtems/config/4.11/rtems-all.bset: epiphany h8300 Is this intentional? I was not able to build the moxie tool set. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax :

Re: RSB: Targets missing in rtems/config/4.11/rtems-all.bset

Hi, On Fri, May 15, 2015 at 12:28 PM, Sebastian Huber sebastian.hu...@embedded-brains.de wrote: Hello, the following targets are missing in rtems/config/4.11/rtems-all.bset: epiphany This is not intentional, I will submit a patch. h8300 Is this intentional? I was not able to build the

Re: [PATCH] [RSB] rtems-all.bset: add rtems-epiphany

What about h8300? On Fri, May 15, 2015 at 7:51 AM, Hesham ALMatary heshamelmat...@gmail.com wrote: --- rtems/config/4.11/rtems-all.bset | 1 + 1 file changed, 1 insertion(+) diff --git a/rtems/config/4.11/rtems-all.bset b/rtems/config/4.11/rtems-all.bset index 8a0fe82..6897e11 100644

Re: [PATCH] [RSB] Add support for building Epiphany tools

the master branch and users pick up the last know stable version. Contact me and I can explain if this is what you want. For building tools we aim to have a reliable, reproducible tool set. Dealing with moving targets makes it harder to support. That's possible. The problem is that the current RSB

[PATCH 1/2] [RSB] Modify GNU's common backend configuration files to build from external sources

--- source-builder/config/binutils-2-1.cfg | 6 -- source-builder/config/gcc-common-1.cfg | 7 +-- source-builder/config/gdb-7-1.cfg | 6 -- 3 files changed, 13 insertions(+), 6 deletions(-) diff --git a/source-builder/config/binutils-2-1.cfg

[PATCH 2/2] [RSB] Add support for building Epiphany tools

This patch adds support for building Epiphany tools. Currently the tools are fetched from Adapteva repositories. In the future, the tools should be fetched from GNU upstreams when Adapteva folks push their latest changes there. --- rtems/config/4.11/rtems-epiphany.bset | 48

Re: [PATCH] [RSB] Add support for building Epiphany tools

explain if this is what you want. For building tools we aim to have a reliable, reproducible tool set. Dealing with moving targets makes it harder to support. That's possible. The problem is that the current RSB doesn't support cloning from GitHub URLs like [1] or even [2]. [1] produce

Re: [PATCH] [RSB] Add support for building Epiphany tools

it harder to support. That's possible. The problem is that the current RSB doesn't support cloning from GitHub URLs like [1] or even [2]. [1] produce malforned URL (no protocol prefix), and [2] assumes that it's a .tar file, and doesn't even clone it. [1] g...@github.com:adapteva/epiphany

Re: [PATCH] [RSB] Add support for building Epiphany tools

then? For building tools we aim to have a reliable, reproducible tool set. Dealing with moving targets makes it harder to support. That's possible. The problem is that the current RSB doesn't support cloning from GitHub URLs like [1] or even [2]. [1] produce malforned URL (no protocol prefix), and [2

Re: [PATCH] [RSB] Add support for building Epiphany tools

. Dealing with moving targets makes it harder to support. About the error you got, I tested the patch and it's building fine on my Fedora OS. I'll have to clone another vanilla RSB repo, apply the patch, and test again. The reason I ask is no hashes are included and a warning is being generated

[PATCH] [RSB] Add support for building Epiphany tools

This patch adds support for building Epiphany tools. Currently the tools are fetched from Adapteva repositories. In the future, the tools should be fetched from GNU upstreams when Adapteva folks push their latest changes there. --- rtems/config/4.11/rtems-epiphany.bset | 43

Re: [PATCH] [RSB] or1k: correct the md5 hash of the GCC patch

Hi, This patch is needed, otherwise RSB wouldn't be able to build or1k toolchain. I was thinking of getting rid of this hash as this patch may be modified. Or, we can refer directly to the latest or1k gcc-4.9.2 [1] until they upstream it, as our patches are already applied there. [1] https

Re: [PATCH] [RSB] or1k: correct the md5 hash of the GCC patch

On 29/04/2015 8:05 pm, Hesham ALMatary wrote: This patch is needed, otherwise RSB wouldn't be able to build or1k toolchain. I was thinking of getting rid of this hash as this patch may be modified. Normally a patch does not change and you increment a minor number or change a date in the file

[PATCH] [RSB] or1k: correct the md5 hash of the GCC patch

--- rtems/config/4.11/rtems-or1k.bset | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rtems/config/4.11/rtems-or1k.bset b/rtems/config/4.11/rtems-or1k.bset index b486885..2e6fb01 100644 --- a/rtems/config/4.11/rtems-or1k.bset +++ b/rtems/config/4.11/rtems-or1k.bset @@ -17,7

Re: [PATCH] [RSB] Add support for building Epiphany tools

Hi Chris, On Tue, Apr 21, 2015 at 11:30 PM, Chris Johns chr...@rtems.org wrote: On 22/04/2015 2:33 am, Hesham ALMatary wrote: This patch adds support for building Epiphany tools. Great to see this support being adding. Currently some tools are fetched from my repositories (until my pull

Re: [PATCH] [RSB] Add support for building Epiphany tools

On Tue, Apr 21, 2015 at 11:30 PM, Chris Johns chr...@rtems.org wrote: On 22/04/2015 2:33 am, Hesham ALMatary wrote: This patch adds support for building Epiphany tools. Great to see this support being adding. Currently some tools are fetched from my repositories (until my pull requests get

[PATCH] [RSB] Add support for building Epiphany tools.

This patch adds support for building Epiphany tools. Currently some tools are fetched from my repositories (until my pull requests get merged), and other tools are fetched from Adapteva repositories. In the future, the tools should be fetched from GNU upstreams when Adapteva folks push their

Re: [PATCH] [RSB] Add support for building Epiphany tools

On 22/04/2015 2:33 am, Hesham ALMatary wrote: This patch adds support for building Epiphany tools. Great to see this support being adding. Currently some tools are fetched from my repositories (until my pull requests get merged), and other tools are fetched from Adapteva repositories. In

[PATCH] [RSB] Add support for building Epiphany tools

This patch adds support for building Epiphany tools. Currently some tools are fetched from my repositories (until my pull requests get merged), and other tools are fetched from Adapteva repositories. In the future, the tools should be fetched from GNU upstreams when Adapteva folks push their

Re: qemu fails to build with RSB on CentOS 6

On 17/04/2015 7:51 am, Joel Sherrill wrote: Has anyone seen this failure? $ make lt LINK vscclient /usr/bin/ld: -f may not be used without -shared collect2: ld returned 1 exit status make: *** [vscclient] Error 1 Is it related to ..

qemu fails to build with RSB on CentOS 6

Hi Has anyone seen this failure? $ make lt LINK vscclient /usr/bin/ld: -f may not be used without -shared collect2: ld returned 1 exit status make: *** [vscclient] Error 1 -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line

Re: qemu fails to build with RSB on CentOS 6

ld is really ld or gold? Version? El 16/4/2015 18:52, Joel Sherrill joel.sherr...@oarcorp.com escribió: Hi Has anyone seen this failure? $ make lt LINK vscclient /usr/bin/ld: -f may not be used without -shared collect2: ld returned 1 exit status make: *** [vscclient] Error 1 -- Joel

[PATCH] [RSB] Apply QEMU patch for openrisc that handles halt signals

--- bare/config/devel/qemu-git-1.cfg | 7 +++ 1 file changed, 7 insertions(+) diff --git a/bare/config/devel/qemu-git-1.cfg b/bare/config/devel/qemu-git-1.cfg index 82544d4..035cf59 100644 --- a/bare/config/devel/qemu-git-1.cfg +++ b/bare/config/devel/qemu-git-1.cfg @@ -8,6 +8,8 @@

[PATCH] [RSB] Apply QEMU patch for openrisc that handles halt signals

--- bare/config/devel/qemu-git-1.cfg | 7 +++ 1 file changed, 7 insertions(+) diff --git a/bare/config/devel/qemu-git-1.cfg b/bare/config/devel/qemu-git-1.cfg index 82544d4..035cf59 100644 --- a/bare/config/devel/qemu-git-1.cfg +++ b/bare/config/devel/qemu-git-1.cfg @@ -8,6 +8,8 @@

Re: [rsb error report] sb: Provide an unverified SSL context to the URL.

On 30/03/2015 11:24 am, QIAO YANG wrote: On Mar 30, 2015, at 08:01 AM, Chris Johns chr...@rtems.org wrote: On 30/03/2015 9:13 am, QIAO YANG wrote: Hello, I've just failed to build the rsb and found an error introduced by the latest commit: commit

Re: [rsb error report] sb: Provide an unverified SSL context to the URL.

On 30/03/2015 11:24 am, QIAO YANG wrote: On Mar 30, 2015, at 08:01 AM, Chris Johns chr...@rtems.org wrote: On 30/03/2015 9:13 am, QIAO YANG wrote: Hello, I've just failed to build the rsb and found an error introduced by the latest commit: commit

[rsb error report] sb: Provide an unverified SSL context to the URL.

Hello, I've just failed to build the rsb and found an error introduced by the latest commit: commit 3237c8ee69d7398c3d2ccade9879a3dde7785db1 Author: Chris Johns chr...@rtems.org Date: Sun Mar 29 15:35:00 2015 +1100 sb: Provide an unverified SSL context to the URL. The RTEMS servers

Re: [rsb error report] sb: Provide an unverified SSL context to the URL.

On 30/03/2015 9:13 am, QIAO YANG wrote: Hello, I've just failed to build the rsb and found an error introduced by the latest commit: commit 3237c8ee69d7398c3d2ccade9879a3dde7785db1 Author: Chris Johns chr...@rtems.org Date: Sun Mar 29 15:35:00 2015 +1100 sb: Provide

SIS Update to rtems-tools and RSB

Hi A patch with Jiri's patch set is waiting list moderator approval. With that committed, my RSB patches (1) update the newlib used to the current snapshot and (2) switch sparc gdb to gdb 7.9 and add Jiri's patch set. Jiri's patch set enables basic leon2 and leon3 executables to run

rsb build process - ftp error

Hi, I am trying to build RSB for sparc. During the installation, it is trying to download autoconf-2.69.tar.gz over ftp but fails. Autoconf is already installed in my host machine. Why is it trying again to download? Also I think there is some error with downloading via ftp - is there some way I

Re: rsb build process - ftp error

hit this with gcc, gdb and binutils. A patch is welcomed On Sat, Mar 21, 2015 at 7:05 AM, Joel Sherrill joel.sherr...@oarcorp.com wrote: On 3/20/2015 8:14 PM, Anand Krishnan wrote: Hi, I am trying to build RSB for sparc. During the installation, it is trying to download autoconf-2.69

Re: rsb build process - ftp error

is different. You will also hit this with gcc, gdb and binutils. A patch is welcomed On Sat, Mar 21, 2015 at 7:05 AM, Joel Sherrill joel.sherr...@oarcorp.com wrote: On 3/20/2015 8:14 PM, Anand Krishnan wrote: Hi, I am trying to build RSB for sparc. During the installation

Re: [PATCH] RSB: Fetch recent version of newlib that solves or1knd build failure.

the hash is not used and should be ignored (and removed). Git internally provides this type of functionality. I believe the hash is used by RSB to set a specific commit to use. +1 And I tested it, without this patch, it would get an earlier buggy newlib version. Sorry, my mistake. I thought

[PATCH] [RSB] Use gcc 5-20150301 snapshot.

Use newlib git repository and gcc snapshot that contains the latest moxie opcodes. Revert back to dtc-1.2.0 as dtc-1.4.1 would raise a compilation error. Note: This patch is unstable, and it's meant to be a temporary solution until the next gcc release,the build process may or may not fail!

<    5   6   7   8   9   10   11   >