In message <c965dc37-04ae-60ec-57f7-d58c51e79b6a@xxxxxxxxxxxxx> on Sat, 24 Feb 2018 06:14:50 -0500, Dennis Clarke <dclarke@xxxxxxxxxxxxx> said: dclarke> On 24/02/18 05:13 AM, Richard Levitte wrote: dclarke> > In message <607c8d70-4283-1b55-2eac-c9f30a3a3f92@xxxxxxxxxxxxx> on dclarke> > Sat, 24 Feb 2018 00:24:34 -0500, Dennis Clarke <dclarke@xxxxxxxxxxxxx> dclarke> > said: dclarke> > dclarke> Not sure why but the various scripts and test files are hell dclarke> > dclarke> bent on using the perl in the system as opposed to what I dclarke> > dclarke> have set in an env var PERL=/usr/local/bin/perl. dclarke> > Hmmm, if it's hell bent on anything, it's on what perl was used to run dclarke> > 'Configure'. I'm not sure if you use that script directly or if you dclarke> > use 'config'... the latter will certainly look at $PERL to run dclarke> dclarke> OKay ... I can try "config" however I did use "Configure" : dclarke> dclarke> corv $ ./Configure shared zlib threads solaris64-sparcv9-cc Ah, yes. And since you probably have the system perl first along your $PATH, that's the one you're gonna get registered. The workaround would be this: /usr/local/bin/perl ./Configure shared zlib threads solaris64-sparcv9-cc Cheers, Richard -- Richard Levitte levitte@xxxxxxxxxxx OpenSSL Project http://www.openssl.org/~levitte/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
