https://bugs.winehq.org/show_bug.cgi?id=37578
Todd Chester ToddAndMargo@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |---
--- Comment #15 from Todd Chester ToddAndMargo@zoho.com --- (In reply to Rosanne DiMesio from comment #14)
From the config.log:
configure:19080: libz 32-bit development files not found, data compression won't be supported.
The message is there; you're the one who chose to ignore it.
Hi Rosanne,
You are changing the subject in order to close this Enhancement Request as INVALID. This request should not be closed until the NONSENSICAL errors output to the user from ./configure are corrected.
The config.log is how I found the ACTUAL problem. The errors I am speaking of on this Enhancement Request are the WEIRD, NONSENSICAL errors you get from the ./configured report:
configure: WARNING: libxslt 32-bit development files not found, xslt won't be supported. and
configure: WARNING: libpng 32-bit development files not found, PNG won't be supported.
Which have nothing to do with libz missing, hence the remark that these errors are NONSENSICAL.
The purpose of this enhancement it to restore some sanity to the errors that come out on the ./configure report.
One should not have to open config.log to figure out a bunch Microsoft style NONSENSICAL errors to do a "./configure; make; make install". These are common command used by UNIX/Linux users from years and years. It is not expected that they should have intimate knowledge of the process to figure out when the program says "salt", it actually means "pepper".
And the purpose of the config.log is to assist the developers in restoring some SANITY into the error messages about libz missing. Not for you to close the request as INVALID.
-T