On Tue, Jun 30, 2020 at 9:42 PM Mritunjay Sharma
wrote:
>
> Hi Gedare,
>
> Thank you for the quick response, I tried using --target=i386-rtems4.10,
> which again
> gave me the same error.
>
Did you build an RTEMS compiler toolchain for 4.10? and install it to
a prefix in your $PATH?
> "checking
Hi Gedare,
Thank you for the quick response, I tried using --target=i386-rtems4.10,
which again
gave me the same error.
"checking for RTEMS_CPU_MODEL... i386_fp
checking for RTEMS_BSP_FAMILY... pc386
checking for CPU_CFLAGS... (cached) -mtune=i386
checking for CFLAGS_OPTIMIZE_V... (cached) -O2 -g
On Wednesday morning (Tuesday evening in the US)
On Tue, Jun 30, 2020 at 5:38 PM Gedare Bloom wrote:
>
> I mentioned this to the students but didn't announce here, in case
> anyone cares to join us, the weekly GSoC-RTEMS IRC meeting is moving
> 30 minutes earlier, to 4:00 AM UTC.
>
> Gedare
_
I mentioned this to the students but didn't announce here, in case
anyone cares to join us, the weekly GSoC-RTEMS IRC meeting is moving
30 minutes earlier, to 4:00 AM UTC.
Gedare
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listi
Use --target=i386-rtems4.10 instead of --target=i386-rtems
Does this work with 4.10.3/4.10 HEAD?
On Tue, Jun 30, 2020 at 3:54 PM Mritunjay Sharma
wrote:
>
> Hello everyone,
>
> I followed the documentation here
> https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
>
Hello everyone,
I followed the documentation here
https://docs.rtems.org/releases/rtemsdocs-4.10.2/share/rtems/pdf/started.pdf
and
started building RTEMS (4.10.2) for target architecture: i386 and BSP:
pc386. The configure seemed to be fine
after entering the following command:
"../configure --ta
On 30/06/2020 17:41, build...@rtems.org wrote:
The Buildbot has detected a passing build on builder snapshot-test while
building rtems.
Full details are available at:
https://buildbot.rtems.org/#builders/4/builds/930
Buildbot URL: https://buildbot.rtems.org/
Worker for this Build: build-
thanks, good clarification
On Tue, Jun 30, 2020 at 1:52 AM Sebastian Huber
wrote:
>
> Update #4018.
> ---
> cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h
> b/cpu
On 30/6/20 3:44 am, Sebastian Huber wrote:
why is there an RTEMS version in curl.bset?
rtems/config/ftp/curl.bset:
#
# RTEMS Version
#
%define rtems_version 5
A mistake? It can be removed.
Thanks
Chris
___
devel mailing list
devel@rtems.org
http:
On 30/6/20 5:44 pm, Sebastian Huber wrote:
Hello,
I updated the version numbers in rtems, rtems-docs, rtems-tools, and
rtems-source-builder to RTEMS 6 on the master branches. I added also a
ticket for the version change:
https://devel.rtems.org/ticket/4020
The release process documentation
Update #4018.
---
cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h
b/cpukit/score/cpu/no_cpu/include/rtems/score/cpu.h
index 84125aa16b..50313bbd61 100644
--- a/cpukit/sco
On 29/06/2020 21:35, Kinsey Moore wrote:
This introduces the CPU_USE_LIBC_INIT_FINI_ARRAY define for use by CPU
ports to determine which global constructor and destructor methods are
used instead of placing architecture defines where they shouldn't be.
Close #4018
Thanks, I checked it in with
Hello,
I updated the version numbers in rtems, rtems-docs, rtems-tools, and
rtems-source-builder to RTEMS 6 on the master branches. I added also a
ticket for the version change:
https://devel.rtems.org/ticket/4020
The release process documentation should be up to date.
_
On 30/06/2020 08:10, Richi Dubey wrote:
I've also sent in the patch for rtems-qual in another email. Please
review them and let me know if everything looks ok.
Sorry for the delay, I checked it in with minor modifications. Please
format text blocks so that they use the minimum amount of vertica
14 matches
Mail list logo