public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Greg Schafer <gschafer@zip.com.au>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Joe Buck <jbuck@synopsys.com>, Paolo Carlini <pcarlini@unitus.it>,
	gcc@gcc.gnu.org
Subject: Re: GCC-3.2.2 pre-release (second iteration)
Date: Fri, 31 Jan 2003 02:14:00 -0000	[thread overview]
Message-ID: <20030131012818.GA23579@tigers-lfs.nsw.bigpond.net.au> (raw)
In-Reply-To: <m3u1fq183c.fsf@uniton.integrable-solutions.net>

On Fri, Jan 31, 2003 at 01:22:31AM +0100, Gabriel Dos Reis wrote:
> I'm also seeing those failures with the tarball I uploaded but not 
> on current version of gcc-3_2-branch (which will be the next
> iteration).  
> 
> I looked into the failures and cannot find out which patches could
> have possibly caused those failures.  All failures seem to be
> "syntax error".  I'm inclined to conlude that the environment I used
> to prepare the second iteration (which is at work) might be insane [it
> is the one which started the reduce/reduce conflit thread]. 
> 
> I would like you run the testsuite again but for current CVS
> gcc-3_2-branch and report the results.  Thank you very much for your
> time.  

Gabriel, just a heads up. the tarball does indeed appear to be broken.

Building from the tarball shows the failures whereas building from CVS is
fine for me:-

tarball:
http://gcc.gnu.org/ml/gcc-testresults/2003-01/msg01382.html

CVS:
http://gcc.gnu.org/ml/gcc-testresults/2003-01/msg01325.html


It is probably the bison thing as Paolo suggested. But I thought the
maintainer scripts were supposed to adjust the timestamps so as not to rely
on the bison in the user's environment. Dunno.

Greg

  parent reply	other threads:[~2003-01-31  1:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 17:07 Gabriel Dos_Reis
2003-01-29 22:45 ` Joe Buck
2003-01-30  1:28   ` Paolo Carlini
2003-01-30 23:34   ` Gabriel Dos Reis
2003-01-31  0:59   ` Gabriel Dos Reis
2003-01-31  1:58     ` Bison-1.875, again! (Re: GCC-3.2.2 pre-release (second iteration)) Paolo Carlini
2003-01-31  2:04       ` Gabriel Dos Reis
2003-01-31  1:59     ` GCC-3.2.2 pre-release (second iteration) Joe Buck
2003-01-31  2:14     ` Greg Schafer [this message]
2003-01-31  2:21       ` Gabriel Dos Reis
2003-01-31  2:44         ` Joe Buck
2003-01-31 13:53           ` Joseph S. Myers
2003-01-31 14:43             ` Gabriel Dos Reis
2003-01-31 18:28               ` Joe Buck
2003-01-31 19:13               ` Joseph S. Myers
2003-02-01 16:19                 ` Gabriel Dos Reis
2003-02-03 16:55                   ` Joe Buck
2003-01-31  3:51         ` Greg Schafer
2003-01-31  5:28           ` Gabriel Dos Reis
2003-01-31 13:51         ` Joseph S. Myers
2003-01-31 14:18           ` Paolo Carlini
2003-01-30 15:56 Volker Reichelt
2003-01-30 17:57 ` Gabriel Dos_Reis

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=20030131012818.GA23579@tigers-lfs.nsw.bigpond.net.au \
    --to=gschafer@zip.com.au \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=jbuck@synopsys.com \
    --cc=pcarlini@unitus.it \
    /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).