public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/297: Compilation Error on Cygwin
Date: Wed, 24 May 2006 19:23:00 -0000	[thread overview]
Message-ID: <20060524192301.5622.qmail@sourceware.org> (raw)

The following reply was made to PR insight/297; it has been noted by GNATS.

From: Keith Seitz <keiths@redhat.com>
To: Brett Gordon <brgordon@andrew.cmu.edu>
Cc: insight-gnats@sources.redhat.com
Subject: Re: insight/297: Compilation Error on Cygwin
Date: Wed, 24 May 2006 12:22:00 -0700

 Brett Gordon wrote:
 
 > Sorry...can you be more specific about my "gdb build directory"? Do you mean /insight-6.4/gdb or the gdb directory that already existed on my computer? If you mean the former, then typing the command produced a "file not found". If you mean the latter, can you tell me where this should be located under cygwin?
 > 
 > Thanks for the quick response.
 
 By build directory I mean the directory where the build was conducted. 
 So when you type "make all", the file ./gdb/config.cache will exist. 
 [config.cache is generated by the configure step.]
 
 Try "find . -name config.cache". One of the directories will be a gdb 
 directory in your build tree.
 
 Also, what is the output of "gcc -v"?
 
 Keith


             reply	other threads:[~2006-05-24 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 19:23 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30 23:14 kseitz
2006-05-25 16:03 Brett R. Gordon
2006-05-24 22:23 Brett R. Gordon
2006-05-24 20:13 Keith Seitz
2006-05-24 20:13 Keith Seitz
2006-05-24 19:53 Brett Gordon
2006-05-24 18:29 kseitz
2006-05-24 18:23 brgordon

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=20060524192301.5622.qmail@sourceware.org \
    --to=keiths@redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@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).