rtems-4.12 _POSIX_MEMLOCK defined but not available

[Joel Sherrill]

On Wed, Mar 22, 2017 at 9:56 AM, Gedare Bloom <gedare at rtems.org> wrote:

> I'm not sure if we will have mlockall anytime soon.
>
>
We don't swap out so just honoring the call (whatever that means) is a
sufficient implementation.

Can you make sure the newlib features.h file has flags that match the
intended state of your work? I can see making sure it matches where
you are headed.

--joel


> On Wed, Mar 22, 2017 at 10:43 AM, Joel Sherrill <joel at rtems.org> wrote:
> >
> >
> > On Wed, Mar 22, 2017 at 3:29 AM, Heinz Junkes <junkes at fhi-berlin.mpg.de>
> > wrote:
> >>
> >> rtems4.12 (master) defines in include/sys/features.h
> >>
> >> _POSIX_MEMLOCK and _POSIX_MEMLOCK_RANGE to 1
> >>
> >> but mlockall is not available in any library and one can read
> >>
> >> ./rtems/doc/posix1003.1/compliance_list:mlockall(), Not Supported
> >> ./rtems/doc/posix1003.1/ch12.t:mlockall(), Function, Unimplemented
> >>
> > That's right. If Gedare weren't working on adding support, I would say we
> > need to turn it off in newlib. But at this point I am not sure it is
> worth
> > a tool spin to turn this off and then back on in newlib.
> >
> > Gedare.. thoughts?
> >
> > --joel
> >
> >>
> >> heinz
> >>
> >>
> >>
> >> _______________________________________________
> >> users mailing list
> >> users at rtems.org
> >> http://lists.rtems.org/mailman/listinfo/users
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20170322/059daeea/attachment-0002.html>