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/thread/QTPFXY3CHG2TJUPBNE3CGXIKBFRH5CPH/