[Bug 37534] 1.7.30 ./configure errors to report

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Nov 11 15:12:36 CST 2014


https://bugs.winehq.org/show_bug.cgi?id=37534

--- Comment #10 from Todd Chester <ToddAndMargo at zoho.com> ---
(In reply to Dmitry Timoshkov from comment #8)

Hi Guys,

Me again.

Created these two Red Hat bug reports to help with your *bogus* error messages:

libxslt/libXrender is missing dependency on libXxert
https://bugzilla.redhat.com/show_bug.cgi?id=1162848

libpng RPM missing dependency on zlib
https://bugzilla.redhat.com/show_bug.cgi?id=1162842


> IMHO ordinal/not experienced users should not waste their and others people
> time trying to build wine/kernel/any other non-trivial thing/, 

I do have to disagree.  
     ./configure
     make
     make install
are and have been "trivial" in the UNIX/Linux world for years and years.  It is
only "non-trivial" when the config file *IS A MESS* and the authors consider
fixing it to be INVALID.

Now as far as your "ordinal" comment: in comment 1, Sebastian stated:

    "libXrender: You are missing libXrender-devel."

Sebastian is really good at this stuff and he got totally schnockered.  So your
bogus error even schnockered the "experts".

Now, you could always reverse the lines in the the config file so that you
check for these dependencies first, giving decent error reporting.  Probably
take you less time than telling me this is an invalid request.


> there are
> binary packages for them to install/use.

In an ideal world yes.  Unfortunately, I have to live in the Enterprise Linux
world.  Things are purposefully out-of-date.

EL6: the latest AND LAST supported edition (by EPEL [extra packages for
Enterprise Linux]) of Wine is 1.6.1.  It will NEVER be upgraded.  1.6.1 is full
of bugs, many of which haunt me.  And many have been fixed in 1.7.x but I can't
test my bug reports to verify this as I am stuck on 1.6.1

EL7: is 64 bit only and will not run 32 bit Wine.  This effective kills Wine on
EL7.

So, no, usable "binary packages" do not always exit.

The Enterprise Linux crowd (me included) will need to compile Wine by hand more
and more at time goes on.

I am personally compiling 1.7.30 because I am tired of living with the bugs in
1.6.1's RPM.  And I can not respond back to the bugs I have reported on it when
ask to do so.

Just a comment, if you do the following google search:

https://www.google.com/?gws_rd=ssl#q=configure:+WARNING:+libxslt+3%2Fusr%2Flib%2FlibXrender.so.12-bit+development+files+not+found%2C+xslt+won%27t+be+supported

You will find that your bogus error effect a lot more people than me.  Some
never figure them out.  And from your comments here, I do not believe you even
care what trouble it causes other people.

And I suspect, since 1.7.30 will compile under EL 6.5, that EPEL won't upgrade
because they find trudging through all the *bogus* errors to be too much of a
pain in their necks.

I won't bother reopening this.  In the time it would take you all to tell me
fixing these *bugus* errors is invalid, you could have reversed the lines in
the config file so that the dependencies are checked for first, giving a VALID
error message.

Jee Wiz guys!

-T

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list