public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeremy Sanders <jss@ast.cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/10169: Bootstrap fails on mainline with Tru64 5.1B
Date: Fri, 16 May 2003 16:46:00 -0000	[thread overview]
Message-ID: <20030516164601.18461.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/10169; it has been noted by GNATS.

From: Jeremy Sanders <jss@ast.cam.ac.uk>
To: Roger Sayle <roger@www.eyesopen.com>
Cc: Dara Hazeghi <dhazeghi@yahoo.com>, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/10169: Bootstrap fails on mainline with Tru64 5.1B
Date: Fri, 16 May 2003 17:40:25 +0100 (BST)

 On Wed, 14 May 2003, Roger Sayle wrote:
 
 >
 > Hi Dara,
 > > it looks like Roger committed a patch to fix this problem. Could either
 > > the submitter or Roger confirm that this is the case? Thanks,
 >
 > The problem is that the PR gives two compilation errors trying to
 > compile mips-tfile.  My patch fixes the first of these, the initializer
 > problems on line 1134.  The compilation still fails on Tru64 5.1B
 > with the "getopt" problem on line 4861.  Unfortunately, I only have
 > access to 5.1 not 5.1B, so I'm unable to reproduce the problem and
 > the obvious "#include <getopt.h>" is reported not to fix it.
 
 Yes - it still fails here. I'm not sure whether it should be a new bug.
 
 stage1/xgcc -Bstage1/ -B/usr/local/alphaev6-dec-osf5.1/bin/ -c   -g -O2
 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
 -Wmissing-prototypes -pedantic -Wno-long-long -Werror -fno-common
 -DHAVE_CONFIG_H    -I. -I. -I../../gcc-cvs/gcc/gcc
 -I../../gcc-cvs/gcc/gcc/. -I../../gcc-cvs/gcc/gcc/config
 -I../../gcc-cvs/gcc/gcc/../include ../../gcc-cvs/gcc/gcc/mips-tfile.c -o
 mips-tfile.o
 ../../gcc-cvs/gcc/gcc/mips-tfile.c: In function `main':
 ../../gcc-cvs/gcc/gcc/mips-tfile.c:4812: warning: implicit declaration of
 function `getopt'
 make[2]: *** [mips-tfile.o] Error 1
 make[2]: Leaving directory `/tmp_mnt/scratch/jss/builds/gcc/gcc'
 make[1]: *** [stage2_build] Error 2
 make[1]: Leaving directory `/tmp_mnt/scratch/jss/builds/gcc/gcc'
 make: *** [bootstrap] Error 2
 
 If anyone is interested in the .i file which fails, get it from
 
 http://www-xray.ast.cam.ac.uk/~jss/data/mips-tfile.i.gz
 
 Jeremy
 
 -- 
 Jeremy Sanders <jss@ast.cam.ac.uk>   http://www-xray.ast.cam.ac.uk/~jss/
 X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
 Public Key Server PGP Key ID: E1AAE053


             reply	other threads:[~2003-05-16 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 16:46 Jeremy Sanders [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-15 17:16 Jeremy Sanders
2003-05-14 18:36 Roger Sayle
2003-05-14 18:16 Dara Hazeghi
2003-03-20 17:56 jss

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=20030516164601.18461.qmail@sources.redhat.com \
    --to=jss@ast.cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).