On Fri, Apr 15, 2016 at 8:50 AM, Joel Sherrill <j...@rtems.org> wrote: > > > On Fri, Apr 15, 2016 at 4:18 AM, Chris Johns <chr...@rtems.org> wrote: >> >> >> > On 15 Apr 2016, at 7:13 PM, Sebastian Huber >> > <sebastian.hu...@embedded-brains.de> wrote: >> > >> > >> > >> >> On 15/04/16 10:28, Chris Johns wrote: >> >>> On 15/04/2016 18:22, Sebastian Huber wrote: >> >>> >> >>>> On 15/04/16 09:53, Chris Johns wrote: >> >>>> The following is just a small sample of the errors I am seeing with >> >>>> the latest tools building libbsd. Anyone else seeing these? >> >>> >> >>> What are the latest tools for you in this case? >> >> >> >> tools/rtems-gcc-6-20160327-newlib-2.4.0-1 >> > >> > Ok, I didn't use this tool set up. I work currently with the latest >> > Newlib to sort out the <sys/types.h> incompatibilities. >> > >> > I do a RSB build now and have a look at this next week. >> > >> >> Thanks. Joel will be about sometime soon. I am off and out for the weekend >> ... my week does start before yours. :) >> >> >> >> >> Reverting to tools/rtems-gcc-6-20160228-newlib-2.3.0.20160226-1 get >> >> further not breaks with a different error ... >> >> >> >> In file included from >> >> /opt/work/rtems/4.12/i386-rtems4.12/include/sys/time.h:47:0, >> >> from >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/rtemsbsd/include/rtems/bsd/sys/time.h:34, >> >> from >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/contrib/libpcap/pcap/pcap.h:47, >> >> from ../../freebsd/contrib/libpcap/pcap-int.h:39, >> >> from ../../freebsd/contrib/libpcap/scanner.l:51: >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:104:18: >> >> error: unknown type name 'fd_set' >> >> int pselect(int, fd_set *__restrict, fd_set *__restrict, fd_set >> >> *__restrict, >> >> ^~~~~~ >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:104:38: >> >> error: unknown type name 'fd_set' >> >> int pselect(int, fd_set *__restrict, fd_set *__restrict, fd_set >> >> *__restrict, >> >> ^~~~~~ >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:104:58: >> >> error: unknown type name 'fd_set' >> >> int pselect(int, fd_set *__restrict, fd_set *__restrict, fd_set >> >> *__restrict, >> >> ^~~~~~ >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:109:17: >> >> error: unknown type name 'fd_set' >> >> int select(int, fd_set *, fd_set *, fd_set *, struct timeval *); >> >> ^~~~~~ >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:109:27: >> >> error: unknown type name 'fd_set' >> >> int select(int, fd_set *, fd_set *, fd_set *, struct timeval *); >> >> ^~~~~~ >> >> >> >> /opt/work/chris/rtems/libbsd/rtems-libbsd.master/freebsd/sys/sys/select.h:109:37: >> >> error: unknown type name 'fd_set' >> >> int select(int, fd_set *, fd_set *, fd_set *, struct timeval *); >> >> ^~~~~~ >> >> Chris >> > >> > Yes, this is due to a bug in Newlib fixed with a later snapshot. >> > > Jeff and I both have built rtems-libbsd with the latest RSB tools for i386 > and > didn't see any issues. Chris.. you got me through a waf submodule update > yesterday and it built fine after that. > <hijack> I've been looking for a suitable set of instructions for running libbsd networking tests. Do any such notes exist, especially for a qemu target? </hijack>
> All I can say that I expected issues due to the feature guard changes and > as soon as Sebastian's patch set is in and there is a newlib snapshot, we > need to bump the tools again. > > In the mean time, do we want the RSB to apply that patch? We also have > the crt0.c one. > > --joel > >> >> > -- >> > Sebastian Huber, embedded brains GmbH >> > >> > Address : Dornierstr. 4, D-82178 Puchheim, Germany >> > Phone : +49 89 189 47 41-16 >> > Fax : +49 89 189 47 41-09 >> > E-Mail : sebastian.hu...@embedded-brains.de >> > PGP : Public key available on request. >> > >> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. >> > >> >> _______________________________________________ >> 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 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
