poppler: error: The pkg-config script could not be found or is too old.

[precioso.p.gabrillo@…]

Trying to install octave by following the wiki instructions:

sudo port install octave-devel +atlas+docs

had errors so after querying the forum, found recommendations to install dependencies first:

sudo port clean octave
sudo port install {dependencies listed from the log...}

then ran into this error that cannot find a solution:

Error: org.macports.configure for port poppler returned: configure failure: command execution failed
Error: Failed to install poppler
Please see the log file for port poppler for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/main.log
Error: The following dependencies were not installed: texlive-basic texlive-bin poppler xorg-libXp texlive-documentation-base texlive-bin-extra dvipng latexmk texlive-latex pdfjam texlive-latex-recommended pgf texlive-context texlive-fonts-recommended texlive-math-extra texlive-metapost texlive-xetex texlive-generic-recommended texlive-documentation-english texlive-fontutils lcdf-typetools ps2eps texlive-lang-czechslovak texlive-lang-dutch texlive-lang-english texlive-lang-french texlive-lang-german texlive-lang-italian texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish texlive-luatex
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port texlive failed

attach is the log. Using Mac OSX 10.6.8 with XCode 3.2.6

[cooljeanius (Eric Gallager)]

This is actually an issue with poppler, not octave. The relevant part of the log is:

:info:configure checking for LIBCURL... no
:info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/work/poppler-0.22.2':
:info:configure configure: error: The pkg-config script could not be found or is too old.  Make sure it
:info:configure is in your PATH or set the PKG_CONFIG environment variable to the full
:info:configure path to pkg-config.
:info:configure 
:info:configure Alternatively, you may set the environment variables LIBCURL_CFLAGS
:info:configure and LIBCURL_LIBS to avoid the need to call pkg-config.
:info:configure See the pkg-config man page for more details.
:info:configure 
:info:configure To get pkg-config, see <http://pkg-config.freedesktop.org/>.
:info:configure See `config.log' for more details
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_poppler/poppler/work/poppler-0.22.2" && ./configure --prefix=/opt/local --disable-introspection --disable-poppler-qt4 --disable-gtk-test --disable-silent-rules --enable-xpdf-headers --enable-zlib --enable-libcurl --enable-poppler-glib --mandir=/opt/local/share/man --x-includes=/opt/local/include --x-libraries=/opt/local/lib 

What does port installed curl return for you? How about port installed pkgconfig?

[precioso.p.gabrillo@…]

Replying to egall@…:

What does port installed curl return for you? How about port installed pkgconfig?

Hi,

This is the info:

The following ports are currently installed:
  curl @7.29.0_1+ssl (active)

The following ports are currently installed:
  pkgconfig @0.28_0 (active)

thanks.

[ryandesign (Ryan Carsten Schmidt)]

Please use WikiFormatting.

[ryandesign (Ryan Carsten Schmidt)]

So what happens when you try to run the pkg-config program yourself? Try:

pkg-config --version

[precioso.p.gabrillo@…]

Replying to ryandesign@…:

So what happens when you try to run the pkg-config program yourself? Try:

pkg-config --version

This is what I got:

-sh: pkg-config: command not found

[ryandesign (Ryan Carsten Schmidt)]

What about:

port contents pkgconfig

[precioso.p.gabrillo@…]

Replying to ryandesign@…:

What about:

port contents pkgconfig

The details:

Port pkgconfig contains:
  /opt/local/bin/pkg-config
  /opt/local/lib/pkgconfig/.turd_pkgconfig
  /opt/local/share/aclocal/pkg.m4
  /opt/local/share/doc/pkgconfig/AUTHORS
  /opt/local/share/doc/pkgconfig/COPYING
  /opt/local/share/doc/pkgconfig/NEWS
  /opt/local/share/doc/pkgconfig/README
  /opt/local/share/doc/pkgconfig/pkg-config-guide.html
  /opt/local/share/man/man1/pkg-config.1.gz
  /opt/local/share/pkgconfig/.turd_pkgconfig

[ryandesign (Ryan Carsten Schmidt)]

So MacPorts says pkg-config should be there, but it seems not to be. Presumably some outside force deleted it without MacPorts' knowledge. That's disconcerting but let's see if we can get it back with:

sudo port -f deactivate pkgconfig
sudo port activate pkgconfig

[cooljeanius (Eric Gallager)]

Replying to ryandesign@…:

So MacPorts says pkg-config should be there, but it seems not to be. Presumably some outside force deleted it without MacPorts' knowledge.

Either that or somehow /opt/local/bin got removed from OP's $PATH. OP, could you post the results of the following commands please?

• echo $PATH (using "env" would also work for this)
• stat /opt/local/bin/pkg-config
• which -a pkg-config (Although based on your response in comment:5 I don't expect this one to actually return anything...)

[cooljeanius (Eric Gallager)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

The value of $PATH on the command line is irrelevant; MacPorts does not use it; instead, MacPorts uses binpath as set in macports.conf. Certainly, removing /opt/local/bin from binpath would be a user error, and as it says in macports.conf, "Customizing binpath is unsupported and is intended for advanced users only", so let's assume the user didn't do that.

[precioso.p.gabrillo@…]

Got as far as octave install but ran into another problem. This is what I did:

sudo port -f deactivate pkgconfig
Password:
--->  Deactivating pkgconfig @0.28_0
--->  Cleaning pkgconfig

sudo port activate pkgconfig
--->  Computing dependencies for pkgconfig
--->  Activating pkgconfig @0.28_0
--->  Cleaning pkgconfig

then:

echo $PATH
/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/git/bin:/usr/X11/bin

stat /opt/local/bin/pkg-config
stat: /opt/local/bin/pkg-config: stat: No such file or directory

which -a pkg-config  <---- returned prompt, no return

I then type the following:

sudo port selfupdate
sudo port clean octave
sudo port clean <the list of dependencies I tried to install firts>
sudo port install <those same list of dependencies>

It seems activating pckconfig may have done the trick as it ran past poppler. However, a lot of warnings were listed at the end but the final statement showed:

--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

I then use the installation instruction from the wiki: sudo port install octave-devel +atlas+docs

and got this last part of the error:

Error: org.macports.build for port metis returned: command execution failed
Please see the log file for port metis for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_metis/metis/main.log
Error: Unable to upgrade port: 1
Error: Unable to execute port: upgrade metis failed

I will try to attach 2 files: from the screen dump at the end of the dependency installation and the metis main.log.

[precioso.p.gabrillo@…]

port install

[precioso.p.gabrillo@…]

metis

[precioso.p.gabrillo@…]

Attachment added.

The file warnings.rtf is a rich text format of a screen dump after installing the dependencies. Main.2.log is from the metis error log.

thanks.

[cooljeanius (Eric Gallager)]

Replying to ryandesign@…:

The value of $PATH on the command line is irrelevant; MacPorts does not use it; instead, MacPorts uses binpath as set in macports.conf. Certainly, removing /opt/local/bin from binpath would be a user error, and as it says in macports.conf, "Customizing binpath is unsupported and is intended for advanced users only", so let's assume the user didn't do that.

I was referring to when the user tried running pkg-config manually in comment:5 above. I'm assuming that command was run as the user's regular account, and not as the macports user.

[cooljeanius (Eric Gallager)]

Replying to precioso.p.gabrillo@…:

Attachment added.

The file warnings.rtf is a rich text format of a screen dump after installing the dependencies. Main.2.log is from the metis error log.

thanks.

This looks like a different error, I'd recommend opening a separate ticket for that.

[precioso.p.gabrillo@…]

Replying to egall@…:

Replying to ryandesign@…:

The value of $PATH on the command line is irrelevant; MacPorts does not use it; instead, MacPorts uses binpath as set in macports.conf. Certainly, removing /opt/local/bin from binpath would be a user error, and as it says in macports.conf, "Customizing binpath is unsupported and is intended for advanced users only", so let's assume the user didn't do that.

I was referring to when the user tried running pkg-config manually in comment:5 above. I'm assuming that command was run as the user's regular account, and not as the macports user.

I tried doing this:

port pkg-config --version
Error: Unrecognized action "port pkg-config"

[precioso.p.gabrillo@…]

Replying to egall@…:

Replying to precioso.p.gabrillo@…:

Attachment added.

The file warnings.rtf is a rich text format of a screen dump after installing the dependencies. Main.2.log is from the metis error log.

thanks.

This looks like a different error, I'd recommend opening a separate ticket for that.

Ticket created. Thanks.

[cooljeanius (Eric Gallager)]

Replying to precioso.p.gabrillo@…:

Replying to egall@…:

This looks like a different error, I'd recommend opening a separate ticket for that.

Ticket created. Thanks.

(This is #38775, for other's reference)

[ryandesign (Ryan Carsten Schmidt)]

I asked you to deactivate and re-activate the pkgconfig port to see if that would bring the pkg-config program back. You showed that you deactivated and re-activated the pkgconfig port, and then showed the output of stat and which commands which showed that the pkg-config program still did not exist.

Does the pkg-config program exist now? Please look in /opt/local/bin. If it does not exist, then we need to fix that before trying anything else, and if deactivating and re-activating did not work, then the next thing to try is rebuilding the port with:

sudo port clean pkgconfig
sudo port -n upgrade --force pkgconfig

[precioso.p.gabrillo@…]

Replying to ryandesign@…:

I asked you to deactivate and re-activate the pkgconfig port to see if that would bring the pkg-config program back. You showed that you deactivated and re-activated the pkgconfig port, and then showed the output of stat and which commands which showed that the pkg-config program still did not exist.

Does the pkg-config program exist now? Please look in /opt/local/bin. If it does not exist, then we need to fix that before trying anything else, and if deactivating and re-activating did not work, then the next thing to try is rebuilding the port with:

sudo port clean pkgconfig
sudo port -n upgrade --force pkgconfig

This is what I have:

/opt/local/bin

-rwxr-xr-x  1 root  admin  597864 Apr  7 16:19 pkg-config

pkg-config: Mach-O 64-bit executable x86_64

I do not have pkgconfig, just pkg-config. Are they different? Have not tried the last 2 commands since pkg-config exists, I think.

[ryandesign (Ryan Carsten Schmidt)]

pkgconfig is the name of the port. pkg-config is the name of the program installed by that port. Ok, so if the pkg-config program now exists, then all is well. There's still the mystery about why the program disappeared, and if you can't explain it, then it's possible that whatever deleted the pkg-config program also deleted parts of other ports, and as you discover such problems, you could deactivate and reactivate those ports as well to fix it.