Hello,
Joan Lledó, le sam. 05 mai 2018 08:01:29 +, a ecrit:
> > > - Not intended to be upstream
> > > autoconf
> > > port
>
> > Why not?
>
> About port, it includes some stack configuration which is only valid for
> us.
Is it not possible to make them valid over all unix variants, and
> > - Not intended to be upstream
> > autoconf
> > port
> Why not?
About port, it includes some stack configuration which is only valid for
us. About autoconf, the stack is distributed without any build system and
the user is expected to provide its own solution. They have a repo called
Samuel Thibault, le mar. 01 mai 2018 01:34:42 +0200, a ecrit:
> > - Won't get to upstream
> > posix
>
> Similarly, why not?
If they really don't want it, we definitely should make this patch more
maitainable by avoiding to move code around, and instead put #ifdef
#endif around, so that changes
Hello,
Joan Lledó, le lun. 30 avril 2018 13:11:11 +0200, a ecrit:
> I've been working on the lwip package and have some patches for the release
> 2.0.3. These patches include:
Thanks!
I have applied them and fixed the build on Linux.
> About patches getting to upstream:
> - Not intended to be
Hello,
I've been working on the lwip package and have some patches for the release
2.0.3. These patches include:
- Solve some bugs on the PORT patch.
- Create a new macro wich allows the user to choose between POSIX or lwip
native socket headers.
- Solve the bug 36167 using the same solution
5 matches
Mail list logo