n when released.
> +#
> +%if %{rsb_released}
> + %define rtems_net_services_version %{rsb_version}
> + %define rtems_net_services_ext xz
> + %define rtems_waf_ext xz
> +%else
> + %define rtems_net_services_ext bz2
> + %define rtems_waf_ext bz2
> +%endif
> +
> +#
> +#
From: Chris Johns
- Zynq ARM fixes
- AARCH64 MMU fix
- Updated imxrt drivers
- x86_64 EFI support
- Flash driver
- Updated validation tests
- Microblaze updates
---
rtems/config/tools/rtems-kernel-6.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Chris Johns
- Add getaddrinfom, gai_strerror, ipv6_addr, if_nametoindex and BSD programs
- Update sysctl
- Move legacy net
---
rtems/config/tools/rtems-net-legacy-6.cfg | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rtems/config/tools/rtems-net-legacy-6.cfg
BSP support.
+#
+%include rtems-bsp.cfg
+
+#
+# Net services Source.
+#
+# If not a release collect and install rtems_waf as cgit snapshots to not
+# capture submodules.
+#
+# Releases package submodules in the top level tarfile.
+#
+%source set rtems_net_services
--rsb-file=rtems-net-services
Am 30.04.23 um 23:53 schrieb Chris Johns:
On 29/4/2023 3:48 am, o...@c-mauderer.de wrote:
Hello Joel,
Am 28.04.23 um 00:19 schrieb Joel Sherrill:
On Wed, Apr 26, 2023 at 7:06 PM Chris Johns mailto:chr...@rtems.org>> wrote:
Hi,
All RSB repo commits need to be posted for
On 29/4/2023 3:48 am, o...@c-mauderer.de wrote:
> Hello Joel,
>
> Am 28.04.23 um 00:19 schrieb Joel Sherrill:
>>
>>
>> On Wed, Apr 26, 2023 at 7:06 PM Chris Johns > <mailto:chr...@rtems.org>> wrote:
>>
>> Hi,
>>
>> Al
Hello Joel,
Am 28.04.23 um 00:19 schrieb Joel Sherrill:
On Wed, Apr 26, 2023 at 7:06 PM Chris Johns <mailto:chr...@rtems.org>> wrote:
Hi,
All RSB repo commits need to be posted for review and independent
approval given
before being pushed to the top level repo.
On 27.04.23 20:05, Gedare Bloom wrote:
On Thu, Apr 27, 2023 at 3:27 AM Karel Gardas wrote:
On 4/27/23 08:13, Sebastian Huber wrote:
Why
don't we use a Git pull request workflow with CI pipelines in the RTEMS
Project?
I don't know, but certainly github.com is not available as an
open-source
On 28/4/2023 4:05 am, Gedare Bloom wrote:
> On Thu, Apr 27, 2023 at 3:27 AM Karel Gardas wrote:
>> On 4/27/23 08:13, Sebastian Huber wrote:
>>> Why
>>> don't we use a Git pull request workflow with CI pipelines in the RTEMS
>>> Project?
>>
>> I don't know, but certainly github.com is not
On Wed, Apr 26, 2023 at 7:06 PM Chris Johns wrote:
> Hi,
>
> All RSB repo commits need to be posted for review and independent approval
> given
> before being pushed to the top level repo.
>
I thought this was the policy for all top level repositories. There is a
degree of t
On Thu, Apr 27, 2023 at 3:27 AM Karel Gardas wrote:
>
> On 4/27/23 08:13, Sebastian Huber wrote:
> > Why
> > don't we use a Git pull request workflow with CI pipelines in the RTEMS
> > Project?
>
> I don't know, but certainly github.com is not available as an
> open-source solution which may be
On 4/27/23 08:13, Sebastian Huber wrote:
Why
don't we use a Git pull request workflow with CI pipelines in the RTEMS
Project?
I don't know, but certainly github.com is not available as an
open-source solution which may be seen as a major roadblock. Am I right
assuming that GitLab Community
On 27/4/2023 4:13 pm, Sebastian Huber wrote:
> what is your (or the RTEMS Project in general) plan to maintain the tools and
> ensure that we can use up to date versions of Newlib, GCC, Binutils, and GDB?
> This involves building the latest versions, reviewing build issues, reporting
> bugs,
Hello Chris,
what is your (or the RTEMS Project in general) plan to maintain the
tools and ensure that we can use up to date versions of Newlib, GCC,
Binutils, and GDB? This involves building the latest versions, reviewing
build issues, reporting bugs, writing patches, etc. Currently, I do
Hi,
All RSB repo commits need to be posted for review and independent approval given
before being pushed to the top level repo.
Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
OK to push
Thanks
Chris
On 31/1/2023 1:44 am, Joel Sherrill wrote:
> Closes #4555.
> ---
> rtems/config/5/rtems-aarch64.bset| 4
> rtems/config/5/rtems-all.bset| 2 --
> rtems/config/5/rtems-microblaze.bset | 3 ---
> rtems/config/5/rtems-tier-4.bset | 1 -
> 4 files
ok
On Mon, Jan 30, 2023 at 7:44 AM Joel Sherrill wrote:
>
> Closes #4555.
> ---
> rtems/config/5/rtems-aarch64.bset| 4
> rtems/config/5/rtems-all.bset| 2 --
> rtems/config/5/rtems-microblaze.bset | 3 ---
> rtems/config/5/rtems-tier-4.bset | 1 -
> 4 files changed, 10
Closes #4555.
---
rtems/config/5/rtems-aarch64.bset| 4
rtems/config/5/rtems-all.bset| 2 --
rtems/config/5/rtems-microblaze.bset | 3 ---
rtems/config/5/rtems-tier-4.bset | 1 -
4 files changed, 10 deletions(-)
delete mode 100644 rtems/config/5/rtems-aarch64.bset
delete
Thanks Frank and Chris. I pushed the patch.
Best regards
Christian
On 2023-01-20 22:53, Chris Johns wrote:
OK to push.
Thanks
Chris
On 21/1/2023 2:06 am, Frank Kuehndel wrote:
From: Frank Kühndel
Close #4642
---
source-builder/sb/ereport.py | 4 +++-
1 file changed, 3 insertions(+), 1
OK to push.
Thanks
Chris
On 21/1/2023 2:06 am, Frank Kuehndel wrote:
> From: Frank Kühndel
>
> Close #4642
> ---
> source-builder/sb/ereport.py | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/source-builder/sb/ereport.py b/source-builder/sb/ereport.py
> index
From: Frank Kühndel
Close #4642
---
source-builder/sb/ereport.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/source-builder/sb/ereport.py b/source-builder/sb/ereport.py
index d8fb5f6..52ee2eb 100755
--- a/source-builder/sb/ereport.py
+++ b/source-builder/sb/ereport.py
From: Frank Kühndel
Hello,
this is the promised patch to close my bug report #4642
https://devel.rtems.org/ticket/4642
"RSB: log.py tends to remove relevant error messages".
I tested it using Christian's Github CI - see his Email:
https://lists.rtems.org/pipermail/devel/2023-Janu
On 20/1/2023 3:13 am, Frank Kühndel wrote:
> Hi Joel,
>
> On 1/19/23 15:08, Joel Sherrill wrote:
>> Subject:
>> Re: [PATCH 1/1] RSB: Mitigate too short error reports
>> From:
>> Joel Sherrill
>> Date:
>> 1/19/23, 15:08
>>
>> To:
Hi Joel,
On 1/19/23 15:08, Joel Sherrill wrote:
Subject:
Re: [PATCH 1/1] RSB: Mitigate too short error reports
From:
Joel Sherrill
Date:
1/19/23, 15:08
To:
Frank Kühndel
CC:
Chris Johns , devel@rtems.org
On Thu, Jan 19, 2023 at 6:47 AM Frank Kühndel <
frank.kuehn...@embedded-brains
On Thu, Jan 19, 2023 at 6:47 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:
> Hello Chris,
> Hello Joel,
>
> On 1/16/23 18:27, Joel Sherrill wrote:
> > Subject:
> > Re: [PATCH 1/1] RSB: Mitigate too short error reports
> > From:
> > J
Hello Chris,
Hello Joel,
On 1/16/23 18:27, Joel Sherrill wrote:
Subject:
Re: [PATCH 1/1] RSB: Mitigate too short error reports
From:
Joel Sherrill
Date:
1/16/23, 18:27
To:
Frank Kühndel
CC:
Chris Johns , devel@rtems.org
On Mon, Jan 16, 2023 at 8:46 AM Frank Kühndel <
frank.ku
On Mon, Jan 16, 2023 at 8:46 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:
> Hi Chris,
>
> On 1/16/23 01:02, Chris Johns wrote:
> > Subject:
> > Re: [PATCH 1/1] RSB: Mitigate too short error reports
> > From:
> > Chris Johns
> > D
Hi Chris,
On 1/16/23 01:02, Chris Johns wrote:
Subject:
Re: [PATCH 1/1] RSB: Mitigate too short error reports
From:
Chris Johns
Date:
1/16/23, 01:02
To:
Frank Kühndel , devel@rtems.org
On 22/12/2022 9:09 pm, Frank Kühndel wrote:
On 12/21/22 00:06, Chris Johns wrote:
On 21/12/2022 3:44 am
r of lines that is always updating. Your attention and interest
around this feature highlights how problematic it is so maybe it is simpler and
better to remove it and we leave users to find the error in the log file.
I am happy to accept the report has not worked as a feature, remove it and in
the process we recover some overheads in the logging area of the RSB?
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 12/21/22 00:06, Chris Johns wrote:
On 21/12/2022 3:44 am, Frank Kuehndel wrote:
From: Frank Kühndel
Close #4642
---
source-builder/sb/ereport.py | 4
1 file changed, 4 insertions(+)
diff --git a/source-builder/sb/ereport.py b/source-builder/sb/ereport.py
index d8fb5f6..d391917
OK to push
Thanks
Chris
On 21/12/2022 3:37 am, Joel Sherrill wrote:
> The ports did not get contributed until during 6 development and are
> not on this release branch.
>
> Closes #4555.
> ---
> rtems/config/5/rtems-aarch64.bset| 4
> rtems/config/5/rtems-all.bset| 2 --
>
On 21/12/2022 3:44 am, Frank Kuehndel wrote:
> From: Frank Kühndel
>
> Close #4642
> ---
> source-builder/sb/ereport.py | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/source-builder/sb/ereport.py b/source-builder/sb/ereport.py
> index d8fb5f6..d391917 100755
> ---
From: Frank Kühndel
Hello Chris,
I am making an attempt to close my bug report #4642
https://devel.rtems.org/ticket/4642
"RSB: log.py tends removes relevant error messages".
The difficulty seems to be to find a rather short text indicating
that the relevant error can sometimes be
From: Frank Kühndel
Close #4642
---
source-builder/sb/ereport.py | 4
1 file changed, 4 insertions(+)
diff --git a/source-builder/sb/ereport.py b/source-builder/sb/ereport.py
index d8fb5f6..d391917 100755
--- a/source-builder/sb/ereport.py
+++ b/source-builder/sb/ereport.py
@@ -55,6
The ports did not get contributed until during 6 development and are
not on this release branch.
Closes #4555.
---
rtems/config/5/rtems-aarch64.bset| 4
rtems/config/5/rtems-all.bset| 2 --
rtems/config/5/rtems-microblaze.bset | 3 ---
3 files changed, 9 deletions(-)
delete
@@ URL: http://www.microwindows.org/
#
# nxlib Source
#
-%source set nxlib https://github.com/alex-sever-h/nxlib.git
+%source set nxlib --rsb-file=nxlib-%{nxlib_version}.zip \
+ https://github.com/alex-sever-h/nxlib/archive/%{nxlib_version}.zip
#
# Prepare the source code.
diff
/download.py
@@ -132,9 +132,7 @@ def _hash_check(file_, absfile, macros, remove = True):
if hasher is not None:
del hasher
else:
-if version.released():
-raise error.general('%s: no hash found in released RSB' % (file_))
-log.warning('%s: no hash found
-#
-%source set mpfr
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
-
%patch add gcc
--rsb-file=Make-lang.in
On 15/11/22 3:22 am, Gedare Bloom wrote:
> ok thanks for sorting this out, and for linking the patch through
> trac. You've given me one more thing to check for in RSB patches that
> reference %patch command :)
Thanks for the review and yeah sorry about the extra bit to check. It cannot
ok thanks for sorting this out, and for linking the patch through
trac. You've given me one more thing to check for in RSB patches that
reference %patch command :)
On Sun, Nov 13, 2022 at 5:02 PM wrote:
>
> From: Chris Johns
>
> The 5.7.2.1 patch referenced in the configuration ca
From: Sebastian Huber
Close #4754
---
source-builder/config/gdb-common-1.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source-builder/config/gdb-common-1.cfg
b/source-builder/config/gdb-common-1.cfg
index 397d44d..b9dd47f 100644
---
From: Chris Johns
The 5.7.2.1 patch referenced in the configuration can be located
so update the version to the latest. Checked with Zynq A9 qemu
and libbsd.
Closes #4758
---
rtems/config/net-mgmt/net-snmp-5.7.2.1-1.cfg | 32 -
rtems/config/net-mgmt/net-snmp-5.9.3.cfg | 48
5.0.5
-
-#
-# Project custom message
-#
-%define gcc_version_message
RSB-%{_sbgit_id})-%{release},gcc-%{gcc_version}/newlib-%{newlib_version}
-
-%define with_threads 0
-%define with_plugin 0
-
-%ifn %{defined with_iconv}
-%define with_iconv 1
-%endif
-
-# Incompatible with Texinfo 5
confidence if all builds pass well.
What I did to my clean config in order to compile RSB is:
- install xz (from homebrew is fine), side effect of this is you will
get Apple's command line developer tools installed too -- which you need.
- compile python3.10 from source -- you need to enable
to my clean config in order to compile RSB is:
- install xz (from homebrew is fine), side effect of this is you will
get Apple's command line developer tools installed too -- which you need.
- compile python3.10 from source -- you need to enable SSL on it
otherwise RSB would not be able
On 11/6/22 22:42, Chris Johns wrote:
indeed, the report here is probably minimal thing I should do.
Sebastian has pushed updates to the tools to the RSB. Did you happen to pick up
those?
Not at all! I'm still on:
https://git.rtems.org/rtems-source-builder/commit/?id
On 7/11/2022 5:38 am, Karel Gardas wrote:
>
> Side note before answering : the email was motivated by the fact that I
> provided
> few patches to RSB to make that working well on Monterey running on M1. This
> was
> just few weeks ago so I know, this was running well. Last
Side note before answering : the email was motivated by the fact that I
provided few patches to RSB to make that working well on Monterey
running on M1. This was just few weeks ago so I know, this was running
well. Last week I've updated to Ventura and things felt apart. Hence the
report
Karel Gardas wrote:
>
> Folks,
>
> upgraded to Ventura from Monterey and this breaks RSB for unknown
> reason. The issue looks like segfault/internal compiler error in GCC
> while compiling newlib.
>
> 6/rtems-sparc:
>
>CC libc/stdlib/libc_a-strtoll_
Folks,
upgraded to Ventura from Monterey and this breaks RSB for unknown
reason. The issue looks like segfault/internal compiler error in GCC
while compiling newlib.
6/rtems-sparc:
CC libc/stdlib/libc_a-strtoll_r.o
CC libm/complex/libm_a-cpowf.o
../../../../gnu-mirror-gcc
gdb_external 1
%define gdb_expand_name sourceware-mirror-binutils-gdb-%{gdb_version}
%source set gdb --rsb-file=%{gdb_expand_name}.tar.gz
https://codeload.github.com/RTEMS/sourceware-mirror-binutils-gdb/tar.gz/%{gdb_version}
%hash sha512 %{gdb_expand_name}.tar.gz \
-
drh71JaHy
From: Chris Johns
Updates #4717
---
rtems/config/rtems-bsp.cfg | 55 --
1 file changed, 41 insertions(+), 14 deletions(-)
diff --git a/rtems/config/rtems-bsp.cfg b/rtems/config/rtems-bsp.cfg
index 801cd5c..af9ad3d 100644
--- a/rtems/config/rtems-bsp.cfg
+++
From: Chris Johns
- Always stage a build
- Install if installable and outter most buildset instance
Closes #4731
---
source-builder/sb/setbuilder.py | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/source-builder/sb/setbuilder.py
Hi,
If these changes are OK I will push the same patches to the devel
branch.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
From: Chris Johns
Closes #4734
---
source-builder/sb/execute.py | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/source-builder/sb/execute.py b/source-builder/sb/execute.py
index f470aba..e3809ec 100755
--- a/source-builder/sb/execute.py
+++
K3U43C1bsMxDDGRqD6fwtrEFoEgqVFX63IuQ==
> # Comment above related to #4657 and patches ends here
>
> -%define newlib_version d9dc880
> +%define newlib_version 01f6251c0
> %define newlib_external 1
> %define newlib_expand_name sourceware-mirror-newlib-cygwin-%{newlib_version}
> %sou
01f6251c0
%define newlib_external 1
%define newlib_expand_name sourceware-mirror-newlib-cygwin-%{newlib_version}
%source set newlib --rsb-file=newlib-%{newlib_version}.tar.gz \
https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/%{newlib_version}
-%hash sha512
s
Chris
> %define newlib_external 1
> %define newlib_expand_name sourceware-mirror-newlib-cygwin-%{newlib_version}
> %source set newlib --rsb-file=newlib-%{newlib_version}.tar.gz \
>
> https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/%{
01f6251c0969f92bf802e1c9f2acd199353a3956
%define newlib_external 1
%define newlib_expand_name sourceware-mirror-newlib-cygwin-%{newlib_version}
%source set newlib --rsb-file=newlib-%{newlib_version}.tar.gz \
https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz
From: Chris Johns
Updates #4716
---
source-builder/sb/setbuilder.py | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/source-builder/sb/setbuilder.py b/source-builder/sb/setbuilder.py
index 1452aca..9836e9b 100644
--- a/source-builder/sb/setbuilder.py
+++
From: Chris Johns
- Check and optionally support arch/bsp format 'with_rtems_bsp' defines
Updates #4717
---
rtems/config/tools/rtems-kernel-common.cfg | 49 +-
1 file changed, 39 insertions(+), 10 deletions(-)
diff --git a/rtems/config/tools/rtems-kernel-common.cfg
From: Chris Johns
- This is a bug introduced in the recent bset tar file changes
Updates #4716
---
source-builder/sb/setbuilder.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/source-builder/sb/setbuilder.py b/source-builder/sb/setbuilder.py
index 36fca46..1452aca
From: Chris Johns
- Add rtems/config to the config directories searched to better
support deployment
- Correctly expand the configdir and path searchs
Updates #4716
---
source-builder/defaults.mc | 2 +-
source-builder/sb/config.py | 52 ++---
2 files
From: Chris Johns
- Make a single tarfile for all buildsets built
- Use the staging tree as the tarfile source
- Use python's tarfile module
- Create a config.file object without loading a .cfg file
Updates #4716
---
source-builder/sb/config.py | 5 +--
source-builder/sb/setbuilder.py
From: Chris Johns
Updates #4716
---
source-builder/sb/setbuilder.py | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/source-builder/sb/setbuilder.py b/source-builder/sb/setbuilder.py
index 16e8cc8..55bd86f 100644
--- a/source-builder/sb/setbuilder.py
+++
Hi
These patches are a mix of back ported fixed from our devel branch
and deployment support for RTEMS 5.
I have a personal repo I will upload soon that tests RTEMS 5 as well
as RTEMS 6 (devel branch).
Chris
___
devel mailing list
devel@rtems.org
Hi,
These patches add support to build GNU sed if it is not avaliable on
a host. GCC requires GNU sed or weird things happen. Ticket #2300
details a MIPS build failure that has existed in GCC for years
where the multilib processing depends on GNU sed.
The simplest solution is to check and if sed
Hi,
These patches fix the BSP buildset files to use arch/bsp.
There are some other fixes building the BSPs exposed.
v2:
Remove the extra defines from the bsp buildsets
Chris
___
devel mailing list
devel@rtems.org
Hi,
These patches fix the BSP buildset files to use arch/bsp.
There are some other fixes building the BSPs exposed.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 9/9/2022 3:53 pm, Chris Johns wrote:
> On 9/9/2022 3:50 pm, Sebastian Huber wrote:
>> On 09.09.22 07:49, Chris Johns wrote:
>>> On 9/9/2022 3:30 pm, Sebastian Huber wrote:
>>>> Hello,
>>>>
>>>> it seems that the recent RSB no
On 9/9/2022 3:50 pm, Sebastian Huber wrote:
> On 09.09.22 07:49, Chris Johns wrote:
>> On 9/9/2022 3:30 pm, Sebastian Huber wrote:
>>> Hello,
>>>
>>> it seems that the recent RSB no longer runs with Python 2.7:
>>>
>>> download:https://c
On 09.09.22 07:49, Chris Johns wrote:
On 9/9/2022 3:30 pm, Sebastian Huber wrote:
Hello,
it seems that the recent RSB no longer runs with Python 2.7:
download:https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/6678700:
error:
https should be ok with python2?
My default "p
On 9/9/2022 3:30 pm, Sebastian Huber wrote:
> Hello,
>
> it seems that the recent RSB no longer runs with Python 2.7:
>
> download: https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/6678700:
> error:
https should be ok with python2?
> Is it now time to drop the Pyth
Hello,
it seems that the recent RSB no longer runs with Python 2.7:
download:
https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/6678700: error:
Is it now time to drop the Python 2 support entirely?
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
Thanks for adding this. Please push.
Chris
On 9/9/2022 3:18 pm, Sebastian Huber wrote:
> Update #4560.
> ---
> user/rsb/project-sets.rst | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/user/rsb/project-sets.rst b/user/rsb/project-sets.rst
> index 54
Update #4560.
---
user/rsb/project-sets.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/user/rsb/project-sets.rst b/user/rsb/project-sets.rst
index 54a3f8e..ce839c5 100644
--- a/user/rsb/project-sets.rst
+++ b/user/rsb/project-sets.rst
@@ -116,6 +116,15 @@ build sets
---
rtems/config/tools/rtems-tools-6.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-tools-6.cfg
b/rtems/config/tools/rtems-tools-6.cfg
index d7522fd..14ee346 100644
--- a/rtems/config/tools/rtems-tools-6.cfg
+++
mpfr_url https://ftp.gnu.org/gnu/mpfr
+
+#
+# Project custom message
+#
+%define gcc_version_message GCC
%{release}-RSB(%{_sbgit_id}),gcc-%{gcc_version}/newlib-%{newlib_version}
+
+#
+# The gcc/newlib build instructions. We use 4.6 Release 1.
+#
+%include %{_configdir}/gcc-4.6-1.cfg
diff --git a/bare
From: Chris Johns
Updates #4716
---
source-builder/sb/build.py | 18 +++-
source-builder/sb/config.py | 161 ++--
source-builder/sb/setbuilder.py | 39 ++--
3 files changed, 133 insertions(+), 85 deletions(-)
diff --git a/source-builder/sb/build.py
uilds:
-del b
-except error.general as gerr:
-if not build_error:
-log.stderr(str(gerr))
-raise
-except KeyboardInterrupt:
-raise
- except:
-self.build_failure = 'RSB general failure'
-
Hi,
These patches update the RSB 5 branch with fixes for getting
sources that are on the development branch.
Getting sources is used to create a release. The release process
fetches all the referenced sources in the RSB and they are
part of the release.
Chris
Hi,
These patches update the RSB to support deployment. With this change you can
create a directory anywhere and in it add a buildset file and build an RTEMS
vertical software stack. For example:
mkdir project
cd project
mkdir config
vi config/project.bset
And in the buildset file add
n.
>
>
> Thanks. I didn't expect a question to turn into a quest for you.
Haha .. it had to be done or the release scripts do not work unless on an RSB
branch with a cleaned up set of buildset and config files.
> Is this for 5 and 6?
Both. The release scripts are tagged and not br
On Tue, Aug 16, 2022, 6:34 PM wrote:
> Hi
>
> These patches fix getting sources for all the packages so releases
> can be CI tested to catch breakages closer to the time they happen.
>
Thanks. I didn't expect a question to turn into a quest for you.
Is this for 5 and 6?
> The get sources
Hi
These patches fix getting sources for all the packages so releases
can be CI tested to catch breakages closer to the time they happen.
The get sources tool now finds the top level buildset files and only
fetches the sources for them. This avoids processing and handling
configurations that are
Update #4560.
---
user/rsb/project-sets.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/user/rsb/project-sets.rst b/user/rsb/project-sets.rst
index 54a3f8e..ce839c5 100644
--- a/user/rsb/project-sets.rst
+++ b/user/rsb/project-sets.rst
@@ -116,6 +116,15 @@ build sets
On 21/7/2022 3:21 pm, Sebastian Huber wrote:
> On 20.07.22 22:52, Chris Johns wrote:
>> On 20/7/2022 6:20 pm, Sebastian Huber wrote:
>>> On 20/07/2022 10:11, Chris Johns wrote:
>> Are these TLS allocations in newlib based on a single use of a newlib
>> call
>> that
>> brings in
On 20.07.22 22:52, Chris Johns wrote:
On 20/7/2022 6:20 pm, Sebastian Huber wrote:
On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call that
brings in the reent stuff? How does that work?
No, each TLS object is defined in the
On 20/7/2022 6:20 pm, Sebastian Huber wrote:
> On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call
that
brings in the reent stuff? How does that work?
>>> No, each TLS object is defined in the translation unit which
On 20/07/2022 10:11, Chris Johns wrote:
There seems to be an issue with i386:
08:09:56 runner ['/opt/rtems/6/bin/rtems-ld', '-C',
'/opt/rtems/6/bin/i386-rtems6-gcc', '-c', '-MMD -Wall -Wmissing-prototypes
-Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs
-mtune=pentiumpro
On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call that
brings in the reent stuff? How does that work?
No, each TLS object is defined in the translation unit which uses the object.
The goal is to get only those objects linked in
est which tests some Newlib
> details.
https://github.com/RTEMS/sourceware-mirror-newlib-cygwin/tree/master/newlib/testsuite
I have never looked at them but I thought it was worth asking.
>> Did the switch to TLS exceptions end up on 6? I cannot see anything in the
>> RSB
>> c
of newlib's tests been run? Can we run newlib tests?
Are there Newlib tests? We added a newlib01 test which tests some Newlib
details.
Did the switch to TLS exceptions end up on 6? I cannot see anything in the RSB
commit history mentioning it.
No, I wait for your feedback. Here is a back port
em.
Which archs in the list have you run the testsuite on?
Has any of newlib's tests been run? Can we run newlib tests?
Did the switch to TLS exceptions end up on 6? I cannot see anything in the RSB
commit history mentioning it.
Are these TLS allocations in newlib based on a single use of a new
On 13/07/2022 11:24, Sebastian Huber wrote:
This makes the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE)
Newlib configuration option available.
Any comments with respect to using the Newlib thread-local storage
configuration option for arm, i386, microblaze, nios2, powerpc,
%define newlib_expand_name sourceware-mirror-newlib-cygwin-%{newlib_version}
%source set newlib --rsb-file=newlib-%{newlib_version}.tar.gz
https://codeload.github.com/RTEMS/sourceware-mirror-newlib-cygwin/tar.gz/%{newlib_version}
-%hash sha512 newlib-%{newlib_version}.tar.gz
Use the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE) Newlib
configuration option on all targets which support thread-local storage.
Update #4560.
---
rtems/config/6/rtems-aarch64.bset| 1 +
rtems/config/6/rtems-arm.bset| 1 +
rtems/config/6/rtems-i386.bset |
Update #4560.
---
source-builder/config/gcc-common-1.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/source-builder/config/gcc-common-1.cfg
b/source-builder/config/gcc-common-1.cfg
index 694a1f3..f6ec883 100644
--- a/source-builder/config/gcc-common-1.cfg
+++
Hi,
This patch applies the fix for non-TLS eh_globals archs. See:
https://devel.rtems.org/ticket/4661
https://gcc.gnu.org/bugzilla/attachment.cgi?id=53103
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
that I know of and this patch enables the support by default. The RSB
> incorrectly supported the configure `--enable-lto` option. That option
> controls
> the host build and when enabled the built host executables are built with
> LTO.
>
> For RTEMS buil
101 - 200 of 1061 matches
Mail list logo
