Ramon, about both your patches,
I think I got this sorted out in opencryptoki-next, where I tried to avoid pinning the build system to a hard-coded libdir (lib versus lib64). After all, I'm not sure what would happen if the user configured the build with --libdir=/something/out-of-the/ordinal and expected ock to work. I'm avoiding making changes to the master's tree build system right now. I'll see if I can merge the last patches from master into -next so that we can work there. Thanks, -Klaus On Mon, 3 May 2010 23:03:40 -0300 Ramon de Carvalho Valle <[email protected]> wrote: > Check if 64-bit libraries are built by default and set variables and > paths accordingly. > > Signed-off-by: Ramon de Carvalho Valle <[email protected]> -- Klaus Heinrich Kiwi | [email protected] | http://blog.klauskiwi.com Open Source Security blog : http://www.ratliff.net/blog IBM Linux Technology Center : http://www.ibm.com/linux/ltc ------------------------------------------------------------------------------ _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
