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 20:13:00 -0000	[thread overview]
Message-ID: <20060524201302.6484.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 13:02:29 -0700

 Brett Gordon wrote:
 > From the build directory, I typed "find . -name config.cache". The output:
 > 
 > ---------------------------------
 > $ find . -name config.cache
 > ./bfd/config.cache
 > ./config.cache
 > ./etc/config.cache
 > ./libiberty/config.cache
 > ./opcodes/config.cache
 > ./tcl/config.cache
 > -----------------------------
 
 Hmm. No gdb/config.cache... Odd.
 
 > 
 > I have a 'gdb' directory, but not sure why there is no config.cache file. The output from "gcc -v" is
 > 
 
 What is in the gdb directory, then? Can you redirect all of the I/O for 
 the build into a log file and attach the log file to the bug report?
 
 $ /path/to/configure > build.out 2>&1
 $ make all-gdb >> build.out 2>&1
 
 Attach build.out
 
 > -----------------------------------
 > Reading specs from /usr/lib/gcc/i686-pc-cygwin/3.4.4/specs
 > Configured with: /gcc/gcc-3.4.4/gcc-3.4.4-1/configure --verbose --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --libex
 > ecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-languages=c,ada,c++,d,f77,java,objc --enable-nls --without-include
 > d-gettext --enable-version-specific-runtime-libs --without-x --enable-libgcj --disable-java-awt --with-system-zlib --enable-interpreter --di
 > sable-libgcj-debug --enable-threads=posix --enable-java-gc=boehm --disable-win32-registry --enable-sjlj-exceptions --enable-hash-synchroniza
 > tion --enable-libstdcxx-debug : (reconfigured)
 > 
 > Thread model: posix
 > 
 > gcc version 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)
 > ------------------------------------
 
 That's the same compiler I am using.
 
 Keith


             reply	other threads:[~2006-05-24 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 20:13 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 19:53 Brett Gordon
2006-05-24 19:23 Keith Seitz
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=20060524201302.6484.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).