[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: www/seamonkey build stopped by failure to find nonexistent packages
> Look in the config.log file in the work directory, perhaps it has more
> details which of the dependencies is/are not found.
> Thomas (Klausner)
I found build/config.log in the work directory (work899.amd64).
DEBUG: configure:15477: checking for gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0
DEBUG: configure: error: Library requirements (gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0 gdk-x11-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a
nonstandard prefix so pkg-config can find them.
ERROR: old-configure failed
*** Error code 1
That was in the build.log and also included the end of build/config.log
So do I need to export PKG_CONFIG_PATH=/usr/pkg/lib/pkgconfig/ or prefix the build command with env PKG_CONFIG_PATH=/usr/pkg/lib/pkgconfig/ ?
Why does this happen when building www/seamonkey and not other packages?
Just for comparison, I looked at /usr/local/lib in FreeBSD and there was nothing comparable to the pkgconfig subdirectory.
I was successful installing www/otter-browser and www/firefox last night (surprise after www/midori failed) but haven't run them yet.
Netsurf and Dillo seem less sturdy/capable.
One peculiarity is that X wouldn't start on i386 but started on amd64.
I never used Otter or Opera browser and am curious how Otter works, not to forget Firefox.
Main Index |
Thread Index |