>> > The config test for pcre try to compile a test program. The pcre.pir >> > dynamically loads the pcre library. So if, for example, you have only >> > a static pcre lib, it will detect it but fails to use. >> >> That makes sense. Can we change the config test to link against a > dynamic >> pcre? >> > > Patches welcome. I'm cc-ing ambs, who was the original contributor of > this config step and the associated C probe, to see if he can help out.
I see a more generic problem. Several modules add lib links to the parrot executable. Makes sense to link static libraries if that is the intention, but is not convenient to link dynamics that can be, and are, dynamically linked at runtime. This way adds unneeded dependences to the binary packages. Also, if the libraries are linked to the parrot executable or the parrot library makes no sense to fail if they can not be located at runtime. We need some way to know that the library is already linked and his symbols available, without forcing all modules that use a library to check for both cases. -- Salu2
