Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#40751 closed defect (invalid)

p5.12-net-ssleay @1.550.0 build failure

Reported by: lightquake@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port:

Description

When I try to sudo port install p5.12-net-ssleay, even after a sudo port clean --all p5.12-net-ssleay, I get this (running with -d):

*** Found OpenSSL-1.0.1e installed in /opt/local
*** Be sure to use the same compiler and options to compile your OpenSSL, perl,
    and Net::SSLeay. Mixing and matching compilers is not supported.
Do you want to run external tests?
These tests *will* *fail* if you do not have network connectivity. [n] n
Writing Makefile for Net::SSLeay
DEBUG: Executing proc-post-org.macports.configure-configure-0
/usr/bin/sed: can't read /^CCFLAGS *=/s/$/ -arch x86_64/: No such file or directory
Command failed: find /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-net-ssleay/p5.12-net-ssleay/work/Net-SSLeay-1.55 -name Makefile -type f -print0 | xargs -0 /usr/bin/sed -i "" '/^CCFLAGS *=/s/$/ -arch x86_64/' ;
Exit code: 1
Error: org.macports.configure for port p5.12-net-ssleay returned: command execution failed
DEBUG: Error code: NONE
DEBUG: Backtrace: command execution failed
    while executing
"$post $targetname"
Warning: targets not executed for p5.12-net-ssleay: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install

Full log file attached.

Attachments (1)

main.log (13.5 KB) - added by lightquake@… 11 years ago.

Download all attachments as: .zip

Change History (3)

Changed 11 years ago by lightquake@…

Attachment: main.log added

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Resolution: invalid
Status: newclosed

The only way I can imagine that problem occurring is if you replaced /usr/bin/sed with gnused. /usr/bin/sed is supposed to be bsdsed on OS X and replacing it with gnused will cause problems, so please put back bsdsed, for example by restoring it from your backups or by reinstalling OS X.

comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Meanwhile, I've changed the perl5-1.0 portgroup in r112102 so that it uses fs-traverse and reinplace, instead of manually calling /usr/bin/sed.

Note: See TracTickets for help on using tickets.