On 07/04/2020 15:26, Joel Sherrill wrote:
> ... The README says "Not all variants are tested" but I cannot see
> what has been tested? When you are new to a BSP a valid list of
what
> works is important.
The BSP runs on the evaluation board with default options.
But it
This looks better to me.
On Tue, Apr 7, 2020 at 2:57 AM Sebastian Huber
wrote:
>
> Delete unused RTEMS_DECLARE_GLOBAL_SYMBOL().
>
> Update #3799.
> ---
> cpukit/include/rtems/score/basedefs.h | 20
> testsuites/sptests/spmisc01/init.c| 7 ---
> 2 files changed, 27
This just means it doesn't have a bset. It doesn't mean it works. It still
is present in libbsd.
It will just now fail when someone performs the same steps by hand. I don't
see removing the bset as the solution.
I do not propose removing it from libbsd or the bsets. There needs to be a
mechanism
It is not possible to build libbsd with the standard settings of this
BSP. The BSP is also highly configurable and it is unlikely that the
RSB built configuration runs on a custom board.
---
rtems/config/5/bsps/atsamv.bset | 10 --
1 file changed, 10 deletions(-)
delete mode 100644
On 07/04/2020 17:05, Gedare Bloom wrote:
This looks better to me.
Good, I will build all BSPs with all tests overnight with this patch set.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hi
It is hard to keep up so here's a summary post of build failures for the
BSP bsets. For those keeping track, it took 7.5 hours of build time on
a fast machine, just to learn that the atsamv and pc BSP bsets
fail to build but the others do.
RSB is at this commit:
commit
On 07/04/2020 15:31, Sebastian Huber wrote:
On 07/04/2020 15:26, Joel Sherrill wrote:
> ... The README says "Not all variants are tested" but I cannot see
> what has been tested? When you are new to a BSP a valid list of
what
> works is important.
The BSP runs on the
On 07/04/2020 15:43, Joel Sherrill wrote:
This just means it doesn't have a bset. It doesn't mean it works. It
still is present in libbsd.
It will just now fail when someone performs the same steps by hand. I
don't see removing the bset as the solution.
I do not propose removing it from
---
bare/config/devel/glib-2.39.3-1.cfg | 4
1 file changed, 4 insertions(+)
diff --git a/bare/config/devel/glib-2.39.3-1.cfg
b/bare/config/devel/glib-2.39.3-1.cfg
index 9ff7af5..bd5770a 100644
--- a/bare/config/devel/glib-2.39.3-1.cfg
+++ b/bare/config/devel/glib-2.39.3-1.cfg
@@ -14,6
On Tue, Apr 7, 2020 at 2:04 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
> On 07/04/2020 08:24, Chris Johns wrote:
> > On 2020-04-07 15:01, Sebastian Huber wrote:
> >> I am not sure what we should do with this one. The libbsd is well
> >> supported on this BSP, however, with
Please apply your Christian's and your patch.
Also bump the dtc base package version number.
I thought we settled on 1.4.
--joel
On Tue, Apr 7, 2020 at 3:56 AM Hesham Almatary
wrote:
> * There is no all$ target in Spike
> * There is no longer --with-fesvr flag since fesvr is source-inlined
>
* There is no all$ target in Spike
* There is no longer --with-fesvr flag since fesvr is source-inlined
by default
---
source-builder/config/spike-1-1.cfg | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/source-builder/config/spike-1-1.cfg
Update #3799.
---
cpukit/include/rtems/score/basedefs.h | 24
1 file changed, 20 insertions(+), 4 deletions(-)
diff --git a/cpukit/include/rtems/score/basedefs.h
b/cpukit/include/rtems/score/basedefs.h
index 4589bea4aa..0a4ac8e415 100644
---
Delete unused RTEMS_DECLARE_GLOBAL_SYMBOL().
Update #3799.
---
cpukit/include/rtems/score/basedefs.h | 20
testsuites/sptests/spmisc01/init.c| 7 ---
2 files changed, 27 deletions(-)
diff --git a/cpukit/include/rtems/score/basedefs.h
---
testsuites/psxtests/Makefile.am | 10 ++
testsuites/psxtests/configure.ac | 1 +
testsuites/psxtests/psxgetcpuclockid01/init.c | 96 +++
.../psxgetcpuclockid01/psxgetcpuclockid01.doc | 19
.../psxgetcpuclockid01/psxgetcpuclockid01.scn | 4 +
5
Update #3799.
---
cpukit/include/rtems/confdefs/percpu.h | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/cpukit/include/rtems/confdefs/percpu.h
b/cpukit/include/rtems/confdefs/percpu.h
index 730571b54a..f3a9a4f3e7 100644
---
On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote:
>
>
> On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote:
>
>>
>> I'm not sure what error this is fixing, is there a ticket open for the
>> warning?
>>
>
> No idea on this.
>
>>
>> Is there a fix for the warning besides squelching it?
>>
>
>
I'm not sure what error this is fixing, is there a ticket open for the
warning?
Is there a fix for the warning besides squelching it?
How permanent is that gitlab? Should we just pluck these patches ourselves?
On Tue, Apr 7, 2020, 7:59 AM Vijay Kumar Banerjee wrote:
> ---
>
On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee wrote:
>
>
>
> On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote:
>>
>>
>>
>> On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote:
>>>
>>>
>>> I'm not sure what error this is fixing, is there a ticket open for the
>>> warning?
>>
>>
>> No
On Wed, Apr 8, 2020 at 12:49 AM Gedare Bloom wrote:
> On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee
> wrote:
> >
> >
> >
> > On Tue, Apr 7, 2020 at 11:12 PM Joel Sherrill wrote:
> >>
> >>
> >>
> >> On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote:
> >>>
> >>>
> >>> I'm not sure what
On Tue, Apr 7, 2020 at 12:35 PM Gedare Bloom wrote:
>
> I'm not sure what error this is fixing, is there a ticket open for the
> warning?
>
No idea on this.
>
> Is there a fix for the warning besides squelching it?
>
I think these are the warnings that are build failures on some hosts.
>
>
On Tue, Apr 7, 2020 at 2:30 PM Richi Dubey wrote:
> Hey everyone,
>
> Can someone please help me out with running a smp testsuite on erc32(which
> uses SPARC instruction set). I tried using sis, but the -m option for multi
> core doesnt seem to work, as the sis readme says: "-m cores : Enable
On Tue, Apr 7, 2020 at 1:30 PM Richi Dubey wrote:
>
> Hey everyone,
>
> Can someone please help me out with running a smp testsuite on erc32(which
> uses SPARC instruction set). I tried using sis, but the -m option for multi
> core doesnt seem to work, as the sis readme says: "-m cores : Enable
On Tue, Apr 7, 2020 at 2:29 PM Gedare Bloom wrote:
> Is there a ticket for psxgetcpuclockid? Linked from the psx compliance
> ticket?
>
https://devel.rtems.org/ticket/3891
--joel
>
> On Tue, Apr 7, 2020 at 5:28 AM Eshan dhawan
> wrote:
> >
>
> If so the commit message should include
>
>
I sent this patch a few days ago.
if anyone could look at it.
the code was tested by dr joel.
But had some style issues.
I have covered all the suggestions.
Do any more changes need to be made before it is merged?
Thanks
-Eshan
On Sat, Apr 4, 2020 at 12:46 AM Eshan dhawan
wrote:
> ---
>
On Wed, Apr 8, 2020 at 12:59 AM Gedare Bloom wrote:
> Is there a ticket for psxgetcpuclockid? Linked from the psx compliance
> ticket?
>
> On Tue, Apr 7, 2020 at 5:28 AM Eshan dhawan
> wrote:
> >
>
> If so the commit message should include
>
> Updates #.
>
> > ---
> >
Is there a ticket for psxgetcpuclockid? Linked from the psx compliance ticket?
On Tue, Apr 7, 2020 at 5:28 AM Eshan dhawan wrote:
>
If so the commit message should include
Updates #.
> ---
> testsuites/psxtests/Makefile.am | 10 ++
> testsuites/psxtests/configure.ac
Hey everyone,
Can someone please help me out with running a smp testsuite on erc32(which
uses SPARC instruction set). I tried using sis, but the -m option for multi
core doesnt seem to work, as the sis readme says: "-m cores : Enable the
number of cores (2 - 4) in a leon3 or RISC-V
Applying: Tests for inttype.h methods
.git/rebase-apply/patch:14: trailing whitespace.
* Copyright (C) 2020, Eshan Dhawan
.git/rebase-apply/patch:29: trailing whitespace.
.git/rebase-apply/patch:30: trailing whitespace.
/* Test for imaxabs */
.git/rebase-apply/patch:34: trailing whitespace.
It looks alright, I'm testing it now.
On Tue, Apr 7, 2020 at 1:13 PM Eshan Dhawan wrote:
>
> I sent this patch a few days ago.
> if anyone could look at it.
> the code was tested by dr joel.
> But had some style issues.
> I have covered all the suggestions.
> Do any more changes need to be made
---
testsuites/psxtests/psxinttypes01/init.c | 26 +--
.../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++-
2 files changed, 33 insertions(+), 3 deletions(-)
diff --git a/testsuites/psxtests/psxinttypes01/init.c
b/testsuites/psxtests/psxinttypes01/init.c
index
Resolved the trailing whitespace issue in this patch.
can you please check :)
On Wed, Apr 8, 2020 at 1:58 AM Eshan dhawan wrote:
> ---
> testsuites/psxtests/psxinttypes01/init.c | 26 +--
> .../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++-
> 2 files changed, 33
---
testsuites/psxtests/psxinttypes01/init.c | 26 +--
.../psxtests/psxinttypes01/psxinttypes01.doc | 10 ++-
2 files changed, 33 insertions(+), 3 deletions(-)
diff --git a/testsuites/psxtests/psxinttypes01/init.c
b/testsuites/psxtests/psxinttypes01/init.c
index
On Wed, Apr 8, 2020, 2:46 AM Gedare Bloom wrote:
> On Tue, Apr 7, 2020 at 2:06 PM Vijay Kumar Banerjee
> wrote:
> >
> >
> >
> > On Wed, Apr 8, 2020 at 12:49 AM Gedare Bloom wrote:
> >>
> >> On Tue, Apr 7, 2020 at 12:03 PM Vijay Kumar Banerjee
> wrote:
> >> >
> >> >
> >> >
> >> > On Tue, Apr
There is a ws error for adding a new line to end of .doc file, but
that is fine. I tested on sis, looks good, pushed it.
On Tue, Apr 7, 2020 at 2:26 PM Eshan dhawan wrote:
>
> ---
> testsuites/psxtests/psxinttypes01/init.c | 26 +--
>
On 2020-04-07 23:36, Sebastian Huber wrote:
On 07/04/2020 15:31, Sebastian Huber wrote:
On 07/04/2020 15:26, Joel Sherrill wrote:
> ... The README says "Not all variants are tested" but I cannot see
> what has been tested? When you are new to a BSP a valid list of
what
>
These patches are needed so all BSPs except epiphany can now
build and link all tests with debug enabled.
Joel Sherrill (6):
lm4f120-testsuite.tcfg: Add psxsignal07
lpc1768_mbed_ahb_ram_eth-testsuite.tcfg: Add psxsignal07
lpc2362-testsuite.tcfg: Add psxaoi03 and psxsignal07
Updates #3938.
---
bsps/m68k/mcf52235/config/mcf52235-testsuite.tcfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/bsps/m68k/mcf52235/config/mcf52235-testsuite.tcfg
b/bsps/m68k/mcf52235/config/mcf52235-testsuite.tcfg
index 1343981..2a387b3 100644
---
Updates #3938.
---
bsps/arm/lpc24xx/config/lpc23xx_tli800-testsuite.tcfg | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bsps/arm/lpc24xx/config/lpc23xx_tli800-testsuite.tcfg
b/bsps/arm/lpc24xx/config/lpc23xx_tli800-testsuite.tcfg
index d75ad36..990f74e 100644
---
Updates #3938.
---
bsps/arm/lpc176x/config/lpc1768_mbed-testsuite.tcfg | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bsps/arm/lpc176x/config/lpc1768_mbed-testsuite.tcfg
b/bsps/arm/lpc176x/config/lpc1768_mbed-testsuite.tcfg
index ae737d9..288ae38 100644
---
Updates #3938.
---
bsps/arm/lm3s69xx/config/lm4f120-testsuite.tcfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/bsps/arm/lm3s69xx/config/lm4f120-testsuite.tcfg
b/bsps/arm/lm3s69xx/config/lm4f120-testsuite.tcfg
index be14cde..b520567 100644
---
Updates #3938.
---
bsps/arm/lpc24xx/config/lpc2362-testsuite.tcfg | 2 ++
1 file changed, 2 insertions(+)
diff --git a/bsps/arm/lpc24xx/config/lpc2362-testsuite.tcfg
b/bsps/arm/lpc24xx/config/lpc2362-testsuite.tcfg
index bd972f9..5717e8e 100644
---
On 2020-04-07 03:54, Gedare Bloom wrote:
On Mon, Apr 6, 2020 at 11:49 AM Joel Sherrill wrote:
On Mon, Apr 6, 2020 at 12:43 PM Gedare Bloom wrote:
This is a problem caused by newer versions of perl. The unescaped { }
in regex was deprecated and then eliminated. It requires an upstream
fix
On 2020-04-07 23:58, Vijay Kumar Banerjee wrote:
---
bare/config/devel/glib-2.39.3-1.cfg | 4
1 file changed, 4 insertions(+)
diff --git a/bare/config/devel/glib-2.39.3-1.cfg
b/bare/config/devel/glib-2.39.3-1.cfg
index 9ff7af5..bd5770a 100644
--- a/bare/config/devel/glib-2.39.3-1.cfg
On Wed, Apr 8, 2020 at 4:10 AM Chris Johns wrote:
> On 2020-04-07 23:58, Vijay Kumar Banerjee wrote:
> > ---
> > bare/config/devel/glib-2.39.3-1.cfg | 4
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/bare/config/devel/glib-2.39.3-1.cfg
> b/bare/config/devel/glib-2.39.3-1.cfg
>
On 2020-04-08 11:20, Gedare Bloom wrote:
On Tue, Apr 7, 2020 at 4:44 PM Chris Johns wrote:
On 2020-04-07 03:54, Gedare Bloom wrote:
On Mon, Apr 6, 2020 at 11:49 AM Joel Sherrill wrote:
On Mon, Apr 6, 2020 at 12:43 PM Gedare Bloom wrote:
This is a problem caused by newer versions of
a few one-liners to try out, here's what I get (Ubuntu 18.04):
$ perl --version 2>&1 | grep version | sed -e 's/.*(v\(.*\)).*/\1/'
5.26.1
$ perl --version 2>&1 | grep version | sed -e 's/.*perl \([0-9]*\),.*/\1/'
5
$perl --version 2>&1 | grep version | sed -e 's/.*version \([0-9]*\),.*/\1/'
On 08/04/2020 00:59, Chris Johns wrote:
This BSP and the libbsd build system are not good enough right now to
add this BSP to an RSB build set.
I agree the build system is lacking but I do not see that as the key
issue that has been uncovered. The main issue is the addition of
"special"
On Tue, Apr 7, 2020 at 4:44 PM Chris Johns wrote:
>
> On 2020-04-07 03:54, Gedare Bloom wrote:
> > On Mon, Apr 6, 2020 at 11:49 AM Joel Sherrill wrote:
> >>
> >>
> >>
> >> On Mon, Apr 6, 2020 at 12:43 PM Gedare Bloom wrote:
> >>>
> >>> This is a problem caused by newer versions of perl. The
On 08/04/2020 07:14, Sebastian Huber wrote:
On 08/04/2020 00:59, Chris Johns wrote:
This BSP and the libbsd build system are not good enough right now
to add this BSP to an RSB build set.
I agree the build system is lacking but I do not see that as the key
issue that has been uncovered.
On 2020-04-07 15:01, Sebastian Huber wrote:
I am not sure what we should do with this one. The libbsd is well
supported on this BSP, however, with default options, the BSP has not
enough memory to link all the libbsd tests. For this BSP you likely have
to specify some BSP options to build it
Is there something happening that is resulting in me seeing these as
threaded to the previous patch set?
Thanks
Chris
On 2020-04-07 07:32, Mritunjay Sharma wrote:
Hi all,
After this patch, you can safely remove all the Motorola M68xxx and
Coldfire BSPs
from the wiki except probably
Hi Alan,
This is awesome. I welcome deployment stories and support for them. I
wonder if we need a way to assist capturing this for our users.
You may need to add something to the site's README to provide beginner
steps.
Chris
On 2020-04-07 11:44, Alan Cudmore wrote:
Chris,
I tested this
Hi Joel,
Thanks, yes the changes have not been merged yet to the 5-freebsd-12 branch.
I am about to prepare the next version of the patch set.
Cheers,
Jan
Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Joel Sherrill
Gesendet: Dienstag, 7. April 2020 01:31
An:
On 07/04/2020 08:24, Chris Johns wrote:
On 2020-04-07 15:01, Sebastian Huber wrote:
I am not sure what we should do with this one. The libbsd is well
supported on this BSP, however, with default options, the BSP has not
enough memory to link all the libbsd tests. For this BSP you likely
Add a start/end file specification if the -qrtems option is present.
Allow targets to customize it.
Support the standard -nodefaultlibs option.
gcc/
* config/rs6000/rtems.h (RTEMS_STARTFILE_SPEC): Define.
(RTEMS_ENDFILE_SPEC): Likewise.
* config/rtems.h
On 07/04/2020 09:29, Sebastian Huber wrote:
Add a start/end file specification if the -qrtems option is present.
Allow targets to customize it.
Support the standard -nodefaultlibs option.
gcc/
* config/rs6000/rtems.h (RTEMS_STARTFILE_SPEC): Define.
(RTEMS_ENDFILE_SPEC):
57 matches
Mail list logo
