From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15549 invoked by alias); 13 Nov 2002 16:54:11 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 15270 invoked from network); 13 Nov 2002 16:54:10 -0000 Received: from unknown (HELO sitek.exorint.net) (194.185.141.190) by sources.redhat.com with SMTP; 13 Nov 2002 16:54:10 -0000 To: Keith Seitz Cc: insight@sources.redhat.com Subject: Re: Insight 5.2.1 compiled on Cygwin GCC v3.2 MIME-Version: 1.0 Message-ID: From: marco@sitek.it Date: Wed, 13 Nov 2002 08:54:00 -0000 Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2002-q4/txt/msg00100.txt.bz2 Thanks for your kind reply. BTW, You wrote: >>Can Insight 5.2.1 be compiled on Cygwin GCC v3.2 20020818 pre? >I don't recall what I used last, but insight is just a c application. >There's no reason why almost any compiler available for years couldn't >build it. I can compile (and being using for several months with zero problems) insight 5.2.1 with Cygwin/GCC2.95.3. This problems raises only when trying to compile insight 5.2.1with Cygwin/GCC3.2 Thought you could be interested in it... Marco Keith Seitz 11/13/2002 06:44 PM To: insight@sources.redhat.com cc: marco@sitek.it Subject: Re: Insight 5.2.1 compiled on Cygwin GCC v3.2 On Wed, 13 Nov 2002 marco@sitek.it wrote: > Hello. I am also trying to build insight5.2.1 with > Cygwin1.3.14-1/GCC 3.2 (20020818 pre) and get it failing here... > Any idea? Marco, I would not recommend using 5.2.1 with cygwin. It has issues. See http://sources.redhat.com/insight/cygwin.html. ---- List, Second, I am amazed that I keep getting requests for how to fix this simple problem. Insight is a debugger, so I presume that people downloading it are at least vaguely familiar with programming. Why can people not figure out how to fix the simplest of errors? > /src/gdb/insight-5.2.1/tcl/win/tclWin32Dll.c: In function > `TclWinSetInterfaces': > /src/gdb/insight-5.2.1/tcl/win/tclWin32Dll.c:121: static symbol > `tclWinTCharEncoding' is marked dllexport The error message says it all: In TclWinSetInterfaces, the static symbol "tclWinTCharEncoding" is marked dllexport. Get it? The STATIC symbol is exported... If people still don't get it, cgf has committed a patch to fix this. Search the mailing list or take a peek at tcl in CVS to find the patch. Keith