Hello,
I would like to announce the start of release snapshots from the master branch.
A release snapshot will be created on the first day of each month. These are
development snapshots so they can be unstable.
An announce email will be posted to u...@rtems.org and devel@rtems.org with a
link to
On 30/10/2019 10:35, Vaibhav Gupta wrote:
So what's the final stand on this?
Should be working on standalone guide or add the contents to RTEMS
Software Engineering guide as suggested by Sebastian?
I think nobody was in favour of adding a new document. I would place it
in the RTEMS Software
Hi
Passing this along. This needs to happen for m68k and coldfire to be
supported in GCC beyond the current release.
--joel
-- Forwarded message -
From: John Paul Adrian Glaubitz
Date: Sat, Oct 19, 2019 at 4:58 AM
Subject: BountySource campaign for gcc PR/91851
To:
Hello!
Fo
On Wed, Oct 30, 2019 at 3:54 PM Chris Johns wrote:
> On 30/10/19 11:52 pm, Joel Sherrill wrote:
> > Does anyone else see this on FreeBSD? Seems to be ok on CentOS.
>
> No
>
> https://lists.rtems.org/pipermail/build/2019-October/007287.html
>
> > gmake[4]: Leaving directory
> '/usr/home/joel/
On 30/10/19 11:52 pm, Joel Sherrill wrote:
> Does anyone else see this on FreeBSD? Seems to be ok on CentOS.
No
https://lists.rtems.org/pipermail/build/2019-October/007287.html
> gmake[4]: Leaving directory
> '/usr/home/joel/rtems-cron-5/rtems-source-builder/rt
> ems/build/microblaze-rtems
>From my perspective, yes. If it breaks something else, we can fix that.
On Wed, Oct 30, 2019 at 9:47 AM Hesham Almatary <
hesham.almat...@cl.cam.ac.uk> wrote:
> OK to push?
>
> On Tue, 29 Oct 2019 at 09:25, Hesham Almatary
> wrote:
> >
> > On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote:
> >
OK to push?
On Tue, 29 Oct 2019 at 09:25, Hesham Almatary
wrote:
>
> On Mon, 28 Oct 2019 at 23:15, Joel Sherrill wrote:
> >
> >
> >
> > On Mon, Oct 28, 2019 at 5:20 AM Hesham Almatary
> > wrote:
> >>
> >> On Mon, 28 Oct 2019 at 04:01, Chris Johns wrote:
> >> >
> >> >
> >> >
> >> > On 28/10/19
On 28/10/2019 22:03, Chris Johns wrote:
On 29/10/19 1:42 am, Sebastian Huber wrote:
Any objections to commit this patch?
Should "Must be done by an RTEMS Maintainer" be "Push performed by an approved
RTEMS Committer" ? This covers "Maintainers" and those with commit access to a
specific area.
Hi
Does anyone else see this on FreeBSD? Seems to be ok on CentOS.
gmake[4]: Leaving directory
'/usr/home/joel/rtems-cron-5/rtems-source-builder/rt
ems/build/microblaze-rtems5-gcc-fb371a33fa6-newlib-6661a67-i386-freebsd12.0-1/bu
ild/microblaze-rtems5/bs/libgcc'
gmake[3]: *** [Makefile:1198: multi
On 30/10/2019 10:29, Chris Johns wrote:
configure:3472: checking whether the C compiler works
configure:3494: arm-rtems5-gcc -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16
-mfloat-abi=hard -O2 -g -ffunction-sections -fdata-sections conftest.c >&5
/opt/work/rtems/5/lib/gcc/arm-rtems5/7.4.0/../../..
So what's the final stand on this?
Should be working on standalone guide or add the contents to RTEMS Software
Engineering guide as suggested by Sebastian?
--Vaibhav
On Fri, Sep 13, 2019, 5:40 PM Vaibhav Gupta
wrote:
> Well I have no problem in working on standalone guide or adding it to
> So
On 30/10/19 7:17 pm, Sebastian Huber wrote:
> On 30/10/2019 07:18, Chris Johns wrote:
>> Hi,
>>
>> Building all ARM BSPs on master today I get ...
>>
>> checking for arm-rtems5-gcc... (cached) arm-rtems5-gcc
>> checking whether the C compiler works... no
>> configure: error: in
>> `/opt/work/chr
Looks good.
--
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...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mit
On 30/10/2019 07:18, Chris Johns wrote:
Hi,
Building all ARM BSPs on master today I get ...
checking for arm-rtems5-gcc... (cached) arm-rtems5-gcc
checking whether the C compiler works... no
configure: error: in
`/opt/work/chris/rtems/kernel/bsps/arm/arm-rtems5/c/lpc40xx_ea_ram':
configure: err
14 matches
Mail list logo