openssl @1.0.1c openssl configure fails on Mountain Lion

[ports@…]

Xcode V4.4

OSX 10.8

Openssl @1.0.1c

Output messages from build attempt:

port clean openssl
--->  Cleaning openssl

# port install openssl
--->  Computing dependencies for openssl
--->  Fetching archive for openssl
--->  Attempting to fetch openssl-1.0.1c_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/openssl
--->  Fetching distfiles for openssl
--->  Verifying checksum(s) for openssl
--->  Extracting openssl
--->  Applying patches to openssl
--->  Configuring openssl
Error: org.macports.configure for port openssl returned: configure failure: command execution failed
Please see the log file for port openssl for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_openssl/openssl/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port openssl failed

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_openssl/openssl/main.log is attached as a file.

[ports@…]

openssl build log

[ryandesign (Ryan Carsten Schmidt)]

FYI it installs fine for me on Mountain Lion.

[jmroot (Joshua Root)]

Looks like your perl is broken somehow? Should probably enforce /usr/bin/perl in openssl's Configure in any case.

[ports@…]

Replying to jmr@…:

Looks like your perl is broken somehow? Should probably enforce /usr/bin/perl in openssl's Configure in any case

JMR - thank you! your suggestion to use /usr/bin/perl resolved the issue.

[mohamedali.gam@…]

I am running mountain lion, how to enforce perl in openssl's Configure

[mohamedali.gam@…]

Replying to ports@…:

Replying to jmr@…:

Looks like your perl is broken somehow? Should probably enforce /usr/bin/perl in openssl's Configure in any case

JMR - thank you! your suggestion to use /usr/bin/perl resolved the issue.

How did you use it? Can you walk me step by step?

[larryv (Lawrence Velázquez)]

I seem to have unknowingly fixed this with r132609.