Date: Sat, 20 Mar 2004 16:45:40 +0300 From: Andrey Chernov <ache@nagual.pp.ru> To: Peter Edwards <peter.edwards@openet-telecom.com>, Jason Andresen <jandrese@mitre.org>, Doug White <dwhite@gumbysoft.com>, freebsd-current@freebsd.org Subject: Re: Pan crashing in libgnuregex after -pthread switchover Message-ID: <20040320134540.GA54827@nagual.pp.ru> In-Reply-To: <20040320130416.GB53843@nagual.pp.ru> References: <4058AC1C.10208@mitre.org> <xzpwu5i7s9v.fsf@dwp.des.no> <4059B9CD.1010003@openet-telecom.com> <4059C3B0.4080003@mitre.org> <20040318095842.W62520@carver.gumbysoft.com> <4059E668.1030405@openet-telecom.com> <405B055D.30203@mitre.org> <405B1304.1020307@openet-telecom.com> <20040320130416.GB53843@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 20, 2004 at 04:04:17PM +0300, Andrey Chernov wrote: > It is interesting note, but I don't see how you really can use _both_ GNU > regex and libc regexec/regcomp. To use libc regexec/regcomp you need to Lets think about even more complex case: file a.c #include <gnu/regex.h> file b.c #include <regex.h> // I.e. system one It breaks GNU regex ABI when calling, say, regcomp() because all _modern_ programs which want GNU regex family assumes that regcomp is part of GNU regex library (or GNU libc) and wants it there. If we remove regcomp() from GNU regex library (like in old variant with NO_POSIX_COMPAT you mentioned), the library will be incomplete and there is no chance for some programs to find needed functions there. I mean - they include <gnu/regex.h> but got wrong (system one) regcomp() in result, if NO_POSIX_COMPAT will be introduced again. -- Andrey Chernov | http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040320134540.GA54827>