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

From	Sergio Gelato <sergio.gelato@astro.su.se>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major'
Date	2019-04-06 12:40 +0200
Message-ID	<xJQTT-2ZW-3@gated-at.bofh.it> (permalink)
References	<xJF2q-3XX-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

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?

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major' Sergio Gelato <sergio.gelato@astro.su.se> - 2019-04-06 12:40 +0200

csiph-web