Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
From: "Dave Korn" <dk@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: Tcl doesn't build out of src repository on cygwin
Date: Wed, 13 Oct 2004 15:01:45 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20041013135259.GG6702@cygbert.vinschen.de>
Message-ID: <NUTMEG1zRL25AExgTVx00000453@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 13 Oct 2004 14:01:45.0470 (UTC) FILETIME=[2CB1A1E0:01C4B12D]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Corinna Vinschen
> Sent: 13 October 2004 14:53

> On Oct 13 13:15, Dave Korn wrote:
> > 
> > 
> >   Should it?  I see loads of error messages caused by a bad 
> table of static
> > initialisers in src/tcl/win/tclWin32Dll.c.
> 
> It happens because DLLIMPORT is used a lot in w32api which is only
> conditionalized with __INSIDE_CYGWIN__.  That's solved in w32api in
> CVS or in recent snapshots.  Or (but that's ugly and not actually
> recommended, use at your own risk) use #define __INSIDE_CYGWIN__
> at the beginning of the affected files (tclWin32Dll.c and tkWinX.c
> AFAIK)

  Or use CFLAGS='-D__INSIDE_CYGWIN__ -g -O2' on the command line,
presumably?

  Thanks Corinna.  I wasn't sure if there was a better list to bring this up
on, since Tcl isn't a sourceware project; then again, since the build
failure was cygwin-specific, I guess it was on-topic anyway.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

