From: Teun Burgers <a.rburgers@freeler.nl>
To: cygwin@cygwin.com
Subject: Re: gcc -mno-cygwin creates cygwin executables!
Date: Tue, 11 Dec 2001 13:09:00 -0000 [thread overview]
Message-ID: <3C167480.8CDE5A06@freeler.nl> (raw)
Christopher Faylor wrote:
> On Tue, Dec 11, 2001 at 06:47:09PM +0100, Teun Burgers wrote:
> >1) gcc -mno-cygwin searches for libs in /usr/lib.
> > Should it?
> It shouldn't, but it does. Changing this requires a complicated change
> to 'ld'. I don't think that anyone is contemplating such a change.
>
> The only alternative is to use the mingw version of the tools.
I can think of a few other perhaps simpler alternatives.
1) Move the pthread functions from libcygwin.a to a separate library
libpthread.a instead of libpthread.a being a symlink to libcygwin.a.
That
would fix this particular configure problem I think. This already
works this way I found for libpng.a and libjpeg.a.
2) Put some cygwin specific libraries as libpthread.a in /usr/cygwin/lib
and add /usr/cygwin/lib to the specs?
Teun Burgers
--
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 reply other threads:[~2001-12-11 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 13:09 Teun Burgers [this message]
2001-12-11 13:22 ` 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: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 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=3C167480.8CDE5A06@freeler.nl \
--to=a.rburgers@freeler.nl \
--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).