I'm guessing its because of routes being defined as ioctls with slightly
different header files in Hurd vs BSD (?) Likely Samuel's solution is correct
to guard against incompatible headers being included in the Hurd path.
Alternatively one could group the Hurd headers better so both APIs require
Joan Lledó, le jeu. 10 oct. 2024 17:36:27 +0200, a ecrit:
> On 10/10/24 17:18, Samuel Thibault wrote:
> >> How can we fix this?
> >
> > We'd probably add && (!defined(__GNU__)) in the dhcpcd source code.
>
> But doesn't that mean we are actually not compatible?
Yes.
I don't know the details conc
Hello,
Joan Lledó, le jeu. 10 oct. 2024 17:05:43 +0200, a ecrit:
> It fails because apparently we define the `BSD` macro. I checked it and it
> comes from glibc:
>
> https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/mach/hurd/bits/param.h;h=48eeb7ddf5d62942d15705e0bcc19db05ed28fc7;hb=HEAD#
On 10/10/24 17:18, Samuel Thibault wrote:
>> How can we fix this?
>
> We'd probably add && (!defined(__GNU__)) in the dhcpcd source code.
>
But doesn't that mean we are actually not compatible?
Also, that's error prone bc without a deeper knowledge about the
codebase it's hard to tell in whic
Hi,
This comes from:
https://lists.debian.org/debian-hurd/2023/11/msg00030.html
I was trying to build the dhcpcd package on the Hurd and it fails with
this error:
```
In file included from arp.h:46,
from privsep.h:134,
from dhcpcd.h:96,
from
