On 2015-02-10 21:57 -0500, Alan Cudmore wrote:
> Raspberry Pi times on my PC ( 6 core AMD, 8GB RAM, SSD , Ubuntu 14.04 ) :
>
> Standard build system:
> ? ? Bootstrap : 7m4s
> ? ? Configure step: 8s
> ? ? Build: 3m15s?
>
> ? ? Size of RTEMS Tree after bootstrap: 308Mbytes
>
> Waf build:
> ?
On 2015-02-11 14:16 +1100, Chris Johns wrote:
> And as I see below options can be altered in a controlled manner instead
> of a local patch applied after the config phase. This is what I was meaning.
Ah, yes it's very controlled in config.cfg. The options are verified (not
fully, yet) for sanit
On 10/02/2015 8:20 am, Amar Takhar wrote:
On 2015-02-10 08:15 +1100, Chris Johns wrote:
Look in config.cfg when you do a 'waf' configure for all the available options
these are exposed there.
Do I just edit these options ?
Yes.
If so, is this temporary or the way we do this ? I am consi
On 11/02/2015 1:57 pm, Alan Cudmore wrote:
Raspberry Pi times on my PC ( 6 core AMD, 8GB RAM, SSD , Ubuntu 14.04 ) :
Standard build system:
Bootstrap : 7m4s
Configure step: 8s
Build: 3m15s
Size of RTEMS Tree after bootstrap: 308Mbytes
Waf build:
configure: ~4s
build wit
Raspberry Pi times on my PC ( 6 core AMD, 8GB RAM, SSD , Ubuntu 14.04 ) :
Standard build system:
Bootstrap : 7m4s
Configure step: 8s
Build: 3m15s
Size of RTEMS Tree after bootstrap: 308Mbytes
Waf build:
configure: ~4s
build with tests: 29s
Size of RTEMS tree : 188Mbytes
Ni
On 2/10/2015 3:46 PM, Peter Dufault wrote:
>> On Feb 10, 2015, at 15:30 , Joel Sherrill wrote:
>>
>> On 2/10/2015 2:26 PM, Hesham Moustafa wrote:
>>> On Tue, Feb 10, 2015 at 8:21 PM, Joel Sherrill
>>> wrote:
Thanks. One down.
Crap. It should have had a comment that closed the PR.
> On Feb 10, 2015, at 15:30 , Joel Sherrill wrote:
>
> On 2/10/2015 2:26 PM, Hesham Moustafa wrote:
>> On Tue, Feb 10, 2015 at 8:21 PM, Joel Sherrill
>> wrote:
>>> Thanks. One down.
>>>
>>> Crap. It should have had a comment that closed the PR. :(
>> Who should add the comment? The ticket is n
Yeah if you don't mind, when you now the ticket number, just include
something like
"closes #xyz"
On Tue, Feb 10, 2015 at 3:26 PM, Hesham Moustafa
wrote:
> On Tue, Feb 10, 2015 at 8:21 PM, Joel Sherrill
> wrote:
>> Thanks. One down.
>>
>> Crap. It should have had a comment that closed the PR. :
On 2/10/2015 2:26 PM, Hesham Moustafa wrote:
> On Tue, Feb 10, 2015 at 8:21 PM, Joel Sherrill
> wrote:
>> Thanks. One down.
>>
>> Crap. It should have had a comment that closed the PR. :(
> Who should add the comment? The ticket is now closed (fixed). In the
> future patches, should I tag the tic
On Tue, Feb 10, 2015 at 8:21 PM, Joel Sherrill
wrote:
> Thanks. One down.
>
> Crap. It should have had a comment that closed the PR. :(
Who should add the comment? The ticket is now closed (fixed). In the
future patches, should I tag the ticket/PR number part of the commit
message?
> On 2/10/2015
Thanks. One down.
Crap. It should have had a comment that closed the PR. :(
On 2/10/2015 2:04 PM, Hesham ALMatary wrote:
> ---
> cpukit/score/cpu/or1k/cpu.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/cpukit/score/cpu/or1k/cpu.c b/cpukit/score/cpu/or1k/cpu.c
> i
---
cpukit/score/cpu/or1k/cpu.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/cpukit/score/cpu/or1k/cpu.c b/cpukit/score/cpu/or1k/cpu.c
index 9d1ae49..69845ff 100644
--- a/cpukit/score/cpu/or1k/cpu.c
+++ b/cpukit/score/cpu/or1k/cpu.c
@@ -14,9 +14,14 @@
#include
#incl
This looks great if it had a comment. :)
On 2/10/2015 1:50 PM, Hesham ALMatary wrote:
> ---
> cpukit/score/cpu/or1k/cpu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/cpukit/score/cpu/or1k/cpu.c b/cpukit/score/cpu/or1k/cpu.c
> index 9d1ae49..4d6e9c0 100644
> --- a/cp
---
cpukit/score/cpu/or1k/cpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/cpukit/score/cpu/or1k/cpu.c b/cpukit/score/cpu/or1k/cpu.c
index 9d1ae49..4d6e9c0 100644
--- a/cpukit/score/cpu/or1k/cpu.c
+++ b/cpukit/score/cpu/or1k/cpu.c
@@ -14,9 +14,10 @@
#include
#include
On 09/02/15 22:28, Gedare Bloom wrote:
Nit: should the counted string functions be used?
No, the allocation part takes care that we have enough space in the buffer.
On Mon, Feb 9, 2015 at 3:35 PM, Sebastian Huber
wrote:
---
cpukit/libfs/src/imfs/imfs_symlink.c | 33 +++--
15 matches
Mail list logo