-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK, fortunately I did some more tests before sending the message. I'm writing this *after* having found the problem, but I plan to send the message nonetheless: it could always help people that has the same problem, in the future, and finds this searching the archives...
The solution was: autoconf updated, autom4te directory created and populated by old directory, new autoconf probably sues a sligthly different formats (and doesn't automatically detect the version change itself) -> the cache cannot be loaded correctly and creates weird problems. aka: $ rm -rf autom4te.cache - ------------ Mhh.... $ autoreconf -f -i (just in case) $ ./configure [...] checking for gcc option to produce PIC... -DDLL_EXPORT checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... ...time flies.. time flies... let's check TaskManager, ordeer by CPU load: ccache.exe 85% CPU, 2.512 KB RAM, 1.248 KB Virt.RAM $ mv /usr/local/bin/gcc /usr/local/bin/gcc-not-now $ which gcc /usr/bin/gcc $ ./configure [...] checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... ...time flies.. time flies... let's check TaskManager, ordeer by CPU load: ccache.exe 85% CPU, 2.512 KB RAM, 1.248 KB Virt.RAM AGAIN? 0_o - -- Lapo Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iEYEARECAAYFAkFduHcACgkQaJiCLMjyUvue0gCgpAJ8stsJHXqXun5/KzuLg4Wm 9nQAoIbnMwbn+SrOvx9oOKfDNZ2ocn0n =z7Bl -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
