In message <FD87DC0EB086048483D3A829@[192.168.1.9]> on Sun, 24 Jan 2016 14:45:13 -0800, Quanah Gibson-Mount <[email protected]> said:
quanah> --On Sunday, January 24, 2016 11:30 PM +0100 Richard Levitte quanah> --<[email protected]> wrote: quanah> quanah> > In message <DE9F941D87C9EE5AEFAAB903@[192.168.1.9]> on Sun, 24 Jan quanah> > 2016 quanah> > 12:36:29 -0800, Quanah Gibson-Mount <[email protected]> said: quanah> > quanah> > quanah> --On Sunday, January 24, 2016 9:32 AM +0100 Richard Levitte quanah> > quanah> --<[email protected]> wrote: quanah> > quanah> quanah> > quanah> >> A more portable fix would be quanah> > quanah> >># !/usr/bin/env perl quanah> > quanah> > quanah> > quanah> > Yes. Thanks for the reminder. quanah> > quanah> quanah> > quanah> Hm, we did that in some script in Zimbra, and it ended up quanah> > causing quanah> > quanah> segfaults on RHEL systems that were pulling in a different quanah> > perl quanah> > than quanah> the system perl. I'll see if I can track down exactly quanah> > what quanah> > the issue quanah> was. quanah> > quanah> > Sounds like crappy $PATH... quanah> quanah> Actually it was Ubuntu rather than RHEL. Unfortuantely, beyond that, quanah> we're lacking on details, other than it was a perl found in quanah> /usr/local/bin. Ok, so I take it someone had made a local build and installation of perl and forgot to clear it out when the perl package was installed. That *ahem* happens to me at times. That's nothing the OpenSSL build can have any control over, or env. Generally speaking, '#!/usr/bin/env perl' is the right thing to do, really. Cheers, Richard -- Richard Levitte [email protected] OpenSSL Project http://www.openssl.org/~levitte/ _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
