On Thu, Feb 27, 2020 at 5:49 AM Eshan Dhawan <eshandhawa...@gmail.com> wrote:
> Also, Should look into ticket #3642 related to adding function prototypes > to wchar.h > Make sure what's left to do is always the first step. :) And make sure you are making progress on a proposal. > > On Thu, Feb 27, 2020 at 5:11 PM Eshan Dhawan <eshandhawa...@gmail.com> > wrote: > >> >> >> On Wed, Feb 26, 2020 at 8:50 PM Joel Sherrill <j...@rtems.org> wrote: >> >>> >>> >>> On Wed, Feb 26, 2020 at 9:06 AM Eshan Dhawan <eshandhawa...@gmail.com> >>> wrote: >>> >>>> so the subtasks would consist of adding missing functions to stat.h , >>>> types.h mainly I suppose >>>> >>> >>> What do you think is missing in those? My reading of the POSIX standard >>> has is implying that >>> <ftw.h> includes <sys/stat.h> to get st_mode and the stat structure. >>> >> Not much related to ftw.h but there are unsupported functions in >> sys/stat.h which can be added >> to Newlib >> > What does your analysis show is missing? The POSIX Compliance document should be right but it is always good to know. For analysis purposes, I would build arm with the xilinx zynq qemu BSP. Then add on rtems-libbsd. The methods can appear in newlib, RTEMS base, or rtems-libbsd. Most likely if it isn't networking related, it will be in the first two. But my tracking spreadsheet indicates mknod() is there with networking which I think sounds odd. Anyway, the Compliance Guide is a good first cut but may have mistakes. Start with good information. > >> Also wanted to know which headers which aren't present in newlib or RTEMS >> which could make my GSOC proposal more acceptable? >> >>> >>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/ftw.h.html >>> >>> The subtasks I referred to as the same for every time a new C Library or >>> POSIX method >>> is added to RTEMS or Newlib: >>> >>> + the code itself >>> + test code >>> + addition to documentation as needed >>> + update to compliance tracking spreadsheet (usually I will do this) >>> >>>> >>>> - Eshan >>>> >>>> On Wed, Feb 26, 2020 at 7:30 PM Joel Sherrill <j...@rtems.org> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Feb 26, 2020 at 7:03 AM Eshan Dhawan <eshandhawa...@gmail.com> >>>>> wrote: >>>>> >>>>>> I wanted to know the status of implementation of ftw.h in newlib >>>>>> and the dependencies it requires? >>>>>> >>>>> >>>>> FIrst hint is that the ticket is still open. :) >>>>> >>>>> The next is a way to check if it is part of the installed C Library. >>>>> Wherever >>>>> you installed the tools (TOOLS_PREFIX) for CPU-rtems5 >>>>> >>>>> find TOOLS_PREFIX -name ftw.h >>>>> CPU-rtems5-nm TOOLS_PREFIX/CPU-rtems5/lib/libc.a | grep ftw >>>>> >>>>> In this case, you will see it isn't there. >>>>> >>>>> >>>>>> >>>>>> As it could be ported from FreeBSD since it lies under favourable >>>>>> licence >>>>>> >>>>> >>>>> Yep. And this would almost certainly need to be merged into the newlib >>>>> C library >>>>> with tests added to RTEMS. >>>>> >>>>> Documentation added to the POSIX Users Guide and the tracking >>>>> spreadsheet >>>>> updated. >>>>> >>>>> Just to list all the subtasks. :) >>>>> >>>>> --joel >>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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
