Skip to content
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

Build Exiv2 without inih library #9437

Merged
merged 1 commit into from
Jan 17, 2023
Merged

Conversation

kevinbackhouse
Copy link
Contributor

This fixes the build failure in Exiv2.

We recently added inih as a dependency to Exiv2, but we need a newer version of inih that includes the C++ bindings. OSS-Fuzz is still using a docker image based on Ubuntu 20.04 which doesn't include a sufficiently up-to-date version of the libinih-dev package. So I've added a build flag to Exiv2 in Exiv2/exiv2#2465 which enables us to build without the inih dependency. The fuzz target doesn't need inih, so it shouldn't make any difference to the fuzzing results.

Copy link
Contributor

@Navidem Navidem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Navidem Navidem merged commit 63e3895 into google:master Jan 17, 2023
eamonnmcmanus pushed a commit to eamonnmcmanus/oss-fuzz that referenced this pull request Mar 15, 2023
This fixes the build failure in Exiv2.

We recently added [inih](https://github.com/benhoyt/inih) as a
dependency to Exiv2, but we need a newer version of inih that includes
the C++ bindings. OSS-Fuzz is still using a docker image based on Ubuntu
20.04 which doesn't include a sufficiently up-to-date version of the
`libinih-dev` package. So I've added a build flag to Exiv2 in
Exiv2/exiv2#2465 which enables us to build
without the inih dependency. The fuzz target doesn't need inih, so it
shouldn't make any difference to the fuzzing results.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants