From: "Ludovic Courtès" <ludo@gnu.org>
To: zamfofex <zamfofex@twdb.moe>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: GMP GCC C++ Hurd cross-build failure on core-updates
Date: Mon, 19 Dec 2022 22:06:00 +0100 [thread overview]
Message-ID: <87mt7jcddz.fsf@gnu.org> (raw)
In-Reply-To: <662026881.1697453.1670321161488@privateemail.com> (zamfofex@twdb.moe's message of "Tue, 6 Dec 2022 07:06:01 -0300 (BRT)")
Hi zamfofex,
And sorry for the late reply…
zamfofex <zamfofex@twdb.moe> skribis:
> hurdauth.c:166:1: error: conflicting types for ‘_S_msg_del_auth’; have ‘kern_return_t(mach_port_t, task_t, const int *, mach_msg_type_number_t, const int *, mach_msg_type_number_t)’ {aka ‘int(long unsigned int, long unsigned int, const int *, unsigned int, const int *, unsigned int)’}
> 166 | _S_msg_del_auth (mach_port_t me,
> | ^~~~~~~~~~~~~~~
> In file included from hurdauth.c:19:
> /tmp/guix-build-glibc-cross-i586-pc-gnu-2.35.drv-0/build/hurd/hurd/msg_server.h:72:15: note: previous declaration of ‘_S_msg_del_auth’ with type ‘kern_return_t(mach_port_t, mach_port_t, int *, mach_msg_type_number_t, int *, mach_msg_type_number_t)’ {aka ‘int(long unsigned int, long unsigned int, int *, unsigned int, int *, unsigned int)’}
> 72 | kern_return_t _S_msg_del_auth
> | ^~~~~~~~~~~~~~~
> make[2]: *** [../o-iterator.mk:9: /tmp/guix-build-glibc-cross-i586-pc-gnu-2.35.drv-0/build/hurd/hurdauth.o] Error 1
Looking at this, glibc now has ‘const’ qualifiers for the ‘uids’ and
‘gids’ parameters:
--8<---------------cut here---------------start------------->8---
kern_return_t
_S_msg_del_auth (mach_port_t me,
task_t task,
const_intarray_t uids, mach_msg_type_number_t nuids,
const_intarray_t gids, mach_msg_type_number_t ngids)
--8<---------------cut here---------------end--------------->8---
This comes from this glibc commit:
commit 0eb230ccceee70c4b5d2a75807d2189aa4ed6e7c
Date: Sun Jan 16 18:28:40 2022 +0000
hurd: Make RPC input array parameters const
This follows mig's cf4bcc3f1435 ("Also add const qualifiers on server
side")
My guess is that you’re running a version of MiG that’s older than
cf4bcc3f1435 (MiG commit), and thus it generates stubs (such as the
‘msg_server.h’ file mentioned in the error message above) that lack
those ‘const’ qualifiers.
If that reasoning is good, updating MiG should fix it.
HTH,
Ludo’.
next prev parent reply other threads:[~2022-12-19 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 7:23 GMP GCC C++ Hurd cross-build failure on core-updates zamfofex
2022-12-04 16:46 ` Joshua Branson
2022-12-05 16:08 ` Ludovic Courtès
2022-12-06 10:06 ` zamfofex
2022-12-06 11:20 ` zamfofex
2022-12-08 15:43 ` Ludovic Courtès
2022-12-19 21:06 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 7:24 Nathan Dehnel
2022-12-15 11:17 ` Svante Signell
2022-12-19 10:57 ` Svante Signell
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=87mt7jcddz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zamfofex@twdb.moe \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.