From: "Matthias Andree" <matthias.andree@gmx.de>
To: insight@sources.redhat.com
Subject: Re: Build failure on Cygwin
Date: Fri, 15 Jan 2010 16:53:00 -0000 [thread overview]
Message-ID: <op.u6k2ijrr1e62zd@balu.cs.uni-paderborn.de> (raw)
Sorry for breaking the threading, I've only just subscribed because I am
facing the same issue as Jon (reported on Jan 2).
This seems to be an imported issue as we get failures from including both
winsock2.h or thereabouts (unconditionally) and sys/select.h.
I don't know why/how exactly sys/select.h gets pulled in, I haven't seen
obvious offending files under tcl/ - so it might be a change and/or bug in
Cygwin headers, too.
Is there a particular reason why Insight compiles its own Tcl, rather than
grab the system default if there is one? Or is there a way to talk Insight
into using a system Tcl?
Cygwin has a Tcl/Tk package after all, why not use that?
TIA
--
Matthias Andree
next reply other threads:[~2010-01-15 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 16:53 Matthias Andree [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-02 20:49 Jon Beniston
2010-01-04 20:18 ` Keith Seitz
2010-01-11 18:20 ` Jon Beniston
2011-04-28 16:39 ` mizo_hazem_2
2011-04-28 16:53 ` Christopher Faylor
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=op.u6k2ijrr1e62zd@balu.cs.uni-paderborn.de \
--to=matthias.andree@gmx.de \
--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).