From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 60023139694 for ; Thu, 18 May 2017 03:47:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C144221C08A; Thu, 18 May 2017 03:47:00 +0000 (UTC) Received: from tsukuyomi.43-1.org (tsukuyomi.43-1.org [188.40.248.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 73BAD21C081 for ; Thu, 18 May 2017 03:47:00 +0000 (UTC) From: Matthias Maier To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] mingw-w64 crossdev prefix? In-Reply-To: <20170517222548.d75vcbnrid5bn7qb@tha-monstah.mydomain> (Marty Plummer's message of "Wed, 17 May 2017 17:25:48 -0500") References: <20170517222548.d75vcbnrid5bn7qb@tha-monstah.mydomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Date: Wed, 17 May 2017 22:46:50 -0500 Message-ID: <87wp9e25ed.fsf@kestrel.kyomu.43-1.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: 29624d79-0f7a-4308-8ace-6d7bc324df63 X-Archives-Hash: 08aa95733166e5d0a8218d4776ee6914 --=-=-= Content-Type: text/plain Hi there, On Wed, May 17, 2017, at 17:25 CDT, Marty Plummer wrote: > Greetings, > > So, I'm a relatively new gentoo user (as of 2016-12) coming from arch, > and one thing I've noticed is the relative difficulty of setting up a > mingw-w64 cross-compile toolchain and libraries. > > I'm considering the idea of setting up a sort of prefix specifically > with the intent of being used on a 'normal' gentoo system with the sole > purpose of creating 'normal' windows binaries; does anyone have > suggestions/objections about the idea? > > As it currently stands I have to use an archlinux chroot to do my > cross-compiling, and I'd really enjoy to be able to do this sort of > thing without depending on an auxiliary distro. You can find some information on the wiki [1] (warning: I might be a bit outdated). But anyway, just check it for you (I haven't set up a cross compilation toolchain for windows for the last ~7 years): From a plain amd64 stage-3 setting up a mingw-264 environment via: # emerge crossdev # crossdev [...] -t x86_64-w64-mingw32 still works with a minor complication [2]. Please verify that this works and open a bug report for the libsanitizer issue mentioning the workaround [2,3]. After that you end up with a cross-compiler toolchain x86_64-w64-mingw32-* and necessary runtime somewhere in /usr/x86_64-w64-mingw32. You can also use $ x86_64-w64-mingw32-emerge to cross compile libraries/packages for mingw. Keep in mind that a cross compilation toolchain is a bit of a rocky journey. You might have to pin certain versions of libraries/programs, and or manually patch some stuff. Best, Matthias [1] https://wiki.gentoo.org/wiki/Mingw [2] I had to manually disable libsanitizer for gcc-6.3.0. Just set EXTRA_ECONF="--disable-libsanitizer" via env/package.env for the cross-x86_64-w64-mingw32/gcc package. [3] https://bugs.gentoo.org/buglist.cgi?quicksearch=mingw&list_id=3536150 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIzBAEBCgAdFiEE6t/5JjgpnbiQKMUluE7NiUruef8FAlkdGSoACgkQuE7NiUru ef+lqRAAxRhzpY6DL+zb58/NteOjtTZ1Jl9wGyRdh0z0xhvKUYJ4Idjk8DsFHE3V Vu/gRMZsAOtz5+9j/bC81FJ30zbtyT7aY825pHU5ahKuxj3eFASIWknPLsHD9Esl 8RRA0RWbnDemT5XVZmlZbq79S7k94aywIVawdkVfOIbNbdX4JzhddiQM23PICelp f8jxQ6P/xrmOvk+ocdElEK09Tdvl1lNhFBzDEXGzJ2Ik4bIdMwlmyftjusYyY3lP DDsyB4BXyJ9Q4C85IiTr19lHSN1Bbi94ns7OFqNVuHV8SmhWEwgCVaOGj/GAvi0o GL1MZYPEDX0iYcHpfeq+xsT8wk2vp/wEPEnPysRXQm4HUIGSuhCd+7SEksnvR9xR XNzHAs5utKCFPAQUfAifdlEpGmylcJ7ySyN3UdhDpEXBVbEoKYkVDKDDLQnoRchH r+YPUKMsiC4WuHC723iLP6q/3VYyKd1igwQYBcuLeHC3f1hgs2SQ14zSeX8kEOdN D/IQonMV5xQYzavbjh5zGNbHJTOOjBm51JoNieTK8nzxmSgh+IYrdXsUutC4WIZM G1edMeB63fnseXF/MT3wiMEX5LLrcEDcqzjQXK2wtD/yB18RfM/qkZdFEGRU5ZJn P/jSZAN9HsE81vlP3vE5bSJinSmXP/8jAHdqOkA1jDDyeSkQm8Q= =J4Ue -----END PGP SIGNATURE----- --=-=-=--