The pkg-config website says it runs on OS X, so that shouldn't be the issue.
But if pkg-config is required for the new build process, shouldn't configure test for a valid version of pkg-config early on? Now it either fails at the pkcs11 part of ./configure or with linking errors with openssl (if PKG_CONFIG=true) when pkg-config is not present. Greetings, Frank Op 21 februari 2012 12:44 heeft Alon Bar-Lev <alon.bar...@gmail.com> het volgende geschreven: > On Tue, Feb 21, 2012 at 1:32 PM, Frank de Brabander > <debraban...@gmail.com> wrote: >> When I try to build like this, it seems to fail at linking to openssl >> (OS X Lion). >> >> ./configure PKG_CONFIG=true >> make >> mekboek:openvpn-2.x-master brabander$ ls /usr/lib/libcrypto.* >> /usr/lib/libssl.* >> /usr/lib/libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.8.dylib >> /usr/lib/libcrypto.dylib /usr/lib/libssl.0.9.7.dylib >> /usr/lib/libssl.0.9.8.dylib /usr/lib/libssl.dylib > > I am sorry, but for now you will have to add: > OPENSSL_CRYPTO_LIBS="-lcrypto" > OPENSSL_SSL_LIBS="-lssl" > > I want to get this fixed, but before I do, are you sure you don't have > pkg-config package for this OS? > I searched and found that there is pkg-config. > I don't want to revert to the old detection mechanism if you can > simply use pkg-config... > > Alon.
