From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: duplicate regexec/regcomp functions detected
Date: Fri, 14 Dec 2001 02:40:00 -0000 [thread overview]
Message-ID: <20011214113619.J740@cygbert.vinschen.de> (raw)
In-Reply-To: <015501c18413$5a3d81f0$9a5f07d5@BRAMSCHE>; from Ralf.Habacker@freenet.de on Thu, Dec 13, 2001 at 09:18:39PM +0100
On Thu, Dec 13, 2001 at 09:18:39PM +0100, Ralf Habacker wrote:
> Hi all,
>
> kde needs the regexp functions regexec and regcomp.
>
> The cygwin lib contains the System V8 function call style, while the pcre package (pcreposix)
> provides another style (the system V style I guess). The problem is now, that both libs
> supports the same names for regexec and regcomp but with different parameter/return types.
> This results sometimes in execution failures if the libs are not in the right order like
> shown in the following example.
>
> pcre regexp wanted
>
> $ gcc ... -lpcreposix -lcygwin -> okay
>
> $ gcc ... -lpthreads|-lm|-lc -lpcreposix -lcygwin -> failure: the functions in cygwin lib
> are used
But that order should never happen EXCEPT you're making the big
mistake to give `-lm' or `-lc' on the command line explicitly.
Since -lcygwin is appended automagically and libc.a and libm.a
are the same library anyway, the answer is simply, "Don't do that."
> Especially in libtool related environment with many dependency libs like kde this causes much
> trouble.
>
> Should it not be better, to remove the regexp support from cygwin into a seperate lib, so
> that users has an easier possibility to choose which regexp style they want ?
We didn't want that for compatibility reasons. We often already
discussed to trash the V8 implementation in favor of a POSIX
implementation but that would break older applications which we're
trying to avoid.
Btw., we have another POSIX regex library besides pcreposix: -lregex.
It's somewhat smaller and it's also DLLized. OpenSSH's configure.ac
file has a special check to see if a regex lib exists and if the base
regexp implementation in the std C lib is POSIX compliant. We added
that to the OpenSSH configury a few weeks ago to make Cygwin happy.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
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-14 10:37 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 [this message]
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
[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=20011214113619.J740@cygbert.vinschen.de \
--to=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).