[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Interest in a Cosmopolitan build?
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Interest in a Cosmopolitan build? |
|
Date: |
Thu, 09 Nov 2023 07:44:17 +0200 |
> From: Alex Corcoles <alex@corcoles.net>
> Cc: emacs-devel@gnu.org
> Date: Wed, 08 Nov 2023 21:11:51 +0100
>
> > Can you post the patches here? I'd prefer not to point people to
> > GitHub.
>
> Not sure if this will come out OK:
Thanks, but can you explain the reasons for these changes? They look
strange to me. E.g., why do you care which symbol is #undef'ed here:
> /* Define to read input using SIGIO. */
> -#undef INTERRUPT_INPUT
> +#undef INTERRUPT_INPUT0
Or why do you need to avoid using enum here:
> --- ./emacs-29.1/src/filelock.c 2023-01-01 14:46:43.000000000 +0100
> +++ ./emacs-29.1/src/filelock.c.new 2023-11-04 17:53:19.163803983
> +0100
> @@ -298,7 +298,7 @@
> There is no way to tell whether a symlink call fails due to
> permissions issues or because links are not supported, but luckily
> the lock file code should work either way. */
> -enum { LINKS_MIGHT_NOT_WORK = EPERM };
> +#define LINKS_MIGHT_NOT_WORK EPERM
> +/* Another process on this machine owns it. */
> +#define ANOTHER_OWNS_IT (NEGATIVE_ERRNO ? 1 : -1)
> +
> +/* This Emacs process owns it. */
> +#define I_OWN_IT (2 * ANOTHER_OWNS_IT)
This sounds like a kludgey solution fopr some problem, but what is the
problem?
Are these all the changes you need, or just a sample?
Re: Interest in a Cosmopolitan build?, Richard Stallman, 2023/11/08