On Mon, 16 Jul 2007 11:04:29 -0700 (PDT)
csilvers@??? (Craig Silverstein) wrote:
> It shows the following commandline:
>
> } x86_64-pc-linux-gnu-gcc -shared -o pcre.so pcre..o -L/usr/lib64 /usr/lib64/libpcre.a -ldl -lnsl -lncurses -lm -lc
>
> Is this really right?? pcre..o, with two dots? pcre.so, rather than
> libpcre.so? Compiling a shared-object library from a static library?
> I've never seen sutff like this before. It's certainly quite
> different from what I see on goobuntu. Is gentoo really so different?
Yes, that is right. It does the same with every object and also does it
if pcre is compiled with -fPIC.
> I think we're really going to need more information to track down
> what's going on here. It sounds like your patch was pretty simple.
> Can you unapply it, run make (or, better, make -k) and include the
> full output? Including your config.log file (from after you ran
> ./configure) might be helpful too.
The patch is pretty simple, see
http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/libpcre/files/pcre-7.1-pic.patch?rev=1.2&view=markup
And here are the logs:
http://dev.gentoo.org/~angelos/pcre-logs/
build/config logs for patched and unpatched pcre 7.2 and build logs for
zsh compiling against patched and unpatched pcre 7.2
