From: Teun Burgers <a.rburgers@freeler.nl>
To: cygwin@cygwin.com
Cc: Robert Collins <robert.collins@itdomain.com.au>
Subject: Re: gcc -mno-cygwin creates cygwin executables!
Date: Wed, 12 Dec 2001 12:15:00 -0000 [thread overview]
Message-ID: <3C17B526.60915DD9@freeler.nl> (raw)
In-Reply-To: <04ea01c18303$55406a70$0200a8c0@lifelesswks>
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)
This comes about since gcc -mno-cygwin searches for libs in /usr/lib
and libpthread.a is a symlink to libcygwin.a
One way to fix this would be to break out the thread functions of
libcygwin.a into a separate libpthread.a. When you then link with
gcc -mno-cygwin, libcygwin.a is not linked in and the link will fail.
Apparantly for performance and technical reasons this is not
recommendable.
This has to do with libcygwin.a depending on the pthread functions.
Another would be to put the libpthread.a symlink in a directory that gcc
-mno-cygwin
doesn't search, e.g. /usr/lib/cygwin, and add this library to the specs
for cygwin
links.
What would be the problem with this approach?
There are 2 other alternatives that fix the configure problem:
1) How about making libpthread.a a dummy library with just one .o file
with a dummy (empty) function? This does fix this particular
configure problem, but might have side effects since the pthread
symbols
are no longer in libpthread.a
2) include the pthread symbols in both libcygwin.a and libpthread.a?
Robert Collins wrote:
> Hmm. Why not put the win32 api checks in the configure script ahead of
> pthread?
What do you mean with that?
Teun
--
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/
next prev parent reply other threads:[~2001-12-12 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 13:43 a.rburgers
2001-12-12 4:27 ` Robert Collins
2001-12-12 12:15 ` Teun Burgers [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 15:20 Teun Burgers
2001-12-12 14:31 Robinow, David
2001-12-12 13:54 Steve Jorgensen
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=3C17B526.60915DD9@freeler.nl \
--to=a.rburgers@freeler.nl \
--cc=cygwin@cygwin.com \
--cc=robert.collins@itdomain.com.au \
/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).