Hello,
Pushed!
Sergey Bugaev, le mar. 09 mai 2023 00:30:55 +0300, a ecrit:
> One annoying warning that I get a lot of when building the Hurd with
> GCC 13 is -Wenum-int-mismatch; here's one example:
>
> ../../trans/streamio.c:694:1: warning: conflicting types for
> ‘trivfs_S_file_sync’ due to enum/integer mismatch; have ‘error_t(struct
> trivfs_protid *, mach_port_t, mach_msg_type_name_t, int, int)’ {aka
> ‘error_t(struct trivfs_protid *, unsigned int, unsigned int, int, int)’}
> [-Wenum-int-mismatch]
> 694 | trivfs_S_file_sync (struct trivfs_protid *cred,
> | ^~~~~~~~~~~~~~~~~~
> ../libtrivfs/trivfs_fs_S.h:232:15: note: previous declaration of
> ‘trivfs_S_file_sync’ with type ‘kern_return_t(struct trivfs_protid *,
> mach_port_t, mach_msg_type_name_t, int, int)’ {aka ‘int(struct
> trivfs_protid *, unsigned int, unsigned int, int, int)’}
> 232 | kern_return_t trivfs_S_file_sync
> | ^~~~~~~~~~~~~~~~~~
>
> Other than just using -Wno-enum-int-mismatch, perhaps there is some
> way we could tell GCC that this is very intentional that error_t is
> used interchangeably with int and kernl_return_t?
I don't know.
> Sp how much does actually build? Well, "all of it", but note that:
> - I've disabled pfinet,
> - I'm building --without-parted --without-libcrypt --without-libbz2
> --without-libz --without-rump, so I haven't attempted to build anything
> excluded by those switches.
With the available .debs you should now be able to enable these.
Samuel
