Running cygwin-64 on a 64-bit Win 10 platform and up until recently I have had NO problems at all.
Starting the end of last week, gcc has started behaving badly. Whether I invoke it from a makefile or directly from bash, almost ALL of the timer, it hangs forever, and Task Manager shows cc1 as "running", but consuming no CPU as far as I can tell. If I kill it through task manager, the prompt returns in bash (or make dies with an "interrupted" error. I can do the following: gcc -v and it returns a bunch of stuff, most importantly Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/13/lto-wrapper.exe Target: x86_64-pc-cygwin Configured with: /mnt/share/packages/gccmake/gcc-13/gcc/gcc.x86_64/src/ ... <details deleted> Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.4.0 (GCC) so that much is working. I have gone so far as as shutting down cygwin, renaming /cygwin-64 to /cygin64.sav and reinstalling cygwin from scratch with no change. I also tried uninstalling the gcc-core package and reinstalling it again with no improvement. The simple "hello.c" program run from bash directly: gcc -o hello.exe hello.c hangs forever. Meanwhile, the same sources compile fine on a WinXP machine running an older version of cygwin and gcc (version 5.4.0) run just fine. I'm at a total loss as to where to go next. ANy more information that anyone might need, I'd be happy to send along. But I'm stumped. -- +-----------------------------------+ | Dick Pierce | | Diverse Pursuits | | Technical Engineering/Development | | cartchunk.org | | Boston - Spruce Head | +-----------------------------------+ -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
