From: Keith Seitz <keiths@redhat.com>
To: insight@sourceware.org
Subject: Re: Any cygwin savvy developers out there? Cygwin build problem
Date: Wed, 24 May 2006 20:04:00 -0000 [thread overview]
Message-ID: <4474BC43.207@redhat.com> (raw)
In-Reply-To: <4474BACD.B9558FE2@dessent.net>
Brian Dessent wrote:
> Keith Seitz wrote:
>
>> I think there are a few of you out there. Anyone know what the following
>> errors might arise from?
>> [...]
>> make[3]: Leaving directory `/home/brgordon/insight-6.4/tcl/win'
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory `/home/brgordon/insight-6.4/tcl'
>> make[1]: *** [all-tcl] Error 2
>> make[1]: Leaving directory `/home/brgordon/insight-6.4'
>> make: *** [all] Error 2
>
> It looks like the reporter is trying to build a release. This problem
> was fixed in CVS on
> <http://sourceware.org/ml/insight/2006-q1/msg00045.html> however it had
> been mentioned in the mailing list for quite some time beforehand:
> <http://sourceware.org/ml/insight/2005-q3/msg00021.html>. So I think
> the solution is just to tell the user to use a more recent version.
That would explain it. Sadly, now that you mention it, it does ring a
bell... :-(
Thanks!
Keith
prev parent reply other threads:[~2006-05-24 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 18:55 Keith Seitz
2006-05-24 19:59 ` Brian Dessent
2006-05-24 20:04 ` Keith Seitz [this message]
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=4474BC43.207@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
/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).