On Sun, Mar 22, 2020 at 1:22 PM Eshan Dhawan <eshandhawa...@gmail.com> wrote: > > confstr() from unistd.h also shows not supported in the compliance status > but it has some kind of supported in newlib(libc/sys/linux)
sys/linux doesn't work on rtems. that is only for linux-specific newlib builds > it also needs to be updated in the compliance status I think > > On Mon, Mar 23, 2020 at 12:37 AM Eshan Dhawan <eshandhawa...@gmail.com> wrote: >> >> https://lists.rtems.org/pipermail/devel/2020-March/058569.html >> >> >> On Mon, Mar 23, 2020 at 12:35 AM Eshan Dhawan <eshandhawa...@gmail.com> >> wrote: >>> >>> >>> >>> On Mon, Mar 23, 2020 at 12:27 AM Joel Sherrill <j...@rtems.org> wrote: >>>> >>>> >>>> >>>> On Sun, Mar 22, 2020, 1:55 PM Eshan Dhawan <eshandhawa...@gmail.com> wrote: >>>>> >>>>> It's present there. >>>>> I hadn't checked there. >>>> >>>> >>>> Does that mean the spreadsheet I uploaded yesterday needs updating again? >>> >>> yes , the spreadsheet shows not supported. >>> also, I have sent another mail related to this >>> for wordexp.h >>> >>>> >>>> Is there a ticket to close? >>> >>> No the ticket was closed earlier >>> I missed that >>>> >>>> Finding something got added without the tracking update is a good outcome >>>> >>>>> >>>>> On Mon, Mar 23, 2020 at 12:19 AM Joel Sherrill <j...@rtems.org> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Mar 22, 2020, 1:37 PM Eshan Dhawan <eshandhawa...@gmail.com> >>>>>> wrote: >>>>>>> >>>>>>> I have identifies 2 main sources to port sockatmark(). >>>>>>> >>>>>>> NetBSD source: >>>>>>> https://github.com/NetBSD/src/blob/trunk/lib/libc/net/sockatmark.c >>>>>>> >>>>>>> FreeBSD Source : >>>>>>> https://github.com/lattera/freebsd/blob/master/lib/libc/net/sockatmark.c >>>>>>> >>>>>>> musl has a same implementation as in FreeBSD >>>>>>> which one would be better to follow. >>>>>> >>>>>> >>>>>> This has to be in sync with rtems-libbsd and may already be there. >>>>>> Please check if it is there. Just closing a ticket and updating the >>>>>> spreadsheet is q food result. :) >>>>>>> Should it also be available in "legacy" networking stack? Or do we let that bitrot / maintain only? >>>>>>> >>>>>>> thanks >>>>>>> -Eshan > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
