On Friday, 2 November 2012 10:13:30 David Chisnall wrote: > On 2 Nov 2012, at 05:24, Jan Beich wrote: > >> Known Issues > > > > emulators/wine doesn't work with lib32 built by clang, probably due to > > wine bugs. > > Is this still the case? There was an issue preventing WINE from working > because it required stricter stack alignment than clang provided by > default, but I thought it was fixed. Does WINE work if compiled with the > flag that forces stack realignment? If not, then it's some other issue... There are two issues here: 1) wine compiled with clang, and 2) wine (compiled with gcc) running on clang compiled base. Regarding 1), according to the wiki [1], wine does have stack alignment issues and some wine programs do not run when compiled with clang [2][3] and other bugs with clang cause freezing within wine [4][5]. The impression I get is that, using the work-a-round of stack realignment, wine does work to some extent when compiled by clang. Regarding 2) (which I believe Jan was referring to), when I have a gcc built world and just replace lib32 with clang built libraries I have winecfg and regedit launching but displaying black screens. Switching back to gcc built lib32 I get a working winecfg and regedit. This, to me, indicates a clang error somewhere. The test was done on FreeBSD 9-Stable with: # clang --version FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 Target: x86_64-unknown-freebsd9.0 Thread model: posix Regards [1] wiki.winehq.org/Clang [2] (regedit) http://llvm.org/bugs/show_bug.cgi?id=9830 [3] (wineboot) http://llvm.org/bugs/show_bug.cgi?id=9844 [4] http://llvm.org/bugs/show_bug.cgi?id=9704 [5] http://llvm.org/bugs/show_bug.cgi?id=9707
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:31 UTC