Hi pete, > I didn't add any configure "--with-openssl" or similar to > my pvfs build. But I'm getting those functions somewhere. > Is this right? It looks on the system for reasonable defaults?
Yeah.. Sam added this to openssl.m4 for configure to look for reasonable defaults (/usr). I borrowed those checks for the test sub directory as well. > > Now when I go to build an MPI code, using an MPI library that > was compiled against libpvfs2.so a few weeks ago, it fails on > the crypto symbols: > > mpicc -c -g -Wall perf.c > mpicc -o perf perf.o -lm > /usr/local/pvfs2-openib/lib/libpvfs2.so: undefined reference to > `CRYPTO_num_locks' > [etc.] > > (Adding -lcrypt -lssl does work around the problem.) > > Do I need to rebuild MPI, adding "-lcrypt -lssl" to get the mpicc > script to automatically add these symbols when compiling user > codes? > Is there, instead, an easy way just to avoid your otherwise quite > nice crypto work? We could revert the changes that Sam made to prevent openssl from being checked for in the default paths.. Do you think that would be a reasonable option? We used to do this as of 2 days ago :) Let me know what you want me to do and I can take a stab at patching things appropriately. thanks, Murali _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
