[PATCH] remove pthread_atfork issue

* open_issues/pthread_atfork.mdwn: delete file --- open_issues/pthread_atfork.mdwn | 111 1 file changed, 111 deletions(-) delete mode 100644 open_issues/pthread_atfork.mdwn diff --git a/open_issues/pthread_atfork.mdwn b/open_issues/pthread_atfork.mdwn deleted fi

[PATCH] Delete ipc_info.h since it is not used

--- We don't implement this interface and the types are not used anywhere. Makefrag.am | 1 - include/mach_debug/ipc_info.h | 77 --- include/mach_debug/mach_debug_types.h | 1 - ipc/mach_debug.c | 1 - 4 files chan

Re: [PATCH] mig: explicitly use -std=gnu11

On Wed, Nov 23, 2022 at 11:51:36AM +0100, Samuel Thibault wrote: Flavio Cruz, le mer. 23 nov. 2022 00:10:10 -0500, a ecrit: Latest GCC will pick up gnu17 by default but gnu11 will be better supported with older compilers. Mmm, but why explicitly requesting gnu11 then? Latest GCC will be fine

Re: Running guix GNU Hurd build

Andy Tai writes: > The Guix HURD image I downloaded was from > https://guix.gnu.org/en/download/latest/ > > at > https://ci.guix.gnu.org/search/latest/image?query=spec:images+status:success+system:x86_64-linux+hurd-barebones.qcow2 > > It can be used to boot a KVM (guest VM) as a GNU/Hurd system

Re: [PATCH] mig: explicitly use -std=gnu11

Flavio Cruz, le mer. 23 nov. 2022 00:10:10 -0500, a ecrit: > Latest GCC will pick up gnu17 by default but gnu11 will be better supported > with older compilers. Mmm, but why explicitly requesting gnu11 then? Latest GCC will be fine with using gnu17, and older GCC will be fine with using whatever