Hello Nick,
thanks for the patch. I checked in a slightly different version which
ignores the return status completely.
On 20/02/15 05:13, Nick Withers wrote:
Hi all,
Commit 3211e8e9c0565fae8b13ba0115e3a23ad3ae8ade added error checking to
a mkdir("/etc", ...) call in pwdgrp_init().
That cal
Hi all,
Commit 3211e8e9c0565fae8b13ba0115e3a23ad3ae8ade added error checking to
a mkdir("/etc", ...) call in pwdgrp_init().
That call might fail if the directory already exists. In my case,
because I'm tarfs-ing stuff into /etc before invoking the NFS client,
which calls pwdgrp_init().
The attac
We should review this entire document. I suspect our status is better than this
document reflects. It is likely out of date.
On February 19, 2015 3:34:59 PM CST, Gedare Bloom wrote:
>Module:rtems
>Branch:master
>Commit:c53705c384e3cbb9716e2709e5cd3b7bbaa20609
>Changeset:
>http://git.
On 19/02/2015 7:36 pm, Sebastian Huber wrote:
On 19/02/15 00:52, Chris Johns wrote:
On 19/02/2015 7:25 am, Joel Sherrill wrote:
Yep. But if all we have is writeable vector tables at 0x0, then it
MIGHT be
ok. GCC may not be able to detect. But on the m68k's without a VBR
register the table is
Hi,
How can I figure out which targets can be tested with a simulator. I would
like to set up an environment which I can work with further.
Thank you.
On 17 Feb 2015 06:11, "Joel Sherrill" wrote:
>
> On 2/16/2015 6:33 PM, Nick Withers wrote:
> > On Mon, 2015-02-16 at 22:57 +0530, Rohini Kulkar
On 19/02/15 00:52, Chris Johns wrote:
On 19/02/2015 7:25 am, Joel Sherrill wrote:
Yep. But if all we have is writeable vector tables at 0x0, then it
MIGHT be
ok. GCC may not be able to detect. But on the m68k's without a VBR
register the table is always at 0x0.
Yeap ...
https://git.rtems
