[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C++ vs. glibc/Hurd/Mach headers
From: |
Samuel Thibault |
Subject: |
Re: C++ vs. glibc/Hurd/Mach headers |
Date: |
Sun, 27 Nov 2016 17:32:41 +0100 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Samuel Thibault, on Sun 27 Nov 2016 17:14:26 +0100, wrote:
> > In file included from /usr/include/errno.h:35:0,
> > from <stdin>:1:
> > /usr/include/hurd.h: In function ‘int __hurd_fail(error_t)’:
> > /usr/include/hurd.h:60:13: error: invalid conversion from ‘int’ to
> > ‘error_t {aka __error_t_codes}’ [-fpermissive]
> > err = EIEIO;
> > ^
> > /usr/include/hurd.h:64:13: error: invalid conversion from ‘int’ to
> > ‘error_t {aka __error_t_codes}’ [-fpermissive]
> > err = ENOMEM;
> > ^
> > /usr/include/hurd.h:68:13: error: invalid conversion from ‘int’ to
> > ‘error_t {aka __error_t_codes}’ [-fpermissive]
> > err = EINVAL;
>
> The HURD_MSGPORT_RPC seems missing casts between kern_error and error_t
> indeed.
Although the problem is actually that you passed 0 instead of ESUCCESS,
but it'd be very inconvenient to have to pass ESUCCESS. So I have
commited the cast.
Samuel