15/04/2021 00:08, Dmitry Kozlyuk:
> 2021-04-14 14:47 (UTC-0700), Ranjit Menon:
> > On 4/14/2021 2:42 PM, Thomas Monjalon wrote:
> > > 14/04/2021 23:34, Ranjit Menon:
> > >> On 4/14/2021 2:12 PM, Thomas Monjalon wrote:
> > >>> 13/04/2021 09:00, Dmitry Kozlyuk:
> > Hi Ranjit,
> >
> >
2021-04-14 14:47 (UTC-0700), Ranjit Menon:
> On 4/14/2021 2:42 PM, Thomas Monjalon wrote:
> > 14/04/2021 23:34, Ranjit Menon:
> >> On 4/14/2021 2:12 PM, Thomas Monjalon wrote:
> >>> 13/04/2021 09:00, Dmitry Kozlyuk:
> Hi Ranjit,
>
> 2021-04-12 21:46 (UTC-0700), Ranjit Menon:
>
On 4/14/2021 2:42 PM, Thomas Monjalon wrote:
14/04/2021 23:34, Ranjit Menon:
On 4/14/2021 2:12 PM, Thomas Monjalon wrote:
13/04/2021 09:00, Dmitry Kozlyuk:
Hi Ranjit,
2021-04-12 21:46 (UTC-0700), Ranjit Menon:
[...]
The change to remove the networking shim breaks l2fwd compilation on
Windo
14/04/2021 23:34, Ranjit Menon:
> On 4/14/2021 2:12 PM, Thomas Monjalon wrote:
> > 13/04/2021 09:00, Dmitry Kozlyuk:
> >> Hi Ranjit,
> >>
> >> 2021-04-12 21:46 (UTC-0700), Ranjit Menon:
> >> [...]
> >>> The change to remove the networking shim breaks l2fwd compilation on
> >>> Windows, since l2fwd/
On 4/14/2021 2:12 PM, Thomas Monjalon wrote:
13/04/2021 09:00, Dmitry Kozlyuk:
Hi Ranjit,
2021-04-12 21:46 (UTC-0700), Ranjit Menon:
[...]
The change to remove the networking shim breaks l2fwd compilation on
Windows, since l2fwd/main.c includes netinet/in.h explicitly.
How do you propose we
13/04/2021 09:00, Dmitry Kozlyuk:
> Hi Ranjit,
>
> 2021-04-12 21:46 (UTC-0700), Ranjit Menon:
> [...]
> > The change to remove the networking shim breaks l2fwd compilation on
> > Windows, since l2fwd/main.c includes netinet/in.h explicitly.
> >
> > How do you propose we fix this, only for Window
Hi Ranjit,
2021-04-12 21:46 (UTC-0700), Ranjit Menon:
[...]
> The change to remove the networking shim breaks l2fwd compilation on
> Windows, since l2fwd/main.c includes netinet/in.h explicitly.
>
> How do you propose we fix this, only for Windows?
This include is redundant for this file on all
Hi Dmitry,
On 4/10/2021 3:47 PM, Dmitry Kozlyuk wrote:
On Windows, EAL contains two sets of functions and macros for POSIX
compatibility: and a networking shim (socket headers).
The latter conflicts with system headers and should not exist.
Exposing the former from EAL can break consumer own PO
On Windows, EAL contains two sets of functions and macros for POSIX
compatibility: and a networking shim (socket headers).
The latter conflicts with system headers and should not exist.
Exposing the former from EAL can break consumer own POSIX compatibility
layer and is against standards in genera
9 matches
Mail list logo
