On Tue, Aug 26, 2025, at 9:54 AM, Paul Eggert wrote: > On 2025-08-26 05:35, Z wrote: >> Here are the files uploaded to archive.org: >> Video:https://archive.org/details/video_20250826 >> Screen:https://ia800508.us.archive.org/6/items/video_20250826/screen.png > > It's not the location of the video/image that matters. It's the > contents. As the bug's symptoms are plain text, I'd rather see the plain > text. And please cc to bug-autoconf.
I concur with Paul that we need to see text, not a video. However, based on the described symptoms, a plain text transcript of the output of `configure` is unlikely to have enough information to diagnose the problem. Instead, please use the `script` utility to capture a log of all terminal output. Inside the shell started by `script`, run `sh -x configure`. Run that command in the same directory as you ran `configure` originally, and give it all the same arguments that you gave the original `configure` command. This will produce an enormous amount of output. It should be obvious when the infinite loop starts (either the text scrolling by will start repeating itself, or it'll get stuck on a single command). At that point you can cancel the job using ^C or, if that doesn't work, ^\. Exit the nested shell. Send us the `typescript` file that `script` produced, and also the `config.log` file that should have been written to the directory where you ran `sh -x configure`. Both will be very large; please compress them before mailing. zw
