http://bugs.winehq.org/show_bug.cgi?id=20042
--- Comment #38 from Thomas Orgis thomas-forum@orgis.org 2010-02-13 11:29:27 --- OK, last try. I really want to avoid having to support both 32 and 64 bit file offsets in the library. One reason might be that it is really not needed that much. We all build with support for large files, right?
Please have a look at the new preliminary mpg123-1.10.1: http://mpg123.org/download/mpg123-1.10.1-prerelease.tar.bz2
I now dropped the protection in the header that wanted to prevent misconfiguration of large file support and instead just blindly use the _FILE_OFFSET_BITS symbol that is defined when including the header. What you have _FILE_OFFSET_BITS == 64, you app will look for mpg123_open_64, if it is not defined, it will look for mpg123_open. Inconsistent setups will fail later at the linking stage, and any user must now figure out herself that the missing symbols are because of large file support mismatch.
I have a FAQ entry already because people did not understand the error message I wrote to explain the breakage... now I will add a new passage about "Missing symbol bla_64?!", pointing to the explanation that is already there. This 32/64 bit off_t mess is a crappy mess and painting over it does not help, obviously.
So, when you folks look at the prerelease version and the header it installs, which indeed is identical now for 32 or 64 bits -- are you happy? Will everyone upgrade to 1.10.1 once I release it to have this fixed (one can dream;-)?