On Wed, Aug 27, 2025, at 7:04 AM, Z wrote:
> Sorry for the delay.
No worries. This project moves at a slow and steady pace.
> The execution on the shared folder actually took about 1 minute, while
> on /tmp it was instantaneous
That means you were correct in thinking that the shared folder has
something to do with the problem.
In "test.1301.output" - execution in /tmp - I see a log of a normal,
successful compilation producing an executable. GCC's `-v` option makes
it print out a bunch of detail about its configuration, and then report
on each of the individual steps it takes to compile and, in this case,
also link the test program, and that report is what's in there.
In "test.1266.output" - execution in /mnt/share/Coding, your shared
folder - things start out the same, but right after the "cc1" step of
compilation begins (/usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/cc1 is an
internal component of GCC that's responsible for almost all the actual
work of turning C into assembly language) something very strange
happens. cc1 prints out some information about where it's going to look
for headers ... and then it gets stuck, somehow, and something starts
emitting binary zeroes to the log file. Almost four megabytes of them.
I suspect it would have gone on doing that forever if not interrupted by
the "timeout" program, and that your original symptoms, where a configure
run got stuck and somehow ground the entire computer to a halt, were because
these binary zeroes were filling up all available space somewhere.
I'm now certain that this is not a bug in Autoconf. Autoconf is just using
the C compiler normally. But I don't know where the bug actually is yet.
I think it's most likely to be in the software backing your shared folder,
but I cannot think of any plausible reason why a bug in a _filesystem_
should cause cc1 to go into an infinite loop or to spew binary zeros.
So I'd like you to do one more test for me.
Make sure you have the `strace` program installed on your computer.
(I believe you're using Arch Linux, so `sudo pacman -S strace` should
install it if it's not already installed.) Then run this command,
exactly as shown:
echo 'int x;' | (
cd /mnt/share/Coding &&
strace -f -tt -o /tmp/cc1.trace timeout 5s \
/usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/cc1 -quiet -o - -
)
And send us the file `/tmp/cc1.trace`. (It will be large, please
compress it.)
zw
