[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 10:43:44 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 RJVB):
Replying to [comment:6 kencu]:
That wasn't asking me - next time CC' me first and then add a comment why
so I get that in my mail ;)
Anyway, try this in the file(s) that requires the undefined token:
{{{
#define LIBEWF_OPEN_READ_WRITE
(LIBEWF_ACCESS_FLAG_READ|LIBEWF_ACCESS_FLAG_WRITE)
}}}
or activate the previous version of libewf via `port activate libewf` to
check the actual definition of LIBEWF_OPEN_READ_WRITE. My hunch is though
that you can simply set both read and write flags to open something in
read+write mode.
If the trick above works we can consider adding it to libewf/definitions.h
to avoid having to patch all dependents (though in theory the dependent
port maintainers should do exactly that...)
--
Ticket URL: <https://trac.macports.org/ticket/57225#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list