[MacPorts] #57225: testdisk @7.0 build failure after update of libewf: error: use of undeclared identifier 'LIBEWF_OPEN_READ_WRITE'
MacPorts
noreply at macports.org
Thu Oct 4 15:52:40 UTC 2018
#57225: testdisk @7.0 build failure after update of libewf: error: use of
undeclared identifier 'LIBEWF_OPEN_READ_WRITE'
-------------------------+--------------------
Reporter: Klaskviker | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: testdisk |
-------------------------+--------------------
Comment (by Klaskviker):
Replying to [comment:10 kencu]:
> So, Klashviker, first of all, sorry for breaking your port. I should
have handled this differently, making a `libewf-devel` port and then
assessing breakage. I may still do that.
>
> But for right now, please
> {{{
> sudo port -v activate libewf
> }}}
> and when it shows you the list of installed versions, hit the number
that corresponds to the previous version. It will stay like that until you
change it, and then you'll be back where you were. You may not even need
to rebuild `testdisk` after that, as things will just be "as they were".
>
> Hopefully RJVB or I can fix `testdisk` to work against the current
`libewf`. Sounds like `testdisk` is actively maintained, but I can't find
a bug tracker or a source repo for it at this time.
I can't restore a previous version of libewf, because I deleted them all
when trying to fix the issue ((
Could you please restore the old version of libewf in the main port and
move the current version to libewf-devel? Because it is possible that
other ports will be affected.
--
Ticket URL: <https://trac.macports.org/ticket/57225#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list