On Mon, Apr 27, 2020, 12:54 PM Gregory Nutt <spudan...@gmail.com> wrote:

>
> > I have a WIP CI run on my fork for Windows using Cygwin (it a bit ugly
> > right now), but it has a fair amount of sim builds failing. Could someone
> > take a look. I'll put a draft PR up tonight for CI but for now this is
> what
> > I have.
> >
> >
> https://github.com/btashton/incubator-nuttx/runs/623326287?check_suite_focus=true
> >
> > It also times out, but that can be dealt with later.
>
> Most of these are failures related to networking with the simulator
> under Windows with wpcap.  That networking logic is very different under
> Windows than Linux where a tap driver is used. That logic has not been
> used in a decade AFAIK and I am not sure if it ever worked.  I believe
> that these are real errors, but probably not fixable in the short term.
> I think we cannot test simulator-based network under windows right now.
>
> I vaguely recall someone telling that they had networking with wpcap
> working a decade or so ago, but I have heard of no used since them.  It
> probably should be marked EXPERIMENTAL.
>
> sim/module:
>
> This looks like a conflict between Cygwin header files and w32api headers
>
>     /usr/include/cygwin/socket.h:27:8: error: redefinition of 'struct
>     sockaddr'
>
>     27 | struct sockaddr {
>
>     /usr/include/w32api/psdk_inc/_ip_types.h:70:8: note: originally
>     defined here
>
>     70 | struct sockaddr {
>
> Similarly with struct linger, the prototype of socket functions, and
> probably other things.  My only conclusion is that wpcap is not
> compatible with Cygwin?  This may not be something we are able to fix,
> or perhaps it is something that could be fixed as simply as removing
> some includes from up_wpcap.c?
>
> sim/nettest:  Same issues
> sim/tcpblaster: Same issues
>
> Everything else looks fine.
>
> Greg
>

Makes sense. Maybe we can create a test dat file for the windows builds
that only targets the sim configs we care about? Maybe another for a set of
ARM targets?  Thanks for helping me understand what's going on.

--Brennan

>

Reply via email to