On Tue, Aug 26, 2025, at 12:01 PM, Z wrote:
> Anyway, I did it, I ran it again for over 5 minutes. But looking at
> the file sizes, I don't think it will be very useful to you: the
> config file has the same number of bytes, and the other one has even
> less, Idk. I hope I'm wrong.
Actually this is very helpful. I have been able to identify exactly
where the configuration process gets stuck:
+ printf %s 'checking if gcc static flag -static works... '
checking if gcc static flag -static works... + test
+ case e in
+ lt_cv_prog_compiler_static_works=no
+ save_LDFLAGS=
+ LDFLAGS=' -static'
+ echo 'int main(void){return(0);}'
+ eval '$CC' -o 'conftest$ac_exeext' '$CFLAGS' '$CPPFLAGS' '$LDFLAGS'
'conftest.$ac_ext' '$LIBS' '>&5'
^C++ ac_signal=2
The command that was running when you interrupted ./configure, both
times, was the thing on the second-to-last line of this log:
eval '$CC' -o ...
Since it was the same command both times, the hang you're experiencing
is happening _inside the C compiler_, which is trying to compile a
trivial program and link it statically. That gives us some more
things to test.
Please copy and paste the following test script into a file (call it
"test.sh" maybe). Make sure to copy it *exactly as shown*. The exact
spelling and punctuation and line wrapping matters in shell scripts.
#! /bin/sh
exec > test.$$.output 2>&1
pwd
printf 'int main(void) { return 0; }\n' |
timeout -k 30s 30s gcc -static -xc -v -o test.$$.exe -
rm -f test.$$.exe
# end of test script
cd into your shared folder, and then run the shell script. The script
itself does not have to be in the shared folder, but your command line
working directory must be in the shared folder. It will create a file
named something like 'test.12345.output'; the number will probably be
different. It should complete execution after no more than a minute
or two.
Now cd into a directory that *isn't* in the shared folder, such as
/tmp, and run the shell script again. It will create another file
named something like 'test.12345.output', with a number different from
the first file.
Send us both of the test.NNNNN.output files.
Thanks for your patience and assistance as we troubleshoot this.
zw
