X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <29771871.post@talk.nabble.com> Date: Tue, 21 Sep 2010 10:40:35 -0700 (PDT) From: "kenny AT ca" To: cygwin AT cygwin DOT com Subject: Re: missing pthread.h in building 64-bit aaplications In-Reply-To: <4C9877B3.30608@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <29764972 DOT post AT talk DOT nabble DOT com> <4C9877B3 DOT 30608 AT users DOT sourceforge DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I guess I found the reason why x86_64-w64-mingw32-gcc can't locate pthread.h. It's because a macro #if HAVE_PTHREAD #include is used in source files, but the macro is not defined by mingw, about which I found it existiing before according to google search. I re-built it after the macro was commentted, and pthread.h was in. How is your thinking? Another, I added -v and dependency output showed usr\x86_64-w64-mingw32\sys-root\mingw\include was in. So the search path mechanism is not a problem. JonY-6 wrote: > > On 9/21/2010 08:01, kenny AT ca wrote: >> >> Hello All, >> >> Goal: Building 64-bit application on Cygwin >> OS: 64-bit Windows 7 >> >> I used "x86_64-w64-mingw32-gcc ...." to build the application, but >> failed. >> The output tells missing pthread.h. pthread.h is included in one of my >> source files. >> >> I located the file, one in C:\cygwin\usr\include, the other >> C:\cygwin\usr\x86_64-w64-mingw32\sys-root\mingw\include. >> >> I tried using -I to tell gcc to include pthread.h, but failed. why? > > Hi, > > Can you show us the command line used to compile? Add a "-v" as well so > we can see where gcc searched for the headers. > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://old.nabble.com/missing-pthread.h-in-building-64-bit-aaplications-tp29764972p29771871.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple