Opened 12 years ago
Closed 12 years ago
#35759 closed defect (duplicate)
kdelibs4 does not build on MAC OS 10.8
Reported by: | kkgokturk@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ||
Port: | kdelibs4 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Hi, here is the log of error which i encountered while trying to build kdelibs4. (sudo port -v install kdelibs4)
log:
:info:build [ 22%] Built target kdecore :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdelibs4/kdelibs4/work/build' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdelibs4/kdelibs4/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kdelibs4/kdelibs4/work/build" && /usr/bin/make -j4 -w all :info:build Exit code: 2 :error:build org.macports.build for port kdelibs4 returned: command execution failed :debug:build Error code: CHILDSTATUS 62074 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"
Change History (3)
comment:1 follow-up: 2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Port: | kdelibs4 added |
comment:3 Changed 12 years ago by mf2k (Frank Schima)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The portion of the output that you pasted above doesn't actually contain the relevant error. I assume this is a duplicate of #34378. If you attach the main.log file we could find out for sure.