From: "Ralf Habacker" <Ralf.Habacker@freenet.de>
To: <cygwin@cygwin.com>
Subject: RE: duplicate regexec/regcomp functions detected
Date: Mon, 31 Dec 2001 12:04:00 -0000 [thread overview]
Message-ID: <000b01c1922d$3f42ca90$865c07d5@BRAMSCHE> (raw)
In-Reply-To: <20011231171737.GC1801@redhat.com>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Christopher Faylor
> Sent: Monday, December 31, 2001 6:18 PM
> To: cygwin@cygwin.com
> Subject: Re: duplicate regexec/regcomp functions detected
>
>
> On Mon, Dec 31, 2001 at 10:28:52AM +0100, Ralf Habacker wrote:
> >> -----Original Message-----
> >> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> >> Of Christopher Faylor
> >> Sent: Sunday, December 30, 2001 8:37 PM
> >> To: cygwin@cygwin.com
> >> Subject: Re: duplicate regexec/regcomp functions detected
> >>
> >>
> >> On Sat, Dec 29, 2001 at 08:21:43PM +0100, Ralf Habacker wrote:
> >> >Ralf Habacker wrote
> >> >>The patch for creating libpthread.a is appended. It contains a script names
> >> "speclib" and an
> >> >additional rule >in the src/winsup/cygwin/Makefile.in.
> >> >
> >> >I have recognized yet a little problem with the speclib script. I have checked
> >> this from the
> >> >cygwin build dir without any errors. If someone was in the winsup dir and does a
> >> make cygwin
> >> >or make, than some command in speclib does not found the input files. The problem
> >> is that ar
> >> >does not have an -o option for an output dir, so the hack to emulate that does
> not work.
> >> >Perhaps it is better to use the absolute path of the input library, but currently
> >> I have no
> >> >idea, how to solve this. :-(
> >> >Perhaps anyone else have an idea ?
> >> >
> >> >speclib
> >> >
> >> >...
> >> >cd $tmpdir
> >> >$ar x $PWD/$inlib $FILES
> >> >cd ..
> >> >...
> >>
> >> I don't know if this helps bug can I suggest an alternate approach? Use
> >> cygwin.din to derive your list of files and do something like:
> >>
> >> $(LIBPTHREAD_A): speclib new-$(DLL_NAME) cygwin.din pthread.o thread.o
> >> /bin/sh ${word 1,$^} $@ "$(NM)" "$(AR)" "$(RANLIB)" ${wordlist 3, 99, $^}
> >>
> >>
> >That means, that libpthread contains all symbols of cygwin.dll and not only the
> symbols from
> >pthread, which are published in pthread.h ? Does libpthread should only contain pthread
> >relates symbols ?
>
> Why would you infer that? You ran 'nm' over cygdll.a. Does that mean that all of the
> symbols from cygdll.a were part of libpthread.a?
>
No, only the symbols, which are defined in pthread.o, called the "reflib" in speclib.
> 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/
>
>
--
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-31 19:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-12-31 14:12 ` Christopher Faylor
[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
2002-01-01 13:56 ` Ralf Habacker
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='000b01c1922d$3f42ca90$865c07d5@BRAMSCHE' \
--to=ralf.habacker@freenet.de \
--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).