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
Wunused-parameter introduced in #1731 breaks the "make config" phase on Mingw64/Msys64 #1772
Comments
The merge pull request #1731 introduced the gcc warning flag Wextra, which in the presents of the Wall warning flag, turns on the warning flag Wunused-parameter. The latter warning flag breaks the “make config” phase on a stock native mingw64/msys64 system (with a windows-installer2 ruby 2.5.1) see below. The compilation completes successfully if the Wextra flag is replaced (leaving out the offending Wunused-parameter warning flag) with the longish warning flag collection -Wbad-function-cast -Wempty-body -Wignored-qualifiers -Wimplicit-fallthrough=3 -Wmissing-field-initializers -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -Wsign-compare -Wtype-limits -Wuninitialized -Wshift-negative-value -Wunused-but-set-parameter "pkg-config --exists libxml-2.0" package configuration for libxml-2.0 is not found |
Thanks for reporting, will investigate this weekend. |
See conversation going on at #1731, I'm having trouble reproducing this. |
I can reproduce the same issues on Fedora and I think the difference is the availability of pkg-config gem:
|
Just FTR, I'd be glad if system pkg-config is enough and I don't need pkg-config gem ... |
Ah, there is a longer discussion in #1731 ... Will continue there ... |
Reproducible on Ubuntu Xenial or Bionic. This Dockerfile reproduces it, just put it in an empty dir and run
|
@johnl Thanks for the repro, investigating now. |
@johnl your repro provides the same errors that @knu's repro in #1731 provides, to wit:
which gives me confidence that we only have one problem here, and not multiple. Working on integrating a fix (and regression tests for this scenario). |
This will be fixed in 1.8.5, due out soon. |
If you're having trouble installing Nokogiri ...
Have you tried following the installation tutorial?
What is the output of
gem install
?What are the contents of the
mkmf.log
file?What operating system are you using?
If this isn't an installation issue ...
What problems are you experiencing?
What's the output from
nokogiri -v
?Can you provide a self-contained script that reproduces what you're seeing?
The text was updated successfully, but these errors were encountered: