POSIX compliance development

Gedare Bloom gedare at rtems.org
Tue Dec 20 20:53:18 UTC 2016


Option #1 writing a script is better. We occasionally add
implementations for POSIX features as needed for various compliance
test requirements or application portability.

On Thu, Dec 15, 2016 at 9:29 AM, Saeed Ehteshamifar
<salpha.2004 at gmail.com> wrote:
> Hello,
>
> For Slingshot, an RTEMS-targeted fault-injection tool for the POSIX API, I
> need to remove the tests that correspond to unimplemented/unimplementable
> POSIX functions/constants/etc. I can either
> 1. write a script that searches for "Unimplemented" and "Unimplementable" in
> the doc's source, and removes the corresponding function's test cases every
> time after generating test cases or,
> 2. manually delete all unimplemented/unimplementable from the Slingshot core
> so that they aren't generated at all.
>
> Now the question is: Apart from unimplementable functions, is there any
> direction to implement unimplemented parts beyond the current situation?
> Cause in that case, I think writing a script is a better option.
>
> Best Regards,
> Saeed
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel


More information about the devel mailing list