| 6 | | On Monterey x86_64, reverting your change to `portarchivetype`, I tried destrooting pari and, every second or two, scanning the work directory for sparse files with Sparsity. (I scanned frequently since we know the problem fixes itself within 10 seconds of the files being created.) Aside from a log file in the configure phase, I didn't see any sparse files. I also tried reverting your change that blacklists Xcode clang; no change. I haven't seen the problem with the pari tbz2 archive on my system. If you consistently see the problem on your system, you could try scanning with Sparsity to see if we can confirm the theory that the problem occurs when there are sparse files. |
| | 6 | On Monterey x86_64, reverting your change to `portarchivetype`, I tried destrooting pari and, every second or two, scanning the work directory for sparse files with Sparsity. (I scanned frequently since we know the problem fixes itself within 10 seconds.) Aside from a log file in the configure phase, I didn't see any sparse files. I also tried reverting your change that blacklists Xcode clang; no change. I haven't seen the problem with the pari tbz2 archive on my system. If you consistently see the problem on your system, you could try scanning with Sparsity to see if we can confirm the theory that the problem occurs when there are sparse files. |
