Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'

To: "926483@bugs.debian.org" <926483@bugs.debian.org>
Cc: "micha@debian.org" <micha@debian.org>
Subject: Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'
From: Sergio Gelato <sergio.gelato@astro.su.se>
Date: Sat, 6 Apr 2019 10:22:44 +0000
Message-id: <[🔎] 3a704d18f25f4bd0928cdb2b6a6dfb27@astro.su.se>
Reply-to: Sergio Gelato <sergio.gelato@astro.su.se>, 926483@bugs.debian.org
References: <[🔎] 155450115753.15109.14286077765728349774.reportbug@fuzzy.home.lenk.info>

major(dev) is defined as a macro in <sys/sysmacros.h> which is provided by libc6-dev.  I don't see that listed as an explicit build dependency, so it's conceivable that it might be present in some build environments but not in others. The configure script tests for it, potentially leading to #define MAJOR_IN_SYSMACROS 1 (and/or to #define MAJOR_IN_MKDEV 1, but <sys/mkdev.h> seems associated with ZFS and the Solaris Porting Layer only).

Would it be wrong to add an explicit build dependency on libc6-dev? Does it actually cure the FTBFS?

Reply to:

References:
- Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'
  - From: Micha Lenk <micha@debian.org>

Prev by Date: Re: Why don't we have linux-5.0 instead of 4.19.0-4 which is the running kernel in Debian 'buster' i.e. testing ?
Next by Date: Bug#926261: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#926261: linux-image-4.19.0-4-amd64: fan continiously spinning above 6900 RPM after resume on lenovo carbon x1 thinkpad with isa adapter)
Previous by thread: Processed: RE: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'
Next by thread: Bug#926483: marked as done (FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major')
Index(es):
- Date
- Thread