Date: Sun, 20 Jan 2019 20:28:06 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 231010] emulators/wine: Segmentation fault when built on 12.0-CURRENT/ALPHA Message-ID: <bug-231010-29464-dBS6Ux1B1L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231010-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-231010-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231010 Gerald Pfeifer <gerald@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress CC| |dbn@FreeBSD.org --- Comment #11 from Gerald Pfeifer <gerald@FreeBSD.org> --- (In reply to Theron Tarigo from comment #9) > Wine was previously working (partially) with LLVM toolchain, but seeing > as how a change there can break it entirely, it might also be true that > the toolchain is the cause of some of the lesser and otherwise inexplicable > failures of WINE that are particular to FreeBSD. Indeed. It's yet another factor/difference that introduces risk in a very complex and hard to duplicate/assess situation. (In reply to Alex S from comment #10) > No, winegcc is just a wrapper. Yes, but GCC appears to be the compiler used by (nearly) all Wine developers and the one used to the commercial Crossover products. So, here is what I'll do: I'll add an option to this port such that the user can choose whether to use GCC or not (in which case it'll be the system compiler). And I'll make the use of GCC the default. That is the conservative option for non-expert users, while giving an option to those who want to avoid GCC - plus an easy way to play with the two compiler choices. (Adding @dbn, who made the original suggestion to go for clang where available back a few years ago, and since he's been more than just helping with things around Wine on FreeBSD over the years.) -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231010-29464-dBS6Ux1B1L>