public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robinow, David" <drobinow@dayton.adroit.com>
To: cygwin@cygwin.com
Subject: RE: gcc -mno-cygwin creates cygwin executables!
Date: Wed, 12 Dec 2001 14:31:00 -0000	[thread overview]
Message-ID: <80575AFA5F0DD31197CE00805F650D767B20FB@wilber.adroit.com> (raw)

 I must say I'm baffled by this whole thread (NPI)
Why are you using such a lame program.
 Just add
  #include <pthread.h>
to zz.c and everything should work as intended, no?
 If you don't do that it seems you get what you deserve.
Am I missing something?

-----Original Message-----
From: Teun Burgers [mailto:a.rburgers@freeler.nl]
Sent: Wednesday, December 12, 2001 2:51 PM
To: cygwin@cygwin.com
Cc: Robert Collins
Subject: Re: gcc -mno-cygwin creates cygwin executables!


To sum up this thread:

consider the following program:

main () {
        pthread_create();
}

gcc -mno-cygwin -o zz.exe zz.c -lpthread will compile and build.
A cygcheck on zz.exe reveals that libcygwin.a is linked in. The
problem with this is that a configure script with CC='gcc -mno-cygwin'
will incorrectly find that libpthread.a is available with
AC_SEARCH_LIBS(pthread_create, -lpthread)


--
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/

             reply	other threads:[~2001-12-12 22:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 14:31 Robinow, David [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-12 15:20 Teun Burgers
2001-12-12 13:54 Steve Jorgensen
2001-12-11 13:43 a.rburgers
2001-12-12  4:27 ` Robert Collins
2001-12-12 12:15   ` Teun Burgers
2001-12-12 12:30     ` egor duda
2001-12-12 13:10       ` Teun Burgers
2001-12-12 13:42         ` Christopher Faylor
2001-12-12 14:01     ` Robert Collins
2001-12-11 13:09 Teun Burgers
2001-12-11 13:22 ` Robert Collins
2001-12-11  9:48 Teun Burgers
2001-12-11 12:14 ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80575AFA5F0DD31197CE00805F650D767B20FB@wilber.adroit.com \
    --to=drobinow@dayton.adroit.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).