[MacPorts] #69236: cryfs @0.11.4: error: expected unqualified-id
MacPorts
noreply at macports.org
Fri Feb 16 05:18:21 UTC 2024
#69236: cryfs @0.11.4: error: expected unqualified-id
-------------------------+----------------------
Reporter: ryandesign | Owner: jolan78
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.9.0
Resolution: | Keywords:
Port: cryfs |
-------------------------+----------------------
Comment (by ryandesign):
Replying to [comment:2 jolan78]:
> No reason other than I was under the impression boost portgroup was
selecting the best version for the system it was built on.
It picks a version that was probably current at the time the portgroup was
created. It cannot be changed in the portgroup without breaking all ports
that do not specify a boost version. Therefore, all ports that use the
portgroup should specify a boost version. Probably somebody should go
through all ports that do not specify a boost version and specify the one
currently in the portgroup, then change the portgroup so that it no longer
specifies a default, forcing all new ports to specify the desired version.
New boost versions routinely change or remove functionality, making them
not backward-compatible. That's why we have several boost versions in
MacPorts. It's not about which boost version is best for the current
system; it's about what boost version this particular port's software was
written to require.
> I tried the versions of boost >1.76 but none of them works with cryfs.
Ok, not working with later versions is a valid reason for sticking with an
old one. But it looks like this project is actively maintained, so if they
don't work with newer boost versions, they may be open to a bug report
about that.
> cryfs references 1.79.0 in the cmake file I use so at least 1.78 should
work.
It looks like the commit that changes their boost version from 1.75 to
1.79 will be included in cryfs 0.12.0, in other words not yet.
Like all boost versions, boost 1.78 and 1.79 are different. A program
working with one of them is no guarantee that it will work with the other
one.
Some boost versions have already been deleted from MacPorts in a possibly
premature effort to clean up and streamline. We don't have boost 1.79 or
1.80 in MacPorts anymore but we do have 1.78 and 1.81. Hopefully cryfs
0.12.0 works with one of those. If not, we could resurrect the port for
boost 1.79.
> I may dig into this later, but as I don't have access to a 10.7 system,
I would have not guarantee it would fix this issue.
If you can update to a later version of boost when cryfs 0.12.0 is
released, then we can re-check the buildbot logs and see if that has fixed
the failure on Mac OS X 10.7.
--
Ticket URL: <https://trac.macports.org/ticket/69236#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list