Opened 3 years ago
Last modified 4 months ago
#62994 assigned defect
m4 @1.4.19_1: fails on Leopard: /confdir-14B---: No space left on device — at Version 6
Reported by: | kencu (Ken) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | leopard | Cc: | |
Port: | m4 bison findutils coreutils gettext |
Description (last modified by kencu (Ken))
Interestingly, Tiger installed this without any trouble.
I also tried in trace mode, just in case, but same error. Disabling parallel builds didn't fix it either.
:info:configure config.status: creating po/Makefile :info:configure 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---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---: No space left on device :info:configure 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---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---: Directory not empty
Change History (7)
Changed 3 years ago by kencu (Ken)
Attachment: | m4-leopard-fail.log added |
---|
comment:1 Changed 3 years ago by kencu (Ken)
Description: | modified (diff) |
---|
comment:2 Changed 3 years ago by leavenode
comment:3 Changed 3 years ago by kencu (Ken)
Description: | modified (diff) |
---|
comment:4 Changed 3 years ago by kencu (Ken)
For reasons I am not presently able to explain, m4 installed without trouble on the same Leopard system today.
All the other ports had finished updating. I installed it from a git repo rather than the usual default rsync repo. Otherwise I can't see anything that was changed.
My favourite kind of problem: intermittent, and inexplicable :>
comment:5 Changed 3 years ago by kencu (Ken)
Yuk -- just saw this again on another system, and no combo of disabling parallel builds, etc, fixed it.
The issue is coming, it seems, from a test in this file m4/getcwd-abort-bug.m4
that makes it's way into the configure script. I didn't spend hours on it, but it looks like they are looking for some kind of bug in libc on certain versions of linux, that shows up when PATH_MAX < getpagesize ();
.
To get around it, I did this:
$ diff -u configure.old configure --- configure.old 2021-06-05 17:36:56.000000000 -0700 +++ configure 2021-06-05 18:48:13.000000000 -0700 @@ -36350,7 +36350,7 @@ #else int bug_possible = 0; #endif - if (! bug_possible) + if (1) return 0; cwd = getcwd (NULL, 0);
to abort running of the test.
I have no idea of this is a proper fix for this issue. I already tried looking around upstream for the Tiger RegNames issue, and I can't figure out where to even see the commit tree to m4, much less sort out how on Earth they would like you to go about asking a question.
And -- so far this only shows up for me on Leopard, so it's pretty hard to burn my limited cred on reporting Leopard bugs :>
If we want this teeny little fix as a patch in m4 to apply on Leopard (and less?) I'm happy to throw that 10 second patch into the port.
comment:6 Changed 3 years ago by kencu (Ken)
Description: | modified (diff) |
---|
I cleaned and attempted it again with the same issue. I'm thinking it must be something broken about that particular installation.
1.4.19_1 just installed fine on my other Tiger system, a G4 iBook.