On 17/11/2017 15:27, gro...@chichak.ca wrote:
> I fear blowing up builds all over the world, but I’ll give it a try.
Fantastic. Looking forward to the fireworks.
Chris
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
I fear blowing up builds all over the world, but I’ll give it a try.
A
> On 2017-November-16, at 21:21, Chris Johns wrote:
>
> On 17/11/2017 15:05, gro...@chichak.ca wrote:
>>
>> (I don’t know how to proceed with getting this reported/fixed.)
>>
>
> Please head to the wiki (https://devel.rte
On 17/11/2017 15:05, gro...@chichak.ca wrote:
>
> (I don’t know how to proceed with getting this reported/fixed.)
>
Please head to the wiki (https://devel.rtems.org/) and select the link in the
"Reporting a bug" column of the Releases Table for the release you are reporting
the bug against. You
> On 2017-November-15, at 16:10, Chris Johns wrote:
>
> On 16/11/2017 09:50, Mr. Andrei Chichak wrote:
>> I’m working with 4.12 for ARM (cortex M7)
>>
>> I’m tracing down an issue and figured it smelled like a stack problem, so I
>> got
>> my command line interpreter to call rtems_stack_che
On 17/11/2017 08:04, Jacob Saina wrote:
> I am currently building 4.11.2 from git ("git checkout 4.11.2" prior to
> building), and it looks promising because it's been going for longer than
> the others took to fail. I'll report back tomorrow.
>
>
> My computer also rebooted, but seem
>
> I am currently building 4.11.2 from git ("git checkout 4.11.2" prior to
> building), and it looks promising because it's been going for longer than
> the others took to fail. I'll report back tomorrow.
>
My computer also rebooted, but seemingly after the build completed. This
means that the bu
On 16/11/2017 14:36, Joel Sherrill wrote:
> FWIW I had a sparc build go ok for the master on Windows but tried a powerpc
> build and it failed with something about unable to fork. I am restarting it
> and
> letting it run again.
I would try a build with your virus checker software disabled. I hav
