New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i2c 4.0 breaks current assumptions in configure #2646
Labels
Comments
Not fully matching current master, so no PR, but seems to work on test packaging builds, so FYI:
|
rpv-tomsk
added a commit
to rpv-tomsk/collectd
that referenced
this issue
May 19, 2018
rpv-tomsk
added a commit
to rpv-tomsk/collectd
that referenced
this issue
May 19, 2018
Many thanks, Christian! |
codesmith14
pushed a commit
to signalfx/collectd
that referenced
this issue
Jun 15, 2018
nmdayton
pushed a commit
to Stackdriver/collectd
that referenced
this issue
Jan 17, 2019
nmdayton
pushed a commit
to Stackdriver/collectd
that referenced
this issue
Jan 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
Configure works
Actual behavior
Configure fails to detect i2c:
Steps to reproduce
The actual i2c detection doesn't break it which might make this less detected at first.
But if you have e.g. barometer enabled it fill fail via dependency error which makes it fatal.
Reason this happens
in i2c these methods were moved to a proper library
So there now is a proper -li2c to be used to be able to get to those symbols.
I'm not a configure magician enough to get that fixed fast, but at least wanted to report so you can take a look.
The text was updated successfully, but these errors were encountered: