public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ro@gcc.gnu.org To: ro@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libf2c/4826: Build error for 3.0.2 on Tru64 Unix 5.1A Date: Sun, 18 Nov 2001 20:16:00 -0000 [thread overview] Message-ID: <20011122200600.3799.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libf2c/4826; it has been noted by GNATS. From: ro@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, harry@atmos.washington.edu, nobody@gcc.gnu.org, ro@gcc.gnu.org Cc: Subject: Re: libf2c/4826: Build error for 3.0.2 on Tru64 Unix 5.1A Date: 22 Nov 2001 19:58:56 -0000 Synopsis: Build error for 3.0.2 on Tru64 Unix 5.1A Responsible-Changed-From-To: unassigned->ro Responsible-Changed-By: ro Responsible-Changed-When: Thu Nov 22 11:58:56 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: open->analyzed State-Changed-By: ro State-Changed-When: Thu Nov 22 11:58:56 2001 State-Changed-Why: Could you please try the attached patch? Compaq changed stdio.h in Tru64 UNIX V5.1A to use __VA_LIST__ instead of va_list/__va_list in various prototypes, and fixincludes doesn't change this to __gnuc_va_list without this patch. Verified by manually running the patched fixincludes on a copy of the V5.1A stdio.h, but I cannot bootstrap or run the testsuite myself due to lack of access to a V5.1A system. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4826&database=gcc
next reply other threads:[~2001-11-22 20:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-18 20:16 ro [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-06 13:56 ro 2001-12-06 13:54 ro 2001-11-18 20:11 ro
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=20011122200600.3799.qmail@sourceware.cygnus.com \ --to=ro@gcc.gnu.org \ --cc=gcc-prs@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).