Opened 10 years ago

Last modified 10 years ago

#41589 closed defect

mercurial @2.8 build failure on 10.9 — at Version 1

Reported by: petr.fischer@… Owned by: deric@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: sean@…
Port: mercurial

Description (last modified by ryandesign (Ryan Carsten Schmidt))

:info:build generating mercurial/locale/da/LC_MESSAGES/hg.mo from i18n/da.po
:info:build msgfmt -v -o mercurial/locale/da/LC_MESSAGES/hg.mo i18n/da.po -c
:info:build error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.8" but "10.9" during configure
:info:build make: *** [build] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/2.8'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/2.8" && make -j4 -w all PYTHON=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
:info:build Exit code: 2
:error:build org.macports.build for port mercurial returned: command execution failed
:debug:build Error code: CHILDSTATUS 45012 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 mercurial: org.macports.activate org.macports.build org.macports.destroot org.macports.install

Change History (1)

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

Cc: sean@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to deric@…
Priority: HighNormal

It builds fine for me on Mavericks. Please "sudo port clean mercurial" and try again and then attach the main.log file if it fails again.

Note: See TracTickets for help on using tickets.