[MacPorts] #56991: wine cannot be built against the 10.14 SDK
MacPorts
noreply at macports.org
Sat Oct 19 15:45:17 UTC 2019
#56991: wine cannot be built against the 10.14 SDK
---------------------------------------------+------------------------
Reporter: IComplainInComments | Owner: ryandesign
Type: defect | Status: assigned
Priority: Low | Milestone:
Component: ports | Version: 2.5.3
Resolution: | Keywords: mojave
Port: wine wine-devel wine-crossover |
---------------------------------------------+------------------------
Comment (by Gcenx):
Replying to [comment:106 akj850]:
> Sorry for such a basic question, but is it just a selfupdate with an
upgrade outdated to pull your changes? Unfortunately, that did not seem
to do the trick for me..
That’s correct unless your using kencu’s universal repository then it
won't. Kencu’s also not rebased it to head recently probably busy.
I’m not using kencu’s universal repository, instead I setup a local port
repository that contains only my custom Portfiles that’s set above the
official listing to ensure mine are used, unlike the current instructions
I’m still injecting {{{LDFLAGS=-Wl,-w}}} via macports-base when forcing an
SDK version.
I’ve looked over the provided log (it’s not a full log) and I see no
reason for it fail as it’s just warning about depreciated code, as that
port is using {{{gmake}}} and part of the cmake group it could be
suffering from the same issue as {{{cmake}}} so you could try editing the
{{{chromaprint}}} Portfile and adding
{{{
# suppress a linker warning when building 32bit on Mojave that makes
cmake barf
if {${os.arch} eq "i386" && ${os.major} == 18} {
configure.env-append "LDFLAGS=-Wl,-w"
}
}}}
Or just {{{configure.env-append "LDFLAGS=-Wl,-w"}}} if the warning are
seen as errors one of the two should resolve the issue your having.
--
Ticket URL: <https://trac.macports.org/ticket/56991#comment:107>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list