From: Joel Brobecker <brobecker@gnat.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Problems with dejagnu and c++ tests...
Date: Wed, 04 Feb 2004 13:20:00 -0000 [thread overview]
Message-ID: <20040204131959.GZ18961@gnat.com> (raw)
In-Reply-To: <20040204125005.53EB84B364@berman.michael-chastain.com>
> Rats, this is my clever code in get_compiler_info blowing up.
Humph! I was certain that I tried backing out your last gdb.exp
patch, and that it didn't help. I just tried again, and now it
seems to be working better...
Blush... I am glad you were able to zero in the source of the
problem before anybody spent any thought on this.
> What was the previous behavior when you did not have a C++ compiler?
Here is the output I get after I backout your patch and all the other
changes in gdb.exp after yours:
<<
gdb compile failed, gcc: ./lib/compiler.cc: C++ compiler not installed on this system
ERROR: Couldn't make /usr/prague.a/brobecke/next_pb/gdb-public/gdb/testsuite/gdb.cp/ambiguous.ci file
>>
--
Joel
next prev parent reply other threads:[~2004-02-04 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 12:50 Michael Elizabeth Chastain
2004-02-04 13:20 ` Joel Brobecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 23:50 Michael Elizabeth Chastain
2004-02-04 23:55 ` Daniel Jacobowitz
2004-02-04 23:03 Michael Elizabeth Chastain
2004-02-04 23:13 ` Daniel Jacobowitz
2004-02-04 22:31 Michael Elizabeth Chastain
2004-02-04 22:49 ` Andrew Cagney
2004-02-04 14:01 Michael Elizabeth Chastain
2004-02-04 15:41 ` Andrew Cagney
2004-02-04 11:58 Joel Brobecker
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=20040204131959.GZ18961@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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