public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16043] New: gcc version not reported to gcc-testresults
Date: Fri, 18 Jun 2004 00:42:00 -0000	[thread overview]
Message-ID: <20040618004234.16043.billingd@gcc.gnu.org> (raw)

The test_summary script is not reporting the GCC version in my mail to gcc-
testresults.  I think I have tracked down the problem and am testing a fix.

The problem appears to be in gcc/testsuite/gcc.exp (and the other tool.exp 
routines).  The regexp to print and report the version is

   regexp "version\[^\n\r\]*" $output version

However "/usr/local/obj/gcc/gcc/xgcc -B/usr/local/obj/gcc/gcc/ -v" gives

Reading specs from /usr/local/obj/gcc/gcc/specs
Configured with: /usr/local/src/gcc/configure --prefix=/usr/local/gcc-3_5 --
enable-threads=posix --enable-languages=c,c++,f95,java,objc --disable-libgcj --
enable-sjlj-exceptions --with-system-zlib --enable-nls --disable-libmudflap --
disable-libstdcxx-pch --enable-version-specific-runtime-libs --without-
included-gettext --disable-shared
Thread model: posix
gcc version 3.5.0 20040617 (experimental)


and the regexp finds --enable-version-specific-runtime-libs flag.

-- 
           Summary: gcc version not reported to gcc-testresults
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: billingd at gcc dot gnu dot org
        ReportedBy: billingd at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-cygwin
  GCC host triplet: i686-pc-cygwin
GCC target triplet: i686-pc-cygwin


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16043


             reply	other threads:[~2004-06-18  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  0:42 billingd at gcc dot gnu dot org [this message]
2004-06-18  1:47 ` [Bug other/16043] " pinskia at gcc dot gnu dot org
2004-06-18 23:48 ` cvs-commit at gcc dot gnu dot org
2004-06-18 23:57 ` billingd at gcc dot gnu dot org
2004-06-19  1:02 ` pinskia at gcc dot gnu dot org
2004-08-29 18:44 ` [Bug other/16043] [3.4 only] " mmitchel at gcc dot gnu dot org
2004-11-01  0:47 ` [Bug other/16043] [3.4 only] gcc version not reported with "enable-version-specific-runtime-libs" " mmitchel at gcc dot gnu dot org
2005-01-24  5:19 ` billingd at gcc dot gnu dot org

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=20040618004234.16043.billingd@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).