[MacPorts] #53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.11" during configure
MacPorts
noreply at macports.org
Wed Dec 7 16:20:27 CET 2016
#53018: mercurial @4.0.1: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but
"10.11" during configure
------------------------+------------------------
Reporter: yabba | Owner: seanfarley
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.5
Resolution: | Keywords:
Port: mercurial |
------------------------+------------------------
Comment (by yabba):
Replying to [comment:4 raimue]:
> Replying to [comment:3 yabba]:
> > Give me the answer for: What _is_ the _usual_ setup? ;)
> > Specify what you expect, please. :)
> >
> > I expected that the update continues to work like the years before. It
stopped working that day, that's the reason I filed the bug.
>
> If we cannot reproduce the problem, we need your input what would be
different on your system that is causing the problem. For example, did you
ever make any changes to your macports.conf? Setting
`macosx_deployment_target` in macports.conf would be something that could
cause this.
OK, I tried to compile darktable. They say, one need to change some
options
("https://redmine.darktable.org/projects/darktable/wiki/Darktable_on_OS_X"):
Add to /opt/local/etc/macports/variants.conf
{{{
+no_gnome +no_x11 +quartz -x11 +llvm34 +gtk3
}}}
Add to /opt/local/etc/macports/macports.conf
{{{
buildfromsource always
cxx_stdlib libc++
macosx_deployment_target 10.9
}}}
Thanks to your hint with `macosx_deployment_target`, I commented that line
and it passes. :)
I'm not in that macports building processes, but should the darktable
build process use the cleaner way to set those options by the/a makefile?
--
Ticket URL: <https://trac.macports.org/ticket/53018#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list