From: Joe Simmons-Talbott <josimmon@redhat.com>
To: libc-help@sourceware.org
Subject: build-many-glibcs.py build failure for i686-gnu
Date: Thu, 22 Jun 2023 15:59:52 -0400 [thread overview]
Message-ID: <20230622195952.GL6392@oak> (raw)
Hi,
I'm investigating a build failure using build-many-glibcs.py for
i686-gnu. There seems to be a mismatch between the declaration of
_hurdsig_fault_catch_exception_raise in hurd/hurdfault.c and the
generated header hurd/faultexc_server.h. I can't figure out how the
header is being generated.
The error I'm seeing is:
hurdfault.c:39:1: error: conflicting types for <E2><80><98>_hurdsig_fault_catch_exception_raise<E2><80><99>; have <E2>
<80><98>kern_return_t(mach_port_t, thread_t, task_t, integer_t, integer_t, long_integer_t)<E2><80><99> {aka <E2>
<80><98>int(unsigned int, unsigned int, unsigned int, int, int, long int)<E2><80><99>}
39 | _hurdsig_fault_catch_exception_raise (mach_port_t port,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from hurdfault.c:27:
/home/josepht/build-many-glibcs/build/glibcs/i686-gnu/glibc/hurd/faultexc_server.h:19:15: note: previous declaration o
f <E2><80><98>_hurdsig_fault_catch_exception_raise<E2><80><99> with type <E2><80><98>kern_return_t(mach_port_t, mach_
port_t, mach_port_t, integer_t, integer_t, integer_t)<E2><80><99> {aka <E2><80><98>int(unsigned int, unsigned int
, unsigned int, int, int, int)<E2><80><99>}
19 | kern_return_t _hurdsig_fault_catch_exception_raise
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[3]: *** [../o-iterator.mk:9: /home/josepht/build-many-glibcs/build/glibcs/i686-gnu/glibc/hurd/hurdfault.o] Error
1
Thanks for any insights.
Thanks,
Joe
next reply other threads:[~2023-06-22 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 19:59 Joe Simmons-Talbott [this message]
[not found] ` <f10bb7c8-90f2-9c15-62ad-657bca63ba17@redhat.com>
[not found] ` <CAN9u=HdwoUqDwD1MmF7OQij0-9y402dSMM7uzaQdzBWhnMchFg@mail.gmail.com>
2023-06-23 12:25 ` Carlos O'Donell
[not found] ` <CAAQBMsO4zHaj6fAbWn+O0+=ZaAOR1DxL6Sm8RFcjxpvAhn2FJw@mail.gmail.com>
2023-06-23 12:30 ` Carlos O'Donell
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=20230622195952.GL6392@oak \
--to=josimmon@redhat.com \
--cc=libc-help@sourceware.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).