[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] fix static compilation in cygwin

From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] fix static compilation in cygwin
Date: Mon, 21 Jul 2014 21:37:07 +0200
User-agent: Mutt/

On Sun, Jul 20, 2014 at 01:47:03PM +0200, Felix Winkelmann wrote:
> From: Michele La Monaca <address@hidden>
> Subject: [Chicken-hackers] [PATCH] fix static compilation in cygwin
> Date: Sun, 13 Jul 2014 14:57:17 +0200
> > Hi,
> > 
> > I think static compilation is broken in cygwin because csc
> > inexplicably (to me at least) looks for cygchicken-0.a instead of
> > libchicken.a.
> Has anybody looked into this, yet? Seems right to me. I don't have a
> cygwin setup, so can someone give me a hand and try Michele's patch?

I've tested the patch, and it indeed seems to fix this particular
situation.  Somehow I thought this would break dynamically linked
builds, as there's no libchicken.dll, only cygchicken-0.dll.  However,
*somehow* dynamic binaries are still linked against cygchicken-0.dll
even with this patch.

I've never understood this cygchicken-0.dll business.  It's still being
built, and the core binaries are still linked against it.  So I'm unsure
whether this patch is the Right Fix; I always assumed there was a reason
we had cygchicken-0.dll, and programs should be linked against it?

Anyway, I don't understand a thing about this, but it seems to fix the
bug, so why not?  I've attached a signed-off copy with a NEWS entry.


Attachment: 0001-fix-static-compilation-in-cygwin.patch
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]