From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: duplicate regexec/regcomp functions detected
Date: Tue, 01 Jan 2002 10:30:00 -0000 [thread overview]
Message-ID: <20020101183002.GA9396@redhat.com> (raw)
In-Reply-To: <20020101185207.A17787@cygbert.vinschen.de>
On Tue, Jan 01, 2002 at 06:52:07PM +0100, Corinna Vinschen wrote:
>On Tue, Jan 01, 2002 at 11:59:21AM -0500, Chris Faylor wrote:
>> On Tue, Jan 01, 2002 at 03:24:49PM +0100, Ralf Habacker wrote:
>> >Then search cygdll.a after those symbols and extract only the relevant
>> >d000xxx.o from cygdll.a to a newly created import library named
>> >libpthread.a or other revelant name.
>>
>> And, here is where I don't understand your confusion. You don't need to
>> search cygdll.a. You already have a text file available to you which
>> contains all of the exports from the cygwin DLL -- cygwin.def.
>
>Which results in some missing symbols in libc.a, namely the symbols
>from $(LIBCOS). The change to have different link libs have let me
>think that we could drop -lcygwin from the gcc specs file in favour
>of -lc. But that's impossible w/o $(LIBCOS) linked to libc.a. Did
>I missunderstood something here?
Yes. We're not dropping libcygwin.a in favor of libc.a.
cgf
--
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:[~2002-01-01 18:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01df01c19259$1cbb8300$0200a8c0@lifelesswks>
2002-01-01 6:27 ` Ralf Habacker
2002-01-01 9:26 ` Christopher Faylor
2002-01-01 9:53 ` Corinna Vinschen
2002-01-01 10:30 ` Christopher Faylor [this message]
2002-01-01 13:56 ` Ralf Habacker
2001-12-13 12:48 Ralf Habacker
2001-12-14 2:40 ` Corinna Vinschen
2001-12-27 10:20 ` Ralf Habacker
2001-12-27 10:21 ` Christopher Faylor
2001-12-28 5:21 ` Ralf Habacker
2001-12-28 5:22 ` Robert Collins
2001-12-28 10:17 ` Christopher Faylor
2001-12-29 12:43 ` Ralf Habacker
2001-12-30 5:03 ` Christopher Faylor
2001-12-30 7:34 ` Ralf Habacker
2001-12-30 11:56 ` Christopher Faylor
2001-12-31 11:19 ` Ralf Habacker
2002-01-01 7:07 ` Corinna Vinschen
2002-01-01 16:00 ` Ralf Habacker
2002-01-02 2:04 ` Corinna Vinschen
2002-01-02 2:11 ` Ralf Habacker
2001-12-29 14:15 ` Ralf Habacker
2001-12-29 16:40 ` Ralf Habacker
2001-12-30 14:35 ` Christopher Faylor
2001-12-30 16:42 ` Christopher Faylor
2001-12-31 1:16 ` Christopher Faylor
2001-12-31 2:42 ` Ralf Habacker
2001-12-31 11:06 ` Christopher Faylor
2001-12-31 12:04 ` Ralf Habacker
2001-12-31 14:12 ` 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=20020101183002.GA9396@redhat.com \
--to=cgf@redhat.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).