From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: Re: guix is the guildhall that we always wanted! Date: Sun, 19 Mar 2017 18:22:17 +0200 Message-ID: <83r31tw81y.fsf@gnu.org> References: <87zigl3wph.fsf@pobox.com> <87a88kf8cu.fsf@gnu.org> <83d1dgyr5e.fsf@gnu.org> <87bmsy65q3.fsf@gnu.org> <83bmsyy8t6.fsf@gnu.org> <8737e945ul.fsf@gnu.org> Reply-To: Eli Zaretskii Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-reply-to: <8737e945ul.fsf@gnu.org> (ludo@gnu.org) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sender: "guile-user" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: wingo@pobox.com, guix-devel@gnu.org, guile-user@gnu.org List-Id: guix-devel.gnu.org > From: ludo@gnu.org (Ludovic Courtès) > Cc: wingo@pobox.com, guix-devel@gnu.org, guile-user@gnu.org > Date: Sun, 19 Mar 2017 16:57:22 +0100 > > > I'm saying that when cross-compiling, it's easy to produce binaries > > that are unusable on Windows because Guile is not run natively during > > the build, and so problems inherent to the Windows port are not > > revealed during the build. > > Right; that would be a bug in Guile’s build system. Is pthread support > detection broken when cross-compiling to MinGW? Not sure what you are asking here. I never cross-built Guile, I always build the MinGW port natively. And pthreads detection is not broken, the build process correctly detects that I have pthreads installed. But if I want to produce a working Guile (or even get the build to run to completion, since that involves running Guile to compile Scheme files), I need to disable threads.