Date: Mon, 05 Nov 2012 11:50:02 -0500 From: Howard Goldstein <hg@queue.to> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: wine, gcc and clang with CPUTYPE Message-ID: <5097EE3A.1010904@queue.to> In-Reply-To: <5097EA28.5000801@gmail.com> References: <50879F62.2010004@gmail.com> <5087BD71.9090002@FreeBSD.org> <5087C428.2020908@gmail.com> <5087CA5D.2090407@FreeBSD.org> <5087D069.7040700@gmail.com> <5097DF8E.3020803@queue.to> <5097EA28.5000801@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9FFBBC3149A2F01DC04393A2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/05/2012 11:32, Volodymyr Kostyrko wrote: > 05.11.2012 17:47, Howard Goldstein wrote: >> Volodymyr, your initial email in this thread regarding clang's being >> stuck on native code generation allowed me to wrap up a week of fighti= ng >> with an updated production box with a weird wine issue - thank you! >> >> FWIW I filed a pr on this. You've done much more useful legwork towar= ds >> a solution of the problem and I wanted to point it out to everyone how= >> helpful it was. THANK YOU! >> >> The pr is at http://www.freebsd.org/cgi/query-pr.cgi?pr=3D173337 >=20 > I'm still unsure of my results though. I can't reproduce gcc core dump > anymore. I think it's shadowed by some later fix. >=20 > As for wine my results are not complete: >=20 > 1. Building a world with CPUTYPE=3Dathlon-tbird on a world built with > CPUTYPE=3Dk6 makes wine work. > 2. Building a world with CPUTYPE=3Dathlon-tbird on a world built with > CPUTYPE=3Dathlon-xp makes wine fail. >=20 Like the other poster I'm not familiar with the amd world but if the host you built on didn't support the same instruction set as the target I suspect you see the same weirdness. For what it's worth wine never dumped .core for me (background: i386, world and kern built with clang to CPUTYPE?=3Dpentium4, then world and ports built with old gcc 4.2 also targeting pentium4, then finally kernel build with old gcc 4.2 is what fixed it. For me winedbg never got far enough in starting up the simplest wine (winecfg) to debug which was a great clue but it didn't sink in until I found your post. I failed to try building wine with symbols so I didn't have a meaningful gdb session. In my eyes you are "da man" as it was a terrible week getting the box back into use until I encountered your list post. Save my email if you're ever in southwest Florida, US because I owe you a couple of brewskis or whatever you prefer. The box is now on its way back to the law office. --------------enig9FFBBC3149A2F01DC04393A2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQl+46dYVFuiUUgywRAvMMAKCFzavWLyvcQa+VPk/KawwNgwekyQCeIO3z md9K3mAx5MHYQsGUXQNnqic= =CJuG -----END PGP SIGNATURE----- --------------enig9FFBBC3149A2F01DC04393A2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5097EE3A.1010904>