Re: problems with "make install" directory permissions

Karl Berry wrote: > https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html > > I can understand increasing permissions to allow +rx on installation > directories, but why force 755, thus disallowing group writability? > I've never understood this forcing of 755. As the one who originally br

Re: problems with "make install" directory permissions

On Mon, Jul 27, 2020 at 3:03 PM Paul Eggert wrote: > > On 7/27/20 2:24 PM, Karl Berry wrote: > > https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html > > > > I can understand increasing permissions to allow +rx on installation > > directories, but why force 755, thus disallowing group writ

[PATCH] xalloc-die: don’t depend on xalloc

This removes a circular dependency, as xalloc depends on xalloc-die. * modules/xalloc-die (Files): Add lib/xalloc.h. (Depends-on): Remove xalloc. Add extern-inline, stdint, xalloc-oversized (this is for xalloc.h). --- ChangeLog | 6 ++ modules/xalloc-die | 5 - 2 files changed, 10

Re: problems with "make install" directory permissions

On 7/27/20 2:24 PM, Karl Berry wrote: https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html I can understand increasing permissions to allow +rx on installation directories, but why force 755, thus disallowing group writability? I've never understood this forcing of 755. I expect it was

Re: problems with "make install" directory permissions

https://lists.gnu.org/r/bug-bison/2020-07/msg00042.html I can understand increasing permissions to allow +rx on installation directories, but why force 755, thus disallowing group writability? I've never understood this forcing of 755. I don't think Zack plans to release a new Automake.

Re: Missing '_Noreturn'

On 7/27/20 12:03 AM, Florian Weimer wrote: The compiler is correct for [[noreturn]]: | The first declaration of a function shall specify the noreturn | attribute if any declaration of that function specifies the noreturn | attribute.

Re: Missing '_Noreturn'

Paul Eggert wrote: -extern void dfawarn (const char *); +extern _Noreturn void dfawarn (const char *); That can't be right, as dfawarn typically does return. Does the following work around the compiler bug? If not we can use stronger medicine. diff --git a/tests/test-dfa-match-aux.c b/tests

Re: Missing '_Noreturn'

* Paul Eggert: > On 7/26/20 3:10 PM, Gisle Vanem wrote: >> Here's an error though: >> >>   test-dfa-match-aux.c >>   test-dfa-match-aux.c(39): error C2381: 'dfawarn': redefinition; >>   '__declspec(noreturn)' or '[[noreturn]]' differs >>   lib\dfa.h(125): note: see declaration of 'dfawarn' > >