[PATCH 1/2] Confstr Port for RTEMS

[Joel Sherrill]

I don't care where we provide it.

The list of names varies a bit based on the version of POSIX you are based
on.  We probably can just use the FreeBSD version minus the standard path
which makes no sense on RTEMS. They just detect you are running on a
supported environment or not. They only support one at a time like we do.

If it is libbsd, it stays up to date easier since we following FreeBSD
seems reasonable. Happy to see it deleted from libbsd and put in rtems
though since it doesn't have a bunch of dependencies.

On Thu, Aug 13, 2020 at 2:42 AM Chris Johns <chrisj at rtems.org> wrote:

> On 13/8/20 3:54 pm, Sebastian Huber wrote:
> > On 12/08/2020 21:07, Gedare Bloom wrote:
> >
> >> Chris, Christian, Sebastian:
> >>
> >> I think it would be best if one of you may have insight on this
> touching libbsd.
> > Is libbsd really the right place for this function? Do we need the
> ability to
> > synchronize it with FreeBSD? Are FreeBSD and RTEMS similar enough to
> share an
> > implementation of confstr()?
>
> Good question, I am not sure. What is the list of `names` we have to
> support?
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200813/9461498c/attachment-0001.html>