[Bug 57875] New: wine cannot load/use system faudio PE library
https://bugs.winehq.org/show_bug.cgi?id=57875 Bug ID: 57875 Summary: wine cannot load/use system faudio PE library Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: arusanu.bu(a)gmail.com Distribution: --- Wine fails to use the system PE FAudio library for FAudio version 25.02, and it falls back on the bundled FAudio library. Wine can still load/accept older system FAudio libraries, but something must have changed in FAudio that makes Wine fail to identify the newer versions of FAudio libraries as valid versions. Config output snippet when Wine is checking faudio-25.02: ' checking for x86_64-w64-mingw32-pkg-config... x86_64-w64-mingw32-pkg-config checking for MinGW FAudio.h... yes checking for FAudio_CommitOperationSet in MinGW -lFAudio... no checking for MinGW fluidsynth.h... yes checking for new_fluid_synth in MinGW -lfluidsynth... yes ' I've tested this behavior on Wine 10.0 and up, with the older and newer versions of the MinGW-FAudio libraries built under the same environment. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- Latest Wine is bundling 25.02 and that works fine, so it sounds like the external one is broken. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #2 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...the obvious question: what's in config.log when the test fails ? Also, if I'm reading that block correctly, it checks for *mingw* (i.e. Windows) build of FAudio, not the linux lib. If you're actually referring to a system PE version, that's a bit odd, but config.log should clear it up. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #3 from aurb <arusanu.bu(a)gmail.com> --- Created attachment 78094 --> https://bugs.winehq.org/attachment.cgi?id=78094 build log wine10.1 with system mingwn PE libraries Attached is the full build log for wine 10.1 using all available system PE/mingw libraries. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #4 from aurb <arusanu.bu(a)gmail.com> --- Created attachment 78095 --> https://bugs.winehq.org/attachment.cgi?id=78095 just the configure output - not the whole log -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #5 from aurb <arusanu.bu(a)gmail.com> --- (In reply to Rafał Mużyło from comment #2)
...the obvious question: what's in config.log when the test fails ?
Also, if I'm reading that block correctly, it checks for *mingw* (i.e. Windows) build of FAudio, not the linux lib. If you're actually referring to a system PE version, that's a bit odd, but config.log should clear it up.
Yes, I'm using available system PE libraries. Since the use of system PE libraries was enabled (Wine 8.+ version?), I haven't had any issues using them instead of Wine bundled ones. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #6 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...in case of autotools configure scripts, config.log is an actual file. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 --- Comment #7 from aurb <arusanu.bu(a)gmail.com> --- Created attachment 78096 --> https://bugs.winehq.org/attachment.cgi?id=78096 config log Sorry for that, I had to regenerate it. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- Looks like the pkgconfig cflags contain "-Dmain=SDL_main" which breaks configure. That's a packaging bug. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=57875 aurb <arusanu.bu(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID --- Comment #9 from aurb <arusanu.bu(a)gmail.com> --- OK(In reply to Alexandre Julliard from comment #8)
Looks like the pkgconfig cflags contain "-Dmain=SDL_main" which breaks configure. That's a packaging bug.
You are right! I haven't noticed that my distribution's mingw-faudio package version caught up with my own version, and Wine used it for building. Thanks for the support, and please excuse my bogus entry. I will set this bug as an invalid bug. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=57875 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Closing bugs marked as invalid. -- 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.
participants (1)
-
WineHQ Bugzilla