[MacPorts] #57742: cairo @1.16.0 +quartz+universal+x11: cannot upgrade from @1.14.12 to @1.16.0
MacPorts
noreply at macports.org
Mon Jan 25 03:45:56 UTC 2021
#57742: cairo @1.16.0 +quartz+universal+x11: cannot upgrade from @1.14.12 to
@1.16.0
---------------------------+------------------------
Reporter: hugo-ribeiro | Owner: ryandesign
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.5.4
Resolution: | Keywords: xcode10
Port: cairo |
---------------------------+------------------------
Comment (by JDLH):
This bug is blocking me from recompiling `cairo
@1.16.0_1+quartz+universal+x11` at the moment.
I use macOS 10.13.6 High Sierra, Xcode 10.1, and macports 2.6.4 (current).
I currently have `cairo @1.16.0_0+quartz+universal+x11` installed and
active. It appears my last build of cairo was in December 2018.
The revision @1.16.0_1 appears to be motivated by the crash in macOS 11.0
Big Sur described in ticket #61586.
My
`/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_cairo/cairo/main.log`
has the same relevant error message as in the Ticket Description above:
{{{
:info:build In file included from cairo-arc.c:37:
:info:build In file included from ./cairoint.h:434:
:info:build In file included from ./cairo-scaled-font-private.h:45:
:info:build In file included from ./cairo-mutex-type-private.h:45:
:info:build ./cairo-mutex-impl-private.h:262:3: error: In file included
from "XXX: No mutex implementation found. Cairo will not work with
multiple threads. Define CAIRO_NO_MUTEX to 1 to acknowledge and accept
this limitation and compile cairo without thread-safety support."cairo-
base85-stream.c
}}}
My
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_cairo/cairo/work/cairo-1.16.0-i386/config.log`
file contains numerous lines matching comment:3 above, of the form:
{{{
ld: warning: The i386 architecture is deprecated for macOS (remove from
the Xcode build setting: ARCHS)
}}}
I will try the workaround from ticket:50800#comment:2, which appears to
cause cairo's `configure` script to ignore all warning messages during
configure. I worry that this might cause it to ignore valid warnings as
well.
ticket:50800#comment:4 cites some upstream bug reports. I haven't looked
up those yet, to see if upstream has a better fix.
(Um, if Xcode doesn't support i386, why are we compiling for that
architecture? How will the tool even let us? Can we just stop trying to
compile Cairo for i386? I am really in the dark about how architectures
are handled in MacPorts. I'm not griping, just wondering.)
--
Ticket URL: <https://trac.macports.org/ticket/57742#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list