From: Stephen & Linda Smith <ischis2@cox.net>
To: Keith Seitz <keiths@redhat.com>
Cc: Marc Schafer <mschafer@avidyne.com>,
"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: problem building 6.1 for powerpc on cygwin
Date: Thu, 03 Jun 2004 02:00:00 -0000 [thread overview]
Message-ID: <40BE863A.30303@cox.net> (raw)
In-Reply-To: <1086197005.2747.19.camel@lindt.uglyboxes.com>
I built insight successfully from CVS (mainline as opposed to the
branch) targeting powerpc-motorola-elf about a week ago. I was getting
the errors refered to earlier without Keith's patch
http://sources.redhat.com/ml/insight/2004-q2/msg00032.html .When I applied patch that everything worked.
Be sure you have a reasonably up to date tcltk on your cygwin installation.
sps
Keith Seitz wrote:
>On Wed, 2004-06-02 at 10:12, Marc Schafer wrote:
>
>
>>configure doesn't seem to do much. i guess most of it happens when
>>you do a make?
>>
>>
>
>Grr.. That's right. Can you send me the output of "make all-tk"?
>
>
>
>>I looked here for a snapshot to try:
>>ftp://sources.redhat.com/pub/gdb/snapshots/current/
>>
>>The newest insight snapshot seems to be from April. Am I looking the
>>wrong place?
>>
>>
>
>Hmm. That's the right place. I guess the gdb folk have decided to drop
>all "support" for insight until the official FSF donation is complete.
>[Of course, that would make two of us!] Or it could just be that the
>snapshot process got broken.
>
>Anyway, if worse comes to worse and you can't or don't want to check out
>HEAD, I can get you a tarball.
>
>Keith
>
>
>
>
>
>
next prev parent reply other threads:[~2004-06-03 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 15:31 Marc Schafer
2004-06-02 16:30 ` Keith Seitz
[not found] ` <04a101c448c4$bd2c6650$0b01a8c0@maestrale>
2004-06-02 17:21 ` Keith Seitz
2004-06-03 2:00 ` Stephen & Linda Smith [this message]
[not found] ` <001a01c44916$481e7400$6501a8c0@canoli>
2004-06-03 3:23 ` Stephen & Linda Smith
2004-06-02 17:21 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=40BE863A.30303@cox.net \
--to=ischis2@cox.net \
--cc=insight@sources.redhat.com \
--cc=keiths@redhat.com \
--cc=mschafer@avidyne.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).