https://bugs.winehq.org/show_bug.cgi?id=37534
--- Comment #5 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Todd Chester from comment #3)
Indeed I am missing it. Would you please fix the error message so that it states plainly which LibGL is wants. "Yum whatprovies */opengl" lights up with probably 50 choices. Not from the log or any other source did it state "mesa-libGL".
The wine package is built for various different distributions and operating systems. Its not possible to give precise package names for your distribution, because its of cause called differently everywhere. If you ask me, the current names are good enough, and the usual way to track down dependency errors is to look at config.log anyway. Most of ./configure is autogenerated, which makes it difficult/impossible to give precise error messages about what went wrong. Thats what the log file is for.
I am pretty sure that there are existing packages for RHEL or similar distros, why don't you look up the dependency names there, instead of trying to guess them?
The log I attached is 63084 lines long. There is a longer one? Oh my goodness!
You didn't attach any log?!
configure:10935: libxslt cflags: -I/usr/include/libxml2 configure:10936: libxslt libs: -lxslt -lz -lm -lxml2 ... configure:10957: checking for -lxslt configure:10982: gcc -m32 -o conftest -g -O2 -I/usr/include/libxml2 conftest.c -lxslt -lxslt -lz -lm -lxml2 >&5 /usr/bin/ld: skipping incompatible /usr/lib64/libz.so when searching for -lz /usr/bin/ld: cannot find -lz <------------------------------------------ collect2: ld returned 1 exit status configure:10982: $? = 1
When you already know that its complaining because of missing zlib-devel, why don't you install it?
Again, I do apologize. The purpose of this bug report was to get yo to fix the reporting errors and the "-lz" error. I thought it was clearly apparent that I was reporting bugs here and asking for help over there.
I have to agree with Rosanne, so far I don't see any real bug in here. I've also looked up, and you indeed asked most of these questions also on the forums, but without following the advice (installing zlib development files was also suggested there, for example). If you wanted to open this bug about the general issue that ./configure in some situations reports imprecise error messages, you should have made this more clear from the beginning, to avoid confusion.
For general help how to compile wine the forums or #winehq (on freenode) are more appropriate, it is only a bug in wine when the detection really fails although you have everything installed.