Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63781 > unrolled thread
| Started by | Sergio Gelato <sergio.gelato@astro.su.se> |
|---|---|
| First post | 2019-04-06 12:40 +0200 |
| Last post | 2019-04-06 12:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Sergio Gelato <sergio.gelato@astro.su.se> |
|---|---|
| Date | 2019-04-06 12:40 +0200 |
| Subject | Bug#926483: FTBFS: utils/blkmapd/device-discovery.c:156: undefined reference to `major' |
| Message-ID | <xJQTT-2ZW-3@gated-at.bofh.it> |
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 top | Article view | linux.debian.kernel
csiph-web