Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20021014154150.74413.qmail@web11502.mail.yahoo.com> Date: Mon, 14 Oct 2002 08:41:50 -0700 (PDT) From: Andrew Lynch Subject: Re: pthreads in YahooPOPs To: egor duda In-Reply-To: <94891653.20021014114321@logos-m.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii OK Thanks! All future messages will go to the mailing list only. I have had some success with SaveMyModem and the cygwin port of YahooPOPs since these messages. I was able to comment out the pthreads portion and add a few other minor changes, Makefile tweaks, etc. After a bit of work, I was able to compile and build the latest YahooPOPs for Linux on Cygwin. I was able to get some success as well, downloading a single message from my Yahoo! Mail account into SaveMyModem. There were some obvious bugs but the proof of concept is there. Now its just fault isolation and debug. (If you want more of the details, visit the URLs below.) Good News! I suspect that the code snippet is a result of a problem on the original authors OS that is not present in Cygwin. I am able to get full or near full functionality without these nonportable modifications. I think the way to handle this and other changes to the code as a result of the Cygwin port is to just add in #ifdef/#endif around this section like any other port. I passed your comments on to the YahooPOPs forum so hopefully the author can eliminate these nonportable sections and make porting to other architectures that much easier. Thanks again for your help! Andrew Lynch PS, if you or anyone else is interested in this FREE (GPL) Cross Platform Mail Filter project using Cygwin, the URLs are: http://sourceforge.net/projects/yahoopops http://sourceforge.net/projects/savemymodem --- egor duda wrote: > Hi! > > >> AL> lock.__m_reserved = 0; > >> AL> lock.__m_count = 0; > >> AL> lock.__m_owner = 0; > >> AL> lock.__m_kind = PTHREAD_MUTEX_TIMED_NP; > >> AL> lock.__m_lock.__status = 0; > >> AL> lock.__m_lock.__spinlock = > __LT_SPINLOCK_INIT; > > It's hard to be sure from such short snippet, but it > looks like they > should use pthread_mutex_init() function if they > want to create a new > pthread mutex and initialize it. > > Single Unix Specification > (http://www.opengroup.org/onlinepubs/007908799/) > is a standard cygwin is trying to conform to. They > have all needed > reference information online. > __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- 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/