Hi, Poppler and xpdf conflict with each other in some executable names. < godel:~ > port activate poppler @0.6_0 ---> Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation. However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem? Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass
Le 07-10-01 à 08:40, Stefan Bruda a écrit :
Hi,
Poppler and xpdf conflict with each other in some executable names.
< godel:~ > port activate poppler @0.6_0 ---> Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation.
However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem?
xpdf has a variant for this case port install xpdf +with_poppler yves
Yves de Champlain wrote:
Poppler and xpdf conflict with each other in some executable names.
< godel:~ > port activate poppler @0.6_0 ---> Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation.
However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem?
xpdf has a variant for this case
port install xpdf +with_poppler
Thank you very much, that does it nicely. Stefan
participants (2)
-
Stefan Bruda
-
Yves de Champlain