Opened 11 years ago
Last modified 14 months ago
#42582 new defect
Building p5.14-libapreq2 fails (upgrade) — at Version 1
Reported by: | st.graef@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | p5-libapreq2 mod_perl2 p5-html-mason p5-http-server-simple-mason |
Description (last modified by neverpanic (Clemens Lang))
:info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-libapreq2/p5.14-libapreq2/work/libapreq2-2.13" && /usr/bin/make -j4 -w all :info:build Exit code: 2 :error:build org.macports.build for port p5.14-libapreq2 returned: command execution failed :debug:build Error code: CHILDSTATUS 17851 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for p5.14-libapreq2: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port p5.14-libapreq2 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-libapreq2/p5.14-libapreq2/main.log
Change History (1)
comment:1 Changed 11 years ago by neverpanic (Clemens Lang)
Description: | modified (diff) |
---|---|
Priority: | High → Normal |
Note: See
TracTickets for help on using
tickets.
Please use WikiFormatting when posting in Trac and don't set priority to high, since that is reserved for MacPorts Developers as mentioned in the ticket guidelines prominently linked from the "new ticket" page.
You will have to attach
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-libapreq2/p5.14-libapreq2/main.log
before anybody will be able to help you.