Yes, sorry, I interrupted right away because the very first time I had done this and I had gone AFK because it seemed like a long exec. And after about 30 minutes, it caused several strange problems on the PC, even after restarting.
Maybe testing on a nested VM should be 'safe,' but atm I don't have that setup. 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. If you need any more info or want to run other tests, lmk. Idk if I'll be able to respond today, I have to pack my bags. Anyway, thank you very much for the links/suggestions. I'm learning Bash and C, but not making much progress lately Good luck On Tuesday, August 26th, 2025 at 3:18 PM, Zack Weinberg <[email protected]> wrote: > On Tue, Aug 26, 2025, at 10:54 AM, Z wrote: > > > Sorry, I didn't understand it. I'm not good with these things. > > > You seem to have followed my instructions just fine, so I think you may > be better at "these things" than you think you are :-) If you want to > get better at working with the Unix command line, I can recommend these > tutorials: > > * https://ryanstutorials.net/linuxtutorial/ > * https://www.learnenough.com/command-line-tutorial > * https://www.shellscript.sh/ (more about shell scripting than the interactive > command line, but still useful) > * https://wizardzines.com/ (you have to pay for these but they're worth it) > > Having said that, I think you did not wait long enough before interrupting > the `sh -x configure` command that I had you run. It did start printing > stuff that looks repetitive, but I know what it's doing and it's not actually > in an infinite loop at that point. Please try again. This time, wait at least > five minutes before interrupting the command. > > > I couldn't even figure out if you have a public bug tracker or not. If > > so, could you give me the link? > > > It's https://savannah.gnu.org/support/?group=autoconf but since we are > > already talking by email let's keep working on this problem that way. > > zw
archive.tar.gz
Description: application/gzip
