Heads up: poppler won't build
ryandesign at macports.org
Tue Feb 26 13:29:30 UTC 2019
On Feb 24, 2019, at 19:24, Bill Cole wrote:
> On 24 Feb 2019, at 18:55, Dave Horsfall wrote:
>> Sierra 10.12.6 + latest security updates, MacPorts 2.5.4.
>> Doing my regular Monday "port upgrade outdated", and...
>> ---> Computing dependencies for poppler
>> ---> Configuring poppler
>> Error: poppler cannot be built while another version of poppler is active.
>> Error: Please forcibly deactivate the existing copy of poppler, e.g. by running:
>> Error: sudo port -f deactivate poppler
>> Error: Then try again.
>> Error: Failed to configure poppler: poppler is active
>> ozzie:~ dave$ sudo port -f deactivate poppler
>> ---> Unable to deactivate poppler @0.72.0_0, the following ports depend on it:
>> ---> gimp2 @2.10.8_3+python27
>> Warning: Deactivate forced. Proceeding despite dependencies.
>> ---> Deactivating poppler @0.72.0_0
>> ---> Cleaning poppler
>> Hmmm... Proceed regardless:
>> ozzie:~ dave$ sudo port -p upgrade outdated
>> Nothing to upgrade.
> Because after you deactivate a port, an "upgrade" isn't possible.
That's not true, however a port is not considered outdated unless it is active. You can still upgrade it by explicitly naming it:
sudo port upgrade poppler
More information about the macports-users