From: marco@sitek.it
To: insight@sources.redhat.com
Subject: Re: Insight 5.2.1 compiled on Cygwin GCC v3.2
Date: Wed, 13 Nov 2002 05:48:00 -0000 [thread overview]
Message-ID: <OFAF289EDC.D924B237-ONC1256C70.004B8ECA-C1256C70.004BC61E@exorint.net> (raw)
>> 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.
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?
Thanks in advance.
Marco
-------------------------------------------------
(cut....)
/usr/include/w32api/winsock2.h:95:2: warning: #warning "fd_set and
associated macros have been defined in sys/types. This may cause
runtime problems with W32 sockets"
/src/gdb/insight-5.2.1/tcl/win/tclWin32Dll.c: In function `DllMain':
/src/gdb/insight-5.2.1/tcl/win/tclWin32Dll.c:193: warning: unused variable
`os'
/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
make[2]: *** [tclWin32Dll.o] Error 1
make[2]: Leaving directory `/build/insight/tcl/win'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/insight/tcl'
make: *** [all-tcl] Error 2
next reply other threads:[~2002-11-13 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 5:48 marco [this message]
2002-11-13 8:41 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 8:54 marco
2002-11-13 9:03 ` Keith Seitz
2002-11-04 7:56 Alexander Stepanov
2002-11-04 8:10 ` Duane Ellis
2002-11-05 10:16 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFAF289EDC.D924B237-ONC1256C70.004B8ECA-C1256C70.004BC61E@exorint.net \
--to=marco@sitek.it \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).