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

On 04/02/2019 21:42, Joel Sherrill wrote: On Mon, Feb 4, 2019 at 2:40 PM Chris Johns > wrote: On 5/2/19 1:59 am, Joel Sherrill wrote: > > Should we also bump binutils to the release (2.32) from last week? > Have you tested them? :) Everyone's a

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

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 see in this patch `erc32` has been removed and

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

On Mon, Feb 4, 2019 at 2:40 PM Chris Johns wrote: > On 5/2/19 1:59 am, Joel Sherrill wrote: > > > > Should we also bump binutils to the release (2.32) from last week? > > > > Have you tested them? :) > Everyone's a comedian. :) --joel > > Chris >

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

On 5/2/19 1:59 am, Joel Sherrill wrote: > > Should we also bump binutils to the release (2.32) from last week?  > Have you tested them? :) Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

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

On Mon, Feb 4, 2019 at 4:56 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: > > > > https://gaisler.se/gdb/gdb-8.2.1-riscv-config.patch > > > >

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

On 4/2/19 9:02 pm, Jiri Gaisler wrote: > > On 2/4/19 10:23 AM, Sebastian Huber wrote: >> On 04/02/2019 10:16, Jiri Gaisler wrote: >>> On 2/4/19 9:02 AM, Jiri Gaisler wrote: On 2/4/19 8:00 AM, Chris Johns wrote: > On 3/2/19 8:38 pm, Jiri Gaisler wrote: >>  From

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

On 2/4/19 8:00 AM, Chris Johns wrote: > On 3/2/19 8:38 pm, Jiri Gaisler wrote: >> From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 >> From: Jiri Gaisler >> Date: Sun, 3 Feb 2019 10:04:00 +0100 >> Subject: [PATCH] gdb: upgrade sis to 2.11 >> >> * support RISC-V

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

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: > > https://gaisler.se/gdb/gdb-8.2.1-riscv-config.patch > > https://gaisler.se/gdb/gdb-8.2.1-sis-2.11.patch > > I have tested building and running all RTEMS tests -

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

On 2/4/19 10:23 AM, Sebastian Huber wrote: > On 04/02/2019 10:16, Jiri Gaisler wrote: >> On 2/4/19 9:02 AM, Jiri Gaisler wrote: >>> On 2/4/19 8:00 AM, Chris Johns wrote: On 3/2/19 8:38 pm, Jiri Gaisler wrote: >  From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 >

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

On 04/02/2019 10:16, Jiri Gaisler wrote: On 2/4/19 9:02 AM, Jiri Gaisler wrote: On 2/4/19 8:00 AM, Chris Johns wrote: On 3/2/19 8:38 pm, Jiri Gaisler wrote: From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 From: Jiri Gaisler Date: Sun, 3 Feb 2019 10:04:00 +0100 Subject:

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

On 2/4/19 9:02 AM, Jiri Gaisler wrote: > On 2/4/19 8:00 AM, Chris Johns wrote: >> On 3/2/19 8:38 pm, Jiri Gaisler wrote: >>> From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 >>> From: Jiri Gaisler >>> Date: Sun, 3 Feb 2019 10:04:00 +0100 >>> Subject: [PATCH] gdb: upgrade

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

On 2/4/19 8:58 AM, Sebastian Huber wrote: > On 04/02/2019 08:00, Chris Johns wrote: >> Are you OK if I add this patch to: >> >>   https://devel.rtems.org/ticket/3460 >> >> as an attachment so I can create `rtems-gdb-8.2.1-1.cfg`? I ask because >> `bfin` >> is broken with gdb-8.0.1 (in the sim

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

On 2/4/19 8:00 AM, Chris Johns wrote: > On 3/2/19 8:38 pm, Jiri Gaisler wrote: >> From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 >> From: Jiri Gaisler >> Date: Sun, 3 Feb 2019 10:04:00 +0100 >> Subject: [PATCH] gdb: upgrade sis to 2.11 >> >> * support RISC-V

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

On 04/02/2019 08:00, Chris Johns wrote: Are you OK if I add this patch to: https://devel.rtems.org/ticket/3460 as an attachment so I can create `rtems-gdb-8.2.1-1.cfg`? I ask because `bfin` is broken with gdb-8.0.1 (in the sim code) on FreeBSD 12.0-p2 ..

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

On 3/2/19 8:38 pm, Jiri Gaisler wrote: > From 72799748f8dca595f804dcf0efd566b3a88eb36e Mon Sep 17 00:00:00 2001 > From: Jiri Gaisler > Date: Sun, 3 Feb 2019 10:04:00 +0100 > Subject: [PATCH] gdb: upgrade sis to 2.11 > > * support RISC-V extension IMACFD > * fix broken erc32 memory

[PATCH] RSB/gdb: upgrade sis to 2.11

ols/rtems-gdb-ce73f310150418a9a1625ab60a527d959096a9e2.cfg +++ b/rtems/config/tools/rtems-gdb-ce73f310150418a9a1625ab60a527d959096a9e2.cfg @@ -11,7 +11,7 @@ %source set gdb --rsb-file=%{gdb_expand_name}.tar.gz https://codeload.github.com/RTEMS/sourceware-mirror-binutils-gdb/tar.gz/%{gdb_vers

Re: [PATCH] RSB: update sis with RISC-V and coverage support

Sorry, wrong patch attached. here is the correct one. Jiri. On 1/26/19 6:24 PM, Jiri Gaisler wrote: > Here is a patch for RSB that updates sis with RISC-V and coverage > support. The sis patch is pulled from gaisler.se which is hosted by a > professional web host service (binero.se), m

[PATCH] RSB: update sis with RISC-V and coverage support

Here is a patch for RSB that updates sis with RISC-V and coverage support. The sis patch is pulled from gaisler.se which is hosted by a professional web host service (binero.se), minimizing risks for any  down-time. The patch also bumps the version of rtems-tools so the latest covoar fixes

[PATCH 0/2] Patches for RSB 4.11 branch

Sebastian Huber (2): sb: Change Linux default prefix to "/opt" sb: Change default prefix source-builder/sb/linux.py | 1 + source-builder/sb/options.py | 6 ++ 2 files changed, 7 insertions(+) -- 2.16.4 ___ devel mailing list

Re: RSB documentation

On 17/1/19 7:15 pm, Sebastian Huber wrote: > > With respect to an example RTEMS application. Should we > > (1) suggest to check out the examples repository and start from here, or > > (2) should we provide a very simple Makefile based project? > > I tend to option (2) and just mention that the

Re: RSB documentation

On 17/01/2019 07:36, Chris Johns wrote: On 17/1/19 5:19 pm, Sebastian Huber wrote: On 17/01/2019 06:45, Chris Johns wrote: On 14/1/19 5:36 pm, Sebastian Huber wrote: I added a build of the partially restructured user manual here: https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf Any

Re: [PATCH] RSB: add RISC-V simulator to gdb

o gdb-8.2. The > SPARC build of RSB is also switched to gdb-8.2 to use the new simulator > as it provides both SPARC and RISC-V emulation. Thank for this. I only have an admin question. Should the patch be on a ticket to make sure it is available and tracked within RTEMS servers?

Re: RSB documentation

On 17/1/19 5:19 pm, Sebastian Huber wrote: > On 17/01/2019 06:45, Chris Johns wrote: >> On 14/1/19 5:36 pm, Sebastian Huber wrote: >>> I added a build of the partially restructured user manual here: >>> >>> https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf >>> >> Any HTML? > >

Re: RSB documentation

On 17/01/2019 06:45, Chris Johns wrote: Do we want to use "tool chain" or "tool set" or "tools" for the RTEMS things running on the host computer? Yeah good question. A "tool chain" seems to have a meaning, a compile etc, a "tool set&qu

Re: RSB documentation

On 17/01/2019 06:45, Chris Johns wrote: On 14/1/19 5:36 pm, Sebastian Huber wrote: I added a build of the partially restructured user manual here: https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf Any HTML? https://ftp.rtems.org/pub/rtems/people/sebh/user/index.html As an aside in

Re: RSB documentation

to the relevance for new users and how the >>> are used later during application development. I would use the RSB chapter >>> as >>> a reference chapter containing all the details and cover the common case in >>> the Quick Start chapter. So, I would move the RSB chapt

Re: [PATCH] RSB: add RISC-V simulator to gdb

On Wed, Jan 16, 2019 at 6:28 PM Chris Johns wrote: > On 17/1/19 5:18 am, Jiri Gaisler wrote: > > This patch adds the RISC-V version of the sis simulator to gdb-8.2. The > > SPARC build of RSB is also switched to gdb-8.2 to use the new simulator > > as it provides both SPARC

Re: [PATCH] RSB: add RISC-V simulator to gdb

On 17/1/19 5:18 am, Jiri Gaisler wrote: > This patch adds the RISC-V version of the sis simulator to gdb-8.2. The > SPARC build of RSB is also switched to gdb-8.2 to use the new simulator > as it provides both SPARC and RISC-V emulation. Thank for this. I only have an admin question

[PATCH] RSB: add RISC-V simulator to gdb

This patch adds the RISC-V version of the sis simulator to gdb-8.2. The SPARC build of RSB is also switched to gdb-8.2 to use the new simulator as it provides both SPARC and RISC-V emulation. diff --git a/rtems/config/5/rtems-sparc.bset b/rtems/config/5/rtems-sparc.bset index 187d337..8b13625

Re: RSB documentation

according to the relevance for new users and how the are used later during application development. I would use the RSB chapter as a reference chapter containing all the details and cover the common case in the Quick Start chapter. So, I would move the RSB chapter to the end after the Host

Re: RSB documentation

On 11/1/19 8:13 pm, Sebastian Huber wrote: > At which position in the manual should it be placed? I think we should > organize the chapters according to the relevance for new users and how the > are used later during application development. I would use the RSB chapter as > a refer

Re: RSB: Why is "/usr" the default prefix?

> On 12 Jan 2019, at 1:38 am, Sebastian Huber > wrote: > > why is "/usr" the default prefix? It is the same as the default for rpmbuild and the SpecBuilder was a copy of that tool. > RTEMS does not belong to the host system. I think it should be "/opt"

Re: RSB: Why is "/usr" the default prefix?

> >> "A further reason not to use the standard prefix is to allow more than one >> version of RTEMS to exist on your host machine at a time. The autoconf and >> automake tools required by RTEMS are not versioned and vary between the >> various versions of RTEMS. If you use a sing

Re: RSB: Why is "/usr" the default prefix?

; "A further reason not to use the standard prefix is to allow more than >> one version of RTEMS to exist on your host machine at a time. The autoconf >> and automake tools required by RTEMS are not versioned and vary between the >> various versions of RTEMS. If you use a sin

Re: RSB: Why is "/usr" the default prefix?

utoconf and > automake tools required by RTEMS are not versioned and vary between the > various versions of RTEMS. If you use a single prefix such as the standard > prefix there is a chance parts from a package of different versions may > interact. This should not happen but it can." > > I

Re: RSB: Why is "/usr" the default prefix?

from a package of different versions may interact. This should not happen but it can." I think this is quite inconvenient from RSB to use such a prefix. Why can't it use OS standard prefix (e.g. "/opt" or "/usr/local") + rtems + version, e.g. "/opt/rtems/5"

RSB: Why is "/usr" the default prefix?

Hello, why is "/usr" the default prefix? RTEMS does not belong to the host system. I think it should be "/opt" http://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s13.html#purpose14 or "/usr/local" http://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html#purpose24 -- Sebastian Huber, embedded

[PATCH] user: Add RSB content as a chapter

Sinne des EHUG. From 85d0ca332ec5c86f793fbc00654db889b3e9a786 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Fri, 11 Jan 2019 10:20:08 +0100 Subject: [PATCH] user: Add RSB content as a chapter Remove the separate RSB manual. --- rsb/conf.py | 14

Re: RSB documentation

- Am 10. Jan 2019 um 0:51 schrieb Chris Johns chr...@rtems.org: > On 10/1/19 3:41 am, Gedare Bloom wrote: >> I'm OK with this proposal.  We used to include quite messy details about how >> to >> bootstrap your own GCC in the user manual. This is a bit nicer. ;) At the &

Re: [PATCH 2/3] rsb: Move "Why Build from Source?" to own chapter

- Am 11. Jan 2019 um 0:23 schrieb Chris Johns chr...@rtems.org: > Hi, > > It has been while since I have read this. Some corrections if that is OK. :) Ok, I will first move it and then add your changes. ___ devel mailing list devel@rtems.org

Re: [PATCH 2/3] rsb: Move "Why Build from Source?" to own chapter

Hi, It has been while since I have read this. Some corrections if that is OK. :) Thanks Chris On 10/1/19 10:52 pm, Sebastian Huber wrote: > --- > rsb/index.rst | 1 + > rsb/source-builder.rst| 56 -------- > rsb/why-build-fro

[PATCH 2/3] rsb: Move "Why Build from Source?" to own chapter

--- rsb/index.rst | 1 + rsb/source-builder.rst| 56 rsb/why-build-from-source.rst | 59 +++ 3 files changed, 60 insertions(+), 56 deletions(-) create mode 100644 rsb/why-build-from

[PATCH 1/3] rsb: Move "History" to own chapter

Move it to the end of the document. It is auxiliary information. --- rsb/history.rst| 26 ++ rsb/index.rst | 23 --- rsb/source-builder.rst | 22 -- 3 files changed, 38 insertions(+), 33 deletions(-) create mode

Re: RSB documentation

On 10/1/19 3:41 am, Gedare Bloom wrote: > I'm OK with this proposal.  We used to include quite messy details about how > to > bootstrap your own GCC in the user manual. This is a bit nicer. ;) At the > maturity of RSB now, merging the doco with the User Manual is sensi

Re: RSB documentation

I'm OK with this proposal. We used to include quite messy details about how to bootstrap your own GCC in the user manual. This is a bit nicer. ;) At the maturity of RSB now, merging the doco with the User Manual is sensible. On Wed, Jan 9, 2019 at 5:55 AM Sebastian Huber < sebastian

RSB documentation

Hello, the RSB has currently its own manual in the documentation set: https://docs.rtems.org/branches/master/rsb/index.html I think it would make sense to move the RSB documentation into the user manual as a chapter. If you are new to RTEMS, then dealing with the RSB is one of the first

Re: RSB Problem with gdb-7.11

Thanks. That was what was needed. On Tue, Dec 11, 2018 at 6:01 PM Chris Johns wrote: > On 11/12/18 11:52 pm, Michael Westfall wrote: > > Hello, > > > > I was trying to use RSB to build the cross compiler toolchain for rtems > 4.10 / > > powerpc, and after a c

Re: RSB Problem with gdb-7.11

On 11/12/18 11:52 pm, Michael Westfall wrote: > Hello, > > I was trying to use RSB to build the cross compiler toolchain for rtems 4.10 / > powerpc, and after a couple of hours working (mostly spent building newlib), > RSB > failed with the following output: > config: tools

RSB Problem with gdb-7.11

Hello, I was trying to use RSB to build the cross compiler toolchain for rtems 4.10 / powerpc, and after a couple of hours working (mostly spent building newlib), RSB failed with the following output: config: tools/rtems-gdb-7.11-1.cfg package: powerpc-rtems4.10-gdb-7.11-x86_64-linux-gnu-1

[PATCH] rsb: Clarify Ada build requirements

--- rsb/building-tools-and-rtems.rst | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/rsb/building-tools-and-rtems.rst b/rsb/building-tools-and-rtems.rst index 5fd5d78..207463c 100644 --- a/rsb/building-tools-and-rtems.rst +++ b/rsb/building-tools-and-rtems.rst @@ -29,7

Re: RSB set-builder Creates File Named "0"

tems.org>> wrote: > > > >> Hi > >> > >> I have been seeing this for a couple of weeks. I decided to watch a > build > >> of the sparc > >> tools and see when it happened. I set a script to test for the > existence > >> o

Re: RSB set-builder Creates File Named "0"

his for a couple of weeks. I decided to watch a build >> of the sparc >> tools and see when it happened. I set a script to test for the existence >> of 0 and kill the set-builder. In the rtems/ subdirectory of the RSB, the >> script killed the set-builder wh

Re: RSB set-builder Creates File Named "0"

xistence > of 0 and kill the set-builder. In the rtems/ subdirectory of the RSB, the > script killed the set-builder when the gdb build started. So I think > something in the gdb bset file is creating this file. > > > It will be something related to the gdb python support I added

Re: RSB set-builder Creates File Named "0"

the rtems/ subdirectory of the RSB, the script > killed the set-builder when the gdb build started. So I think something in > the gdb bset file is creating this file. It will be something related to the gdb python support I added: https://git.rtems.org/rtems-source-builder/tree/source-build

RSB set-builder Creates File Named "0"

Hi I have been seeing this for a couple of weeks. I decided to watch a build of the sparc tools and see when it happened. I set a script to test for the existence of 0 and kill the set-builder. In the rtems/ subdirectory of the RSB, the script killed the set-builder when the gdb build started. So

Re: Spike Fails to Build on CentOS 7 (Possible RSB Issue)

e: > > > Hi > > > > > > Hesham was nice enough to bump the Spike version in the RSB so > others have a > > > chance of using it to test RISC-V executables. Unfortunately, it > now doesn't > > > build for me. I am not sure if thi

[PATCH v2 1/7] tester: Change the QEMU command line to match the RSB built QEMU.

From: Chris Johns The command line changed and the RSB is the newer version. Make the old version via a config variable. --- tester/rtems/testing/qemu.cfg | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tester/rtems/testing/qemu.cfg b/tester/rtems/testing/qemu.cfg

[PATCH 1/3] tester: Change the QEMU command line to match the RSB built QEMU.

From: Chris Johns The command line changed and the RSB is the newer version. Make the old version via a config variable. --- tester/rtems/testing/qemu.cfg | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tester/rtems/testing/qemu.cfg b/tester/rtems/testing/qemu.cfg

Re: Spike Fails to Build on CentOS 7 (Possible RSB Issue)

On 21/11/2018 03:43, Joel Sherrill wrote: > > > On Fri, Nov 16, 2018 at 6:57 PM Chris Johns <mailto:chr...@rtems.org>> wrote: > > On 17/11/18 1:45 am, Joel Sherrill wrote: > > Hi > > > > Hesham was nice enough to bump the

Re: Spike Fails to Build on CentOS 7 (Possible RSB Issue)

On Fri, Nov 16, 2018 at 6:57 PM Chris Johns wrote: > On 17/11/18 1:45 am, Joel Sherrill wrote: > > Hi > > > > Hesham was nice enough to bump the Spike version in the RSB so others > have a > > chance of using it to test RISC-V executables. Unfortunately, it now &g

Re: Spike Fails to Build on CentOS 7 (Possible RSB Issue)

On 17/11/18 1:45 am, Joel Sherrill wrote: > Hi > > Hesham was nice enough to bump the Spike version in the RSB so others have a > chance of using it to test RISC-V executables. Unfortunately, it now doesn't > build for me. I am not sure if this is a  > > ../source-builder/s

Re: qemu for riscv not in RSB

> rv64imafd_medany and found that > > > qemu-system-riscv* does not seem to be in our qemu RSB configuration. > > > > > > Where is this supposed to come from? Is it time to bump our qemu > > > configuration? > > > > I had to use the RISC-V Qemu rep

Spike Fails to Build on CentOS 7 (Possible RSB Issue)

Hi Hesham was nice enough to bump the Spike version in the RSB so others have a chance of using it to test RISC-V executables. Unfortunately, it now doesn't build for me. I am not sure if this is a ../source-builder/sb-set-builder --log=l-spike.txt --prefix=/home/joel/rtems-work/tools/5 devel

Re: qemu for riscv not in RSB

On Thu, 15 Nov 2018 at 06:05, Sebastian Huber wrote: > > On 14/11/2018 22:07, Joel Sherrill wrote: > > Hi > > > > I was trying to duplicate Sebastian's RISC-V testing for > > rv64imafd_medany and found that > > qemu-system-riscv* does not seem to be in our q

Re: qemu for riscv not in RSB

On 14/11/2018 22:07, Joel Sherrill wrote: Hi I was trying to duplicate Sebastian's RISC-V testing for rv64imafd_medany and found that qemu-system-riscv* does not seem to be in our qemu RSB configuration. Where is this supposed to come from? Is it time to bump our qemu configuration? I had

qemu for riscv not in RSB

Hi I was trying to duplicate Sebastian's RISC-V testing for rv64imafd_medany and found that qemu-system-riscv* does not seem to be in our qemu RSB configuration. Where is this supposed to come from? Is it time to bump our qemu configuration? Thanks --joel

Re: qemu build failure - RSB pkg-config failure

On 11/11/2018 00:24, Joel Sherrill wrote: > On CentOS 7, qemu and couverture variant fail to build. They end with this > which > I think indicates that pkg-config is invoked incorrectly. The RSB pkg-config now selects python3 or python2 depending on your set up. Ping me and we can be

Re: [PATCH] rsb: Update RISC-V's Spike revision

On 09/11/2018 21:22, Hesham Almatary wrote: > --- > bare/config/devel/spike-1.1.0.cfg | 4 ++-- > source-builder/config/spike-1-1.cfg | 20 ++-- > 2 files changed, 12 insertions(+), 12 deletions(-) OK to push. Chris ___ devel

qemu build failure - RSB pkg-config failure

[--prefix-variable PREFIX] [--static] [--dump] [lib [lib ...]] pkg-config: error: unrecognized arguments: zlib My RSB clone is up to date. Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[PATCH] rsb: Update RISC-V's Spike revision

--- bare/config/devel/spike-1.1.0.cfg | 4 ++-- source-builder/config/spike-1-1.cfg | 20 ++-- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/bare/config/devel/spike-1.1.0.cfg b/bare/config/devel/spike-1.1.0.cfg index 5b633fc..4e94189 100644 ---

Re: Strange RSB build failure

d129983b-x86_64-linux-gnu-1 > > Build FAILED >   See error report: > rsb-report-or1k-rtems5-gcc-4.9.3-newlib-08eab6396f678cf5e5968acaed0bae9fd129983b-x86_64-linux-gnu-1.txt > > error: building > or1k-rtems5-gcc-4.9.3-newlib-08eab6396f678cf5e5968acaed0bae9fd129983b-x86_64-linux-g

Strange RSB build failure

found building: or1k-rtems5-gcc-4.9.3-newlib-08eab6396f678cf5e5968acaed0bae9fd129983b-x86_64-linux-gnu-1 error: building or1k-rtems5-gcc-4.9.3-newlib-08eab6396f678cf5e5968acaed0bae9fd129983b-x86_64-linux-gnu-1 Build FAILED   See error report: rsb-report-or1k-rtems5-gcc-4.9.3-newlib

Re: [PATCH 0/3] De-dupe RSB and Users Guides

FYI the formatted output is at https://ftp.rtems.org/pub/rtems/people/joel/test-docs-20181012/ Review and comment. On Fri, Oct 12, 2018 at 2:29 PM Joel Sherrill wrote: > Hi > > The RSB and Users Guide had duplicative descriptions of the > same tasks as well as overlapping bu

[PATCH 1/3] Merge duplicative RSB Quick Start into Users Guide

--- rsb/building-tools-and-rtems.rst | 38 +++ rsb/index.rst| 2 +- rsb/quick-start.rst | 535 --- rsb/source-builder.rst | 37 ++- user/ecosys/index.rst| 156 user/hosts/os.rst

[PATCH 3/3] Move duplicate host configuration information from RSB to Users Guide

--- rsb/index.rst | 1 - user/hosts/macos.rst| 31 +++- user/hosts/posix.rst| 132 ++ user/hosts/windows.rst | 384 user/installation/developer.rst | 72 +++- 5 files changed, 383

[PATCH 0/3] De-dupe RSB and Users Guides

Hi The RSB and Users Guide had duplicative descriptions of the same tasks as well as overlapping but incomplete descriptions of host computer setup. This set of patches should result in their being one copy of this information in the Users Guide. This information may still need updating

RE: RSB download of MPC fails

Looks like m32c Thanks From: Joel Sherrill Sent: Tuesday, August 28, 2018 5:41 PM To: Jeff Mayes Cc: rtems-de...@rtems.org Subject: Re: RSB download of MPC fails On Tue, Aug 28, 2018 at 5:32 PM, Jeff Mayes mailto:jeff.ma...@oarcorp.com>> wrote: Hi all, Just trying out t

Re: RSB download of MPC fails

On Tue, Aug 28, 2018 at 5:40 PM, Joel Sherrill wrote: > > > On Tue, Aug 28, 2018 at 5:32 PM, Jeff Mayes > wrote: > >> Hi all, >> >> >> >> Just trying out the RSB and the --source-only-download option. >> >> Looks like MPC has a problem

Re: RSB download of MPC fails

On Tue, Aug 28, 2018 at 5:32 PM, Jeff Mayes wrote: > Hi all, > > > > Just trying out the RSB and the --source-only-download option. > > Looks like MPC has a problem. > > > > download: http://www.multiprecision.org/mpc/download/mpc-0.8.2.tar.gz -> > sour

RSB download of MPC fails

Hi all, Just trying out the RSB and the --source-only-download option. Looks like MPC has a problem. download: http://www.multiprecision.org/mpc/download/mpc-0.8.2.tar.gz -> sources/mpc-0.8.2.tar.gz download: http://www.multiprecision.org/mpc/download/mpc-0.8.2.tar.gz: error: HTTP Error

Re: error while building from RSB

>> >> >> >> >> >> >> On Fri, 15 Jun 2018 at 17:49, Vijay Kumar Banerjee >> >> wrote: >> >>> >> >>> Hello, >> >>> >> >>> While trying to freshly build RTEMS from RSB with the following >&g

Re: error while building from RSB

Vijay Kumar Banerjee > wrote: > > > > > > On Fri, 15 Jun 2018, 22:35 Cillian O'Donnell, > wrote: > >> > >> > >> > >> On Fri, 15 Jun 2018 at 17:49, Vijay Kumar Banerjee > >> wrote: > >>> > >>> Hello, >

Re: error while building from RSB

18 at 17:49, Vijay Kumar Banerjee >> wrote: >>> >>> Hello, >>> >>> While trying to freshly build RTEMS from RSB with the following command >>> >>> `../source-builder/sb-set-builder \ >>> --prefix=/home/lunatic/development/rtems

Re: error while building from RSB

On Fri, 15 Jun 2018, 22:35 Cillian O'Donnell, wrote: > > > On Fri, 15 Jun 2018 at 17:49, Vijay Kumar Banerjee < > vijaykumar9...@gmail.com> wrote: > >> Hello, >> >> While trying to freshly build RTEMS from RSB with the following command >> >> `.

error while building from RSB

Hello, While trying to freshly build RTEMS from RSB with the following command `../source-builder/sb-set-builder \ --prefix=/home/lunatic/development/rtems/5 5/rtems-sparc" I'm getting the following error : -- error: downloading https://gaisler.org/gdb/gdb-8.0.1-sis-leon2-leon3

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

On 21/02/2018 01:47, Maksim E. Kozlov wrote: > According to commit d30be3129e9681a74efc80ce241aaf3c3a5b0efe in > rtems-source-builder repo. > > Signed-off-by: Maksim E. Kozlov Pushed. Thank you. Chris ___ devel mailing list

Re: autotools build fail from rsb

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 /usr/local/bin/perl ruru rtems $ perl --version This is perl 5, version 24, subversion 3 (v5.24.3) built for amd64-freebsd-thread-multi I do not

Re: autotools build fail from rsb

perl is handling regex escaping where a newer perl >> causes an error when an older perl caused a warning. Since we are kind >> of stuck with an older automake, you should install an older perl. >> Apparently, something before 5.26.0 should work I guess. >> >> -Gedare >

Re: autotools build fail from rsb

s://lists.gnu.org/archive/html/bug-automake/2017-06/msg3.html >> >> The problem is how perl is handling regex escaping where a newer perl >> causes an error when an older perl caused a warning. Since we are kind >> of stuck with an older automake, you should install an ol

Re: autotools build fail from rsb

s how perl is handling regex escaping where a newer perl > causes an error when an older perl caused a warning. Since we are kind > of stuck with an older automake, you should install an older perl. > Apparently, something before 5.26.0 should work I guess. > > -Gedare > > >>> > On Mar 17, 2018

Re: autotools build fail from rsb

d a warning. Since we are kind of stuck with an older automake, you should install an older perl. Apparently, something before 5.26.0 should work I guess. -Gedare >>> > On Mar 17, 2018 11:34 AM, "Vijay Kumar Banerjee" >>> > <vijaykumar9...@gmail.com> >>>

Re: autotools build fail from rsb

gt; > wrote: >> >> >> >> hello , >> >> >> >> As suggested by Gedare , I have started this thread on the build error >> >> that I'm getting . >> >> >> >> I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while >> >> trying >> >> to build autotools from rsb >> >> >> >> I'm using fedora 27 64bit . >> >> >> >> P.S: the error report is attached >> >> >> >> -- vijay > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: autotools build fail from rsb

: > >> > >> hello , > >> > >> As suggested by Gedare , I have started this thread on the build error > >> that I'm getting . > >> > >> I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while > trying > >> to build

Re: autotools build fail from rsb

> hello , >> >> As suggested by Gedare , I have started this thread on the build error >> that I'm getting . >> >> I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while trying >> to build autotools from rsb >> >> I'm using fedora 27 64bit . &g

Re: RSB build failure

>Interesting. Please raise a ticket, set the component to rsb and assign to me. I will take a look next week. I cannot remember if I deleted the source tarball on MacOS and tested this. Done. The ticket is #3355 Best, Vidushi On Sun, Mar 18, 2018 at 9:07 AM, Chris Johns <chr...@rtems.org&

Re: RSB build failure

yesterday. Though in the > process I had another error which I managed to deal with. PFA the attached > report. Its about the relocation of the libexpat to github. I manually > downloaded the tar file and put it in the required sources folder. > Interesting. Please raise a ticket, set t

Re: RSB build failure

s/2.7/bin/python > >> checking for python2.7... no > >> configure: error: python is missing or unusable > > > > That looks like the problem (at least on the surface). macOS does come > with > > Python built-in, but I don't believe that's good enough for de

Re: RSB build failure

e surface). macOS does come with > Python built-in, but I don't believe that's good enough for development The default Python is fine for use with GDB and the RSB. There is no problem with the default provided by Apple on MacOS. $ uname -a Darwin huia 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec

autotools build fail from rsb

hello , As suggested by Gedare , I have started this thread on the build error that I'm getting . I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while trying to build autotools from rsb I'm using fedora 27 64bit . P.S: the error report is attached -- vijay RTEMS Tools Project

Re: RSB build failure

>> If so, could you confirm that you have the python2.7 binary in your PATH >> variable too? >> >> On Sat, Mar 17, 2018 at 3:24 PM Vidushi Vashishth <reachv...@gmail.com> >> wrote: >> >> > Hello! >> >> > I was trying to set up the spar

<    3   4   5   6   7   8   9   10   11   >