[Bug 1231821] New: Regression: winegcc requires absolute library path
https://bugzilla.suse.com/show_bug.cgi?id=1231821 Bug ID: 1231821 Summary: Regression: winegcc requires absolute library path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs@suse.de Reporter: aleithner@level101.at QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Using winegcc from wine-devel currently requires setting the -L flag to be able to link Winelib DLLs. E.g., it is required to include -L/usr/lib64/wine/i386-unix when compiling and linking a 32-bit Winelib DLL. Building Wine from source on my machine yields a winegcc which knows where Wine's libraries and archives are located (making -L unnecessary). It was hinted that specifying -L explicitly should not be needed on the Wine developer's mailing list. For context and reference, see the Wine Developer's mailing list thread [1] where I have asked about this originally. [1]: https://list.winehq.org/mailman3/hyperkitty/list/wine-devel@winehq.org/threa... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231821 https://bugzilla.suse.com/show_bug.cgi?id=1231821#c2 Aaron Puchert <aaronpuchert@alice-dsl.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaronpuchert@alice-dsl.net --- Comment #2 from Aaron Puchert <aaronpuchert@alice-dsl.net> --- Unlike your bug 1231820, this doesn't show up in the wine-nine-standalone build [1]. Looking through the differences, I'm thinking it might be -mwindows? But I haven't looked into it because it works for this package. [1] https://build.opensuse.org/package/show/home:aaronpuchert:branches:Emulators... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231821 https://bugzilla.suse.com/show_bug.cgi?id=1231821#c3 --- Comment #3 from Alexander Leithner <aleithner@level101.at> --- (In reply to Aaron Puchert from comment #2)
Unlike your bug 1231820, this doesn't show up in the wine-nine-standalone build [1]. Looking through the differences, I'm thinking it might be -mwindows? But I haven't looked into it because it works for this package.
[1] https://build.opensuse.org/package/show/home:aaronpuchert:branches:Emulators... wine-nine-standalone
If you're referring to -mwindows when building a binary with winegcc, that should not make a difference as, per the man page of winegcc and winebuild, it only adds a bunch of -l flags and forces the entry point to be WinMain. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231821 https://bugzilla.suse.com/show_bug.cgi?id=1231821#c4 --- Comment #4 from Aaron Puchert <aaronpuchert@alice-dsl.net> --- (In reply to Alexander Leithner from comment #3)
If you're referring to -mwindows when building a binary with winegcc, that should not make a difference as, per the man page of winegcc and winebuild, it only adds a bunch of -l flags and forces the entry point to be WinMain.
The man page could be incomplete. Anyway, you can see in the build log that the linker succeeds without passing a library directory (https://build.opensuse.org/package/live_build_log/home:aaronpuchert:branches...). Note that -L@WINE32_LIBDIR@ doesn't do anything because such a directory doesn't exist. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com