From: Keith Seitz <keiths@redhat.com>
To: Spen <spen@spen-soft.co.uk>
Cc: p.rockett@sheffield.ac.uk, "'insight'" <insight@sourceware.org>
Subject: Re: FW: Can't build Insight with Cygwin
Date: Fri, 23 Dec 2005 23:19:00 -0000 [thread overview]
Message-ID: <43AC704E.1060008@redhat.com> (raw)
In-Reply-To: <200512231852.jBNIq9cM007525@mx1.redhat.com>
Spen wrote:
> I have built 6.4 both from the tar.gz release and cvs head
I updated my cygwin box to latest:
CYGWIN_NT-5.0 cocoa 1.5.18(0.132/4/2) 2005-07-02 20:30 i686 unknown
unknown Cygwin
and gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125).
I saw the DLL problem which Dave Korn's patch fixed. This fixed
everything. [Of course, gdb (not insight) segfaults on me in about three
seconds flag -- try debugging gdb.exe on gdb.exe. Break in main. Try
stepping into the "return gdb_main (&args);" part. It crashes in
handle_inferior_event.]
So, yes, there must be some sort of weird build dependency that neither
Spen nor I are seeing.
Spen, are you using Win2k, WinNT, or WinXP? Like I mentioned before, I
only have Win2k.
Keith
next parent reply other threads:[~2005-12-23 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200512231852.jBNIq9cM007525@mx1.redhat.com>
2005-12-23 23:19 ` Keith Seitz [this message]
2005-12-24 0:55 ` Peter Rockett
2005-12-24 18:00 ` Spen
[not found] <cmu-lmtpd-20522-1135363936-1@impala>
2005-12-23 22:58 ` Peter Rockett
[not found] <cmu-lmtpd-21756-1135354673-4@impala>
2005-12-23 18:52 ` Peter Rockett
2005-12-23 21:41 ` Peter Rockett
2005-12-24 14:00 ` Keith Seitz
2005-12-23 21:47 ` Spen
[not found] <200512231618.jBNGI4BD085002@mail.cso.atmel.com>
2005-12-23 18:10 ` Eric Weddington
2005-12-23 16:17 wilfried.fauvel
2005-12-23 16:21 ` FW: " Peter Rockett
2005-12-23 16:24 ` Spen
-- strict thread matches above, loose matches on Subject: below --
2005-12-23 16:09 Peter Rockett
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=43AC704E.1060008@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=p.rockett@sheffield.ac.uk \
--cc=spen@spen-soft.co.uk \
/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).