Re: Bug#256669: e2fsprogs: FTBFS(hurd-i386): uses undefined struct sockaddr_dl

2004-08-31 Thread Ognyan Kulev
Theodore Ts'o wrote: We do try using SIOCGIFWHADDR; but it's not being defined apparently given the header files we're including. If you could take a look at gen_uuid.c (attached) and tell me what I'm doing wrong for the Hurd. AF_LINK is defined unconditionally in glibc, along with all other ad

Re: Bug#256669: e2fsprogs: FTBFS(hurd-i386): uses undefined struct sockaddr_dl

2004-08-02 Thread Theodore Ts'o
On Mon, Aug 02, 2004 at 12:06:11PM +0200, Marco Gerards wrote: > > It should not be hard to add SIOCGIFHWADDR if it is really important. > Just have a look at hurd/iioctl.defs and pfinet/iioctl-ops.c in the > Hurd sourcecode. > We do try using SIOCGIFWHADDR; but it's not being defined apparently

Re: Bug#256669: e2fsprogs: FTBFS(hurd-i386): uses undefined struct sockaddr_dl

2004-08-02 Thread Marco Gerards
Göran Weinholt <[EMAIL PROTECTED]> writes: >> This seems to be because the hurd defines AF_LINK without defining >> struck sockaddr_dl. The sockaddr_dl/AF_LINK code was added to support >> grabbing the local MAC of an local ethernet interface for >> MacOS/Darwin. Apparently the Hurd doesn't prov

Re: Bug#256669: e2fsprogs: FTBFS(hurd-i386): uses undefined struct sockaddr_dl

2004-08-02 Thread Göran Weinholt
On Thu, Jul 29, 2004 at 08:45:15PM -0400, Theodore Ts'o wrote: > On Mon, Jun 28, 2004 at 01:55:49PM +0200, G?ran Weinholt wrote: > > Package: e2fsprogs > > Version: 1.35-6 > > Severity: important > > > > e2fsprogs fails to build on hurd-i386. struct sockaddr_dl is not > > defined anywhere in glibc