[PATCH] gnulib-tool.py: Don't emit empty Automake snippets.

I finally figured out why these lines are printed in Emacs gnulib.mk.in: +## begin gnulib module manywarnings +ifeq (,$(OMIT_GNULIB_MODULE_manywarnings)) + +endif +## end gnulib module manywarnings + The same thing happens for the 'warnings' module as well. This patch fixes these added lines fr

[PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 67.

Two simple patches. This just makes it so that the library Makefile is output after gnulib-comp.m4. The second patch fixes an error that I noticed because of this change. We have a loop like this: for file in ['Makefile.in.in', 'remove-potcdate.sin']: tmpfile = self.assistant.tmpfilename(join

Re: Problems with directory trees "confdir-14B---" and "confdir3"

On 3/18/24 5:11 PM, Peter Dyballa wrote: > Right now I am on PPC Leopard, Mac OS X 10.5.8. No ktrace/kdump here, only > dtrace. > > Do you know how to invoke dtrace? (Did it last time presumingly decades ago > on Solaris…) >From what I read from the previous messages, we only care about the ord

Re: Problems with directory trees "confdir-14B---" and "confdir3"

> Am 19.03.2024 um 00:38 schrieb Paul Eggert : > > ktrace rm -rf confdir-14B--- Right now I am on PPC Leopard, Mac OS X 10.5.8. No ktrace/kdump here, only dtrace. Do you know how to invoke dtrace? (Did it last time presumingly decades ago on Solaris…) BTW, here it's after local midnight and

[PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 66.

This patch should be pretty easy to test with: $ gnulib-tool --create-testdir --dir mytestdir libtextstyle-optional comparing gnulib-tool.sh and gnulib-tool.py before and after the patch. Also, I am aware that the conditional that I changed in GLTestDir.execute() can be simplified to: #

Re: Problems with directory trees "confdir-14B---" and "confdir3"

On 3/18/24 11:38, Peter Dyballa wrote: Am 18.03.2024 um 18:57 schrieb Paul Eggert : What's up with that "No space left on device" message? I'd say that this is a misinterpretation. Mac OS X was not able to create a new subdirectory, so it said "No space left on device". This sounds unlike

[PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 65.

Hey Bruno, I *think* I did this patch correctly, but there are some code ordering differences which are slightly confusing. I'm not sure if they can cause issues or not. Most of the changes in 'GLImport.py' are just translations of the shell version. I've made one style change: -current_

Re: Problems with directory trees "confdir-14B---" and "confdir3"

> Am 18.03.2024 um 17:51 schrieb Peter Dyballa : > > Usually the test programme returns 3, meaning that it reached the line before > /break;/, which is: > > fail = 3; /* Unable to construct deep hierarchy. */ I have to correct myself! It's my code that I added to the for loop and is execute

Re: Problems with directory trees "confdir-14B---" and "confdir3"

> Am 18.03.2024 um 18:57 schrieb Paul Eggert : > > What's up with that "No space left on device" message? I'd say that this is a misinterpretation. Mac OS X was not able to create a new subdirectory, so it said "No space left on device". When I saw this message I checked that I had enough dis

Re: Problems with directory trees "confdir-14B---" and "confdir3"

Looking back at the original bug report I now see this weird line: rm: confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/con

Re: Problems with directory trees "confdir-14B---" and "confdir3"

> Am 11.01.2022 um 00:35 schrieb Paul Eggert : > > On 1/9/22 03:10, Peter Dyballa wrote: >> checking whether getcwd aborts when 4k < cwd_length < 16k... yes >> and of course the reports about not being able to remove the >> "confdir-14B---" and "confdir3" directory trees, > > So, the probl

Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 64.

Hi Bruno, On 3/18/24 4:05 AM, Bruno Haible wrote: > Thanks a lot. Yes, things get tricky if, after after some refactoring, the > function names don't fit the semantics any more. Yeah, how we have it now should match gnulib-tool.sh, but the naming is a bit misleading. I'll keep it in the back of m

Re: libacl

Gordon Steemson wrote: > While I was originally provoked to attempt work in this area because "why > won't libacl compile?" The answer to this question is: libacl is a library for POSIX ACLs. Its public API is such that it cannot handle the other types of ACLs, that exist on other platforms than

Re: [PATCH] gnulib-tool.py: Follow gnulib-tool changes, part 64.

Hi Collin, > after the change that this patch is following the function names are > slightly misleading since: > > GLModule.isNonTests() != (not GLModule.isTests()) > > Instead we have 3 separate unique operations in gnulib-tool.sh: > > 1. func_verify_tests_module > 2. func_verify_nont

Re: Problems with directory trees "confdir-14B---" and "confdir3"

> Am 11.01.2022 um 00:35 schrieb Paul Eggert : > > On 1/9/22 03:10, Peter Dyballa wrote: >> checking whether getcwd aborts when 4k < cwd_length < 16k... yes >> and of course the reports about not being able to remove the >> "confdir-14B---" and "confdir3" directory trees, > > So, the probl