On building poppler

Ruben Di Battista rubendibattista at gmail.com
Sun Apr 12 21:19:22 UTC 2020

Hi Dave, 

That is standard practice. I don’t know the real reason for it, didn’t bother to investigate, but you just need to follow what is written there: that is deactivating Poppler before upgrading it. 

`sudo port -f deactivate popper`
`sudo port upgrade popper`.

I guess it is a safety measure to avoid breaking running programs? I guess.  Here: https://trac.macports.org/ticket/58574 there’s probably the long answer to that :)

-.     .´  |∞∞∞∞
  ',  ;    |∞∞∞∞∞∞
    ˜˜     |∞∞∞∞∞∞∞∞∞ RdB
    ,.,    |∞∞∞∞∞∞
  .'   '.  |∞∞∞∞
-'       `’


On 12 April 2020 at 23:02:11, Dave Horsfall (dave at horsfall.org) wrote:

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: 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20200412/3924a3f1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP using AMPGpg
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20200412/3924a3f1/attachment.sig>

More information about the macports-users mailing list