Hi Mark,

On Thu, Jun 14, 2007 at 01:18:55PM +0100, Mark Hobbs wrote:
> Thanks Alexander, please see updates.
You're welcome.

> > > does not appear to be recognised by perl Makefile.PL. I have manually
> I doubled checked this and re-installed all the "use" modules in Makefile.PL
> and still get the same. If you do use "OPENSSL_PREFIX=/usr/local" are you
> sure it is the parameter that is working as this directory is hardcoded into
> the script as a default search location. When I edit the script to include
> my 098 openssl location in the default search path the script runs fine but
> reports the following warning:
>   'OPENSSL_PREFIX' is not a known MakeMaker parameter name.
> which would also suggest that the parameter is not being parsed.
Ah, I assume you are trying to do something along the lines of
perl Makefile.PL OPENSSL_PREFIX=...? OPENSSL_PREFIX is assumed to be
defined in the shell environment, so try something like
OPENSSL_PREFIX=... perl Makefile.PL PREFIX=... or
export OPENSSL_PREFIX=...; perl Makefile.PL PREFIX=...

> Yep, you are completely correct. I needed to change PERL5LIB to include:
>    /openxpki/runtime/lib/perl5/site_perl/5.8.6/
> Things improved after ;)
Fine :-)

> I still get a number of "make test" errors and would appreciate any comments
> on whether they are important or not.
> 
> 1) perl_modules, a number of the cert crypto tests fail (after the CA
> certificate create test) which I presume is related to a message that says I
> don't have openssl 098. I can only assume that the make test script doesn't
> pick up on the correct Openssl 098 location for my system even though this
> was recognised by Makefile.PL and presumably make.
Hmmm, the test file takes it from t/cfg.binary.openssl, which is written
during make. Could you please check that this points to the correct
location?

> 2) For both the client builds (client and Mason) make test stops fairly
> quickly with: "OpenXPKI deployment environment is not installed".
> 
> Not quite sure what I am supposed to do to fix this or if it is a problem.
> 
> Finally, on my environment I could only run "openxpkiadm deploy" and
> openxpki-configure if I change the command references to "openpki_metaconf"
> to "./openpki_metaconf". Not sure if this is a bug or an environment qwirk.
This sounds related. Both the tests and the deployment tools assume that
they can find the (other) deployment tools in the path. So you may need
to set $PATH to a value where they can be found ...

Best regards,
    Alex
-- 
Dipl.-Math. Alexander Klink | IT-Security Engineer
        [EMAIL PROTECTED] | working @ urn:oid:1.3.6.1.4.1.11417

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to