public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Paul C. Leopardi" <leopardi@bigpond.net.au>
To: gcc-help@gcc.gnu.org
Subject: gcc testsuite definitely uses the wrong g++: why?
Date: Sat, 08 May 2004 00:09:00 -0000	[thread overview]
Message-ID: <200405081009.00282.leopardi@bigpond.net.au> (raw)
In-Reply-To: <1083940866.4533.ezmlm@gcc.gnu.org>

Hi all,
Sorry to press this, but I'm still trying to figure out why "make 
check-gcc-c++" uses the wrong g++ even though "make check-c++" uses the right 
g++. Perhaps I should just submit a bug report?
Thanks

On Saturday 08 May 2004 00:41, gcc-help-digest-help@gcc.gnu.org wrote:
> Re: gcc testsuite apparently can't find g++
>
> From:
> "Paul C. Leopardi" <leopardi@bigpond.net.au>
>
>
> To:
> gcc-help@gcc.gnu.org
>
>
> Date:
> 2004-05-07 01:11
>
> Rob,
> I have run the test again with RUNTESTFLAGS="-v -v" and I get lots of
> output now. Unfortunately I don't know what the output should look like, so
> I can't see what the problem is. I ran
> make check-c++ RUNTESTFLAGS="-v -v" > make-check-c++.1.out 2>&1
> which said, eg.:
> Invoking the compiler
> as /home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/g++ -shared-libgcc
> -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -nostdinc++ ...
> and ran
> make check-gcc-c++ RUNTESTFLAGS="-v -v" > make-check-gcc-c++.1.out 2>&1
> which said, eg.:
> Invoking the compiler as
> g++
> /home/leopardi/Documents/src/gcc/gcc-3.4.0/gcc/testsuite/g++.dg/bprob/g++-b
>prob-1.C   -nostdinc++
>
> I have attached a single file containing the first part of the output of
> each. Is this enough to tell what's going on? What am I looking for?
> Best regards

       reply	other threads:[~2004-05-08  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1083940866.4533.ezmlm@gcc.gnu.org>
2004-05-08  0:09 ` Paul C. Leopardi [this message]
2004-05-09 17:18   ` llewelly

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=200405081009.00282.leopardi@bigpond.net.au \
    --to=leopardi@bigpond.net.au \
    --cc=gcc-help@gcc.gnu.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).