This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
In the process of building the latest fetchmail (i.e., 6.2.0) for release, I seem to have stumbled over a Cygwin gcc 3.2 build problem. Although fetchmail builds cleanly under Cygwin gcc 3.2, it does not function properly -- it seems to get completely confused. Here are some of my observations so far: o All of my public fetchmail releases to dated were built with gcc 2.95.3-5 or earlier. o Configured with the defaults (i.e., CFLAGS=-O), fetchmail exits very early in its poll with a "socket error" when attempting to fetch mail from a known good IMAP server. See the first attachment for the details. o Configured with CFLAGS=-g, fetchmail completes its poll cycle. However, the log file shows lots of garbage (include carriage returns). See the second attachment for the details. o Configured with CC=gcc-2, fetchmail behaves as expected. See the third attachment for the details. o Configured with the defaults under Linux and gcc 3.2, fetchmail behaves as expected. Any suggestions on how to best debug this problem or potential root causes will be greatly appreciated. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Attachment:
gcc3-1.log
Description: Text document
Attachment:
gcc3.log
Description: Text document
Attachment:
gcc2.log
Description: Text document
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |