| Summary: | app-emulation/wine-vanilla USE=-mono - /usr/lib/wine-vanilla-4.0.2/bin/wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
| Component: | Current packages | Assignee: | Wine Maintainers <wine> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Hi Jeroen, Does this occur on wine-vanilla-4.0.3? Also, what are the specific reproduction steps? Thanks, Nick (In reply to Nick Sarnie from comment #1) > Also, what are the specific reproduction steps? I described those in comment #0. Is this still reproducible? |
With USE=-mono, the wine executable fails to find its dynamically linked libraries. I happened to discover this when I grasped for a straw and set USE=mono. After re-emerging, suddenly the problem disappeared. With USE=-mono: $ wine-vanilla-4.0.2 /usr/lib/wine-vanilla-4.0.2/bin/wine: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory After re-emerging with USE=mono: $ wine-vanilla-4.0.2 Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --version Output version information and exit Perhaps the pkg_postinst() message for the `! use mono` case should be updated to reflect that, or the actual problem could be fixed instead.