Source: collectd
Version: 5.7.2-2
Hi,
I ran into an FTBFS as well when I wanted to rebuild in Ubuntu to pick
up the new DPDK 17.11.
I found [1], but I wasn't sure if the reported warning on liblvm2app
is "the" FTBFS. I mean collectd due to the way it works uses plenty of
libs and that way is easy to become outdated.
But while deprecated it doesn't look like an actual error to me.
Before finding this bug I was wondering more about:
error: 'i2c_smbus_read_i2c_block_data' undeclared (first use in this
function); did you mean 'i2c_smbus_ioctl_data'?
But due to the mass of libs used (and tests done due to that) I
wondered if maybe even something completely else would be the issue.
It turns out we were both right.
In my case barometer was dependency-error breaking configure due to
actually i2c failing. This is due to changes to libi2c version 4.0 in
the Archive.
Once I removed barometer from being enabled it continued to run into
the bug pointed out by [1].
I see no upstream fixes for either yet.
TL;DR: we have an additional issue with the newer i2c libs.
Upstream in i2c this came by the change:
commit 251d594fd0d338c7b85707a2e72153a404a25b10
Author: Jean Delvare <jdelv...@suse.de>
Date: Mon May 21 16:52:48 2012 +0000
New library for I2C device access under Linux. As a first step, the
library will host the i2c_smbus_*() inline functions which were
previously in the user-space flavor of <linux/i2c-dev.h>.
I reported the issue upstream at [2] so they can add a proper
toleration for the change in the i2c lib.
Note: short term the following does the trick to get it building at
least (obviously without i2c&barometer):
confflags += --disable-barometer
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881641
[2]: https://github.com/collectd/collectd/issues/2646
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
