public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bernhard Simon <simon@zid.tuwien.ac.at> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/2622: gcc-2.95.3 fails to build on ULTRIX V4.5 Date: Tue, 26 Nov 2002 07:56:00 -0000 [thread overview] Message-ID: <20021119162603.12068.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/2622; it has been noted by GNATS. From: Bernhard Simon <simon@zid.tuwien.ac.at> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, simon@zid.tuwien.ac.at, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/2622: gcc-2.95.3 fails to build on ULTRIX V4.5 Date: Tue, 19 Nov 2002 17:22:08 +0100 (MET) > Synopsis: gcc-2.95.3 fails to build on ULTRIX V4.5 > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Tue Nov 19 07:59:22 2002 > State-Changed-Why: > This is a rather old bootstrap error. Can you say whether this > still happens with newer versions of gcc? > > Thanks, W. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2622 > AFAIK mips-dec-ultrix is not supported in newer versions of gcc any more. So I did not try it, but was finally able to build gcc-2.95.3 with the following changes (and with ANSI C, i.e. CC="cc -std1"): gcc/configure (line 6078, 6080, 6082, 6159: ... test -x ...) gcc/cp/Make-lang.in (line 169: ... [ -x ...) gcc/fixinc/fixincl.sh (line 77, 100, 102: ... test -x ... [ ! -x ...) (void *) cmp_combine_givs_stats gcc/loop.c (line 7044, 7285, 7459) texinfo/makeinfo/makeinfo.c (line 8225) _IO_pos_t -> _IO_off_t libio/genops.c (line 470, 473, 554, 885) libio/fileops.c (line 422, 590) libio/ioseekoff.c (line 28) libio/ioseekpos.c (line 28, 31) libio/strops.c (line 208) -bernhard
next reply other threads:[~2002-11-19 16:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-26 7:56 Bernhard Simon [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-26 9:46 bangerth 2002-11-26 2:56 bangerth
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=20021119162603.12068.qmail@sources.redhat.com \ --to=simon@zid.tuwien.ac.at \ --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: linkBe 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).