From: John David Anglin <dave.anglin@bell.net>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] 32-bit PA-RISC with HP-UX: remove deprecated ports
Date: Fri, 26 Aug 2022 15:09:13 -0400 [thread overview]
Message-ID: <88267e96-77d2-415a-daa3-8b009139d119@bell.net> (raw)
Message-ID: <20220826190913.vACqiXBgumARjMcyc1KXNK3RZ-wEmvY09zaQhMvG0JE@z> (raw)
In-Reply-To: <f977bee1-f8d7-b523-1b4d-75bd4d6dbb73@suse.cz>
On 2022-08-26 3:15 a.m., Martin Liška wrote:
> fixincludes/ChangeLog:
>
> * configure: Regenerate.
> * inclhack.def: Remove patterns for deprecated ports.
> * fixincl.x: Regenerate.
There are problems with the fixincludes changes. These break build on hppa64-hpux11.
configure:4015: checking whether we are cross compiling
configure:4023: /home/dave/gnu/gcc/objdir64/./gcc/xgcc -B/home/dave/gnu/gcc/objd
ir64/./gcc/ -B/opt/gnu64/gcc/gcc-12/hppa64-hp-hpux11.11/bin/ -B/opt/gnu64/gcc/gc
c-12/hppa64-hp-hpux11.11/lib/ -isystem /opt/gnu64/gcc/gcc-12/hppa64-hp-hpux11.11
/include -isystem /opt/gnu64/gcc/gcc-12/hppa64-hp-hpux11.11/sys-include -fno-c
hecking -o conftest -g -O2 conftest.c >&5
In file included from /home/dave/gnu/gcc/objdir64/gcc/include-fixed/stdio.h:21,
from conftest.c:11:
/home/dave/gnu/gcc/objdir64/gcc/include-fixed/stdio.h:608:59: error: unknown type name 'va_list'
608 | extern int vsnprintf(char *, __size_t, const char *, __va__list);
| ^~~~~~~~~~
/home/dave/gnu/gcc/objdir64/gcc/include-fixed/stdio.h:116:1: note: 'va_list' is defined in header '<stdarg.h>'; did you forget to '#include
<stdarg.h>'?
115 | # include <sys/_size_t.h>
Some hpux11 specific hacks are removed. Some non system specific hpux hacks are also removed.
One can't trust comments or hacknames to infer applicability.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2022-08-26 19:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 7:15 Martin Liška
2022-08-26 7:20 ` Andreas Schwab
2022-08-26 7:22 ` Martin Liška
2022-08-26 19:09 ` John David Anglin [this message]
2022-08-26 19:09 ` John David Anglin
2022-08-28 16:34 ` John David Anglin
2022-08-28 16:34 ` John David Anglin
2022-08-29 14:06 ` Martin Liška
2022-08-29 14:06 ` Martin Liška
2022-08-30 18:39 ` John David Anglin
2022-08-30 18:39 ` John David Anglin
2022-08-30 19:00 ` John David Anglin
2022-08-30 19:00 ` John David Anglin
2022-08-30 19:51 ` John David Anglin
2022-08-30 19:51 ` John David Anglin
2022-08-31 0:13 ` Jeff Law
2022-08-31 0:32 ` John David Anglin
2022-08-31 7:21 ` [PATCH][V3] " Martin Liška
2022-08-31 15:35 ` Jeff Law
2022-08-31 16:40 ` John David Anglin
2022-08-31 17:24 ` Jeff Law
2022-09-01 13:08 ` John David Anglin
2022-09-01 13:08 ` John David Anglin
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=88267e96-77d2-415a-daa3-8b009139d119@bell.net \
--to=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).