This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: (new) pcre package for consideration


Ronald Landheer-Cieslak wrote:

> I've taken the changes by Gerrit and Chuck into account for these, so Cygwin uses Libtool for compiling & linking now. However, Chuck's patch seems to break the linking stage anyway: I just unpacked the tarball and ran cygcheck against cygpcreposix.dll and got:
> $ cygcheck cygpcreposix-0.dll Found: .\cygpcreposix-0.dll
> cygpcreposix-0.dll
> D:\cygwin\bin\cygwin1.dll
> C:\WINNT\System32\KERNEL32.dll
> C:\WINNT\System32\ntdll.dll
> D:\cygwin\bin\cygpcre.dll
>
> Can someone tell me whether running libtool --finish /usr/lib will make this alright? (I don't want to break my installation if I know what I'm going to do will do that in any case). If that is the case (that libtool --finish will fix this) I'll write a post-install script, but that would mean making libtool a dependency of pcre.. (which I don't particularly like).



What are you talking about? I don't see any problem there: cygpcreposix depends on cygpcre, and on the system runtime lib cygwin1.dll (which in turn depends on the MS runtime libs kernel32 and ntdll). That's all fine.


So I don't see what "problem" you're trying to fix. libtool --finish simply fixes up some stuff in libpcre.la and possible relinks; on windows, it appears that it is almost never necessary.

--
Chuck




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]