Re: Fwd: Build Error on FreeBSD 12

On 9/11/19 10:36 am, Joel Sherrill wrote: > Looks like a failing in the GDB configure magic which finds libiconv Sadly this is the case. The idea of /usr/local does not seem to be supported. Check the RSB's freebsd.py support to see if the path is being set correctly. This should end up in the gen

Fwd: Build Error on FreeBSD 12

Looks like a failing in the GDB configure magic which finds libiconv -- Forwarded message - From: John Baldwin Date: Fri, Nov 8, 2019 at 11:20 AM Subject: Re: Build Error on FreeBSD 12 To: , On 10/30/19 11:41 AM, Joel Sherrill wrote: > Hi > > When building gdb 8.3 for *-rtems5

Re: Performance problem with PyYAML

On 9/11/19 10:02 am, Joel Sherrill wrote: > > > On Fri, Nov 8, 2019 at 4:58 PM Chris Johns > wrote: > > On 9/11/19 9:52 am, Joel Sherrill wrote: > > On Fri, Nov 8, 2019 at 4:26 PM Chris Johns > >

Re: all bset email

On 9/11/19 10:00 am, Joel Sherrill wrote: > > > On Fri, Nov 8, 2019 at 4:24 PM Chris Johns > wrote: > > On 9/11/19 3:04 am, Joel Sherrill wrote: > > When building the rtems-all.bset, the build log is quite large, > especially > when > > there are fail

Re: Performance problem with PyYAML

On Fri, Nov 8, 2019 at 4:58 PM Chris Johns wrote: > On 9/11/19 9:52 am, Joel Sherrill wrote: > > On Fri, Nov 8, 2019 at 4:26 PM Chris Johns > > wrote: > > > > On 9/11/19 2:57 am, Gedare Bloom wrote: > > > Ah, pickling makes sense. > > > > > > On Fri, Nov

Re: all bset email

On Fri, Nov 8, 2019 at 4:24 PM Chris Johns wrote: > On 9/11/19 3:04 am, Joel Sherrill wrote: > > When building the rtems-all.bset, the build log is quite large, > especially when > > there are failures. > > I have increased the limit on that list. > > > Would it make more sense for automated test

Re: Performance problem with PyYAML

On 9/11/19 9:52 am, Joel Sherrill wrote: > On Fri, Nov 8, 2019 at 4:26 PM Chris Johns > wrote: > > On 9/11/19 2:57 am, Gedare Bloom wrote: > > Ah, pickling makes sense. > > > > On Fri, Nov 8, 2019 at 4:03 AM Sebastian Huber > >

Re: Performance problem with PyYAML

On Fri, Nov 8, 2019 at 4:26 PM Chris Johns wrote: > On 9/11/19 2:57 am, Gedare Bloom wrote: > > Ah, pickling makes sense. > > > > On Fri, Nov 8, 2019 at 4:03 AM Sebastian Huber > > wrote: > >> > >> Sorry, for the frequent updates. It turned out to be a very small > >> modification to add a build

Re: [PATCH] eng: Add build system chapter

On 9/11/19 12:56 am, Sebastian Huber wrote: > Update #3818. > --- > > This is the first draft of the documentation of the new build system from the > RTEMS maintainer perspective. Well done. This this effort is looking nice. > I work the documentation for the user manual next week. The next ste

Re: [PATCH] user: Add hints for macOS Catalina

On 8/11/19 7:08 pm, Sebastian Huber wrote: > On 08/11/2019 08:50, Chris Johns wrote: >> >>> On 8 Nov 2019, at 5:20 pm, Sebastian Huber >>> wrote: >>> >>> On 07/11/2019 22:04, Chris Johns wrote: > On 7/11/19 7:51 pm, Sebastian Huber wrote: > Use macOS throughout.  Order release hints so th

Re: Performance problem with PyYAML

On 9/11/19 2:57 am, Gedare Bloom wrote: > Ah, pickling makes sense. > > On Fri, Nov 8, 2019 at 4:03 AM Sebastian Huber > wrote: >> >> Sorry, for the frequent updates. It turned out to be a very small >> modification to add a build specification item cache with pickle. I agree pickle and generati

Re: all bset email

On 9/11/19 3:04 am, Joel Sherrill wrote: > When building the rtems-all.bset, the build log is quite large, especially > when > there are failures. I have increased the limit on that list. > Would it make more sense for automated testing to build each target > independently? This would result in

all bset email

Hi When building the rtems-all.bset, the build log is quite large, especially when there are failures. Would it make more sense for automated testing to build each target independently? This would result in more, smaller emails. I am thinking it might be easier to figure out the specific failure

Re: Performance problem with PyYAML

Ah, pickling makes sense. On Fri, Nov 8, 2019 at 4:03 AM Sebastian Huber wrote: > > Sorry, for the frequent updates. It turned out to be a very small > modification to add a build specification item cache with pickle. Python > is really a nice language. > > -- > Sebastian Huber, embedded brains G

[PATCH 09/13] samples/paranoia: Remove include

This include is superfluous. --- testsuites/samples/paranoia/paranoia.c | 1 - 1 file changed, 1 deletion(-) diff --git a/testsuites/samples/paranoia/paranoia.c b/testsuites/samples/paranoia/paranoia.c index 2f2d1943fe..4d5a1443f9 100644 --- a/testsuites/samples/paranoia/paranoia.c +++ b/testsui

[PATCH 12/13] ada/samples: Avoid build system defined defines

Update #3818. --- testsuites/ada/samples/base_mp/node1/Makefile.am | 5 + testsuites/ada/samples/base_mp/node1/init.c | 2 ++ testsuites/ada/samples/base_mp/node2/Makefile.am | 5 + testsuites/ada/samples/base_mp/node2/init.c | 2 ++ 4 files changed, 6 insertions(+), 8 deletions(

[PATCH 11/13] mptests/mp14: Make MAX_LONG_TEST_DURATION constant

If there is a real need, it can be made a configuration option again. Update #3818. --- testsuites/mptests/Makefile.am | 4 ++-- testsuites/mptests/configure.ac | 4 testsuites/mptests/mp14/init.c | 6 ++ 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/testsuites/mptests

[PATCH 00/13] Avoid build system defined defines

Build system defined defines are quite bad. Firstly, they are invisible to code indexing tools such as ctags and code anlaysers included in IDEs. Secondly, they make the introduction of a new build system more complicated than necessary. This patch set removes all build system defined defines fr

[PATCH 04/13] sptests: Avoid build system defined defines

Update #3818. --- testsuites/sptests/Makefile.am | 49 --- testsuites/sptests/sp27/init.c | 146 +-- testsuites/sptests/sp27/sp27impl.h | 145 +++ testsuites/sptests/sp27a/init.c| 2 +

[PATCH 10/13] tmtests: Avoid build system defined defines

Update #3818. --- testsuites/tmtests/Makefile.am | 28 +++--- testsuites/tmtests/tm02/task1.c| 189 + testsuites/tmtests/tm02/tm02impl.h | 187 testsuites/tmtests/tm03/task1.c| 180 +--

[PATCH 02/13] psxtests: Avoid build system defined defines

Update #3818. --- testsuites/psxtests/Makefile.am | 8 +- testsuites/psxtests/psxsignal03/init.c| 252 +- testsuites/psxtests/psxsignal03/psxsignal0ximpl.h | 234 testsuites/psxtests/psxsignal04/init.c| 2 + 4 f

[PATCH 13/13] mptests: Avoid build system defined defines

Update #3818. --- testsuites/mptests/Makefile.am | 104 - testsuites/mptests/mp01/init1.c| 2 + testsuites/mptests/mp01/init2.c| 2 + testsuites/mptests/mp01/{init.c => initimpl.h} | 0 testsuites/mptests/mp03/init1.c

[PATCH 07/13] libtests: Avoid build system defined defines

Update #3818. --- testsuites/libtests/Makefile.am| 27 +- testsuites/libtests/complex/docomplexl.c | 3 + testsuites/libtests/dl06/init.c| 89 +- testsuites/libtests/dl06/initimpl.h| 88 ++ testsuites/libtests/dl06/pre-

[PATCH 01/13] tests: Remove superfluous SMPTESTS define

Update #3818. --- testsuites/smptests/Makefile.am | 14 +++--- testsuites/sptests/Makefile.am | 2 +- testsuites/support/include/tmacros.h | 10 +- 3 files changed, 9 insertions(+), 17 deletions(-) diff --git a/testsuites/smptests/Makefile.am b/testsuites/smptests/Make

[PATCH 03/13] psxtmtests: Avoid build system defined defines

Update #3818. --- testsuites/psxtmtests/Makefile.am | 12 +- testsuites/psxtmtests/psxtmcond08/init.c | 184 + .../psxtmtests/psxtmcond08/psxtmcond08impl.h | 182 testsuites/psxtmtests/psxtmcond09/init.c | 2 +

[PATCH] build: Add build specification items pickle cache

--- .gitignore | 1 + wscript| 51 --- 2 files changed, 45 insertions(+), 7 deletions(-) diff --git a/.gitignore b/.gitignore index d7ca74b338..0ff9d6929e 100644 --- a/.gitignore +++ b/.gitignore @@ -7,6 +7,7 @@ doc .lock* Makefile.in *.pyc

[PATCH 08/13] samples: Avoid build system defined defines

Update #3818. --- testsuites/samples/Makefile.am| 10 +- testsuites/samples/base_mp/init1.c| 2 ++ testsuites/samples/base_mp/init2.c| 2 ++ testsuites/samples/base_mp/{init.c => initimpl.h} | 0 testsuites/samples/paranoia/paranoia.c

[PATCH 06/13] sptests: Remove obsolete semaphore consume driver

This driver is no longer used by a test program. Update #3818. --- testsuites/sptests/Makefile.am| 16 +- testsuites/sptests/spfatal_support/consume_sems.c | 63 --- testsuites/sptests/spfatal_support/system.h | 11 3 files changed, 2 inserti

[PATCH 05/13] spfatal16: Remove obsolete test program

The "TRrc" semaphore was removed in commit 2c12262f9a8fe7975556729f0574fab8d5a792f5. --- testsuites/sptests/spfatal16/spfatal16.doc | 19 --- testsuites/sptests/spfatal16/spfatal16.scn | 3 --- testsuites/sptests/spfatal16/testcase.h| 29 - 3 files

[PATCH] eng: Add build system chapter

Update #3818. --- This is the first draft of the documentation of the new build system from the RTEMS maintainer perspective. I work the documentation for the user manual next week. The next step is to convert all tests to the new build system (except Ada tests). The final step is to convert al

Re: Performance problem with PyYAML

Sorry, for the frequent updates. It turned out to be a very small modification to add a build specification item cache with pickle. Python is really a nice language. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax

Re: Performance problem with PyYAML

I experimented a bit with marshal, pickle, and ast.literal_eval. I think that using a cache file is the way to go. An update evaluation based on the mtime is quite fast. You need the YAML to X conversion only if a build specification file changed or upon first use. We don't have to store the ca

Re: Performance problem with PyYAML

Attached is a script to create the aggregated items with the marshal module. Loading it is quite fast (0.1s). -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedde

Re: [PATCH] user: Add hints for macOS Catalina

On 08/11/2019 08:50, Chris Johns wrote: On 8 Nov 2019, at 5:20 pm, Sebastian Huber wrote: On 07/11/2019 22:04, Chris Johns wrote: On 7/11/19 7:51 pm, Sebastian Huber wrote: Use macOS throughout. Order release hints so that the latest macOS release comes first. Thanks for this. +Catalina