-   Slackware (
-   -   PKG CONFIG PATH Adjustment (

alkahest 04-13-2013 03:19 PM

Hello Everybody,

I am attempting to install a Google Chrome Slackbuild on Slackware 14.

I tried to install a Chrome RPM from the official website to no avail, so now I am attempting the Slackbuild route.

It has been brought to my attention that Google Chrome has runtime dependencies on ORBit and GConf. So I am trying to install builds for those two.

I have successfully unpacked and installed ORBit2, using 'tar xzvf' and 'sudo ORBit2.SlackBuild'.

I attempted the same steps for GConf. But when I ran 'sudo GConf.SlackBuild', I got the error 'No package ORBit-2.0' found'.

Now, the problem is that I installed 'ORBit2', not 'ORBit-2.0'. My guess is that this naming discrepancy is the reason that I can't install GConf.

So how do I change the names so that GConf will install?

Konsole says I should "consider adjusting the PKG_CONFIG_PATH environmental variable if you installed software in a non-standard prefix". It also suggests that I can "set the environmental variables DEPENDENT_CFLAGS and DEPENDENT_LIBS" to avoid the need to call pkg-config.

But I am not sure how to do these things, or what they mean.

Again, how can I change ORBit2 to ORBit-2.0 so that I can install GConf?

solarfields 04-13-2013 03:31 PM

GConf is part of Slackware. Where did you get the google-chrome Slackbuild from?

If you want to install google chrome, you can find a SlackBuild, instructions and dependencies in /extra:

Read the README there!
Also, read the HOWTO section at SBo in case you are not familiar with using SLackBuilds:

Alien Bob 04-13-2013 03:32 PM

If you are really running Slackware 14 you should already have GConf and Orbit installed.
Please read the Google Chrome README in Slackware 14's "extra" directory if you want to know how install Chrome and its dependency, the PAM library:


jprzybylski 04-13-2013 03:38 PM

Hi! GConf is already installed on Slackware 14.0, I believe.

Have you tried following the directions here?

solarfields 04-13-2013 03:39 PM

Eric, I think you may be mistaken about Orbit? Mine is installed from SBo on Slackware 14.0.

alkahest 04-13-2013 03:43 PM


I got the Slackbuild from I realize that this may not have been the best idea, but I am not really familiar with the FTP repository yet.

How do I download the files from If I click on the files, they just open in my browser.

solarfields 04-13-2013 03:44 PM

right click -> Save as... ? ;)

alkahest 04-13-2013 04:10 PM

Okay, I have the .deb and the .SlackBuild in the same directory (/downloads)

I have tried the following, all as Root:

Running '/downloads/google-chrome.SlackBuild' returns 'Permission Denied'

Running 'cd /downloads' and then 'google-chrome.SlackBuild' returns 'google-chrome.SlackBuild: Command Not Found'

Running 'su /downloads/google-chrome.SlackBuild' returns 'Unknown id: /downloads/google-chrome.SlackBuild'

Running 'cd /downloads' and then 'su google-chrome.SlackBuild' or 'su /google-chrome.SlackBuild' or any combination of slashes, gives "Unknown id" as well.

What am I doing wrong?

jprzybylski 04-13-2013 04:13 PM


chmod +x google-chrome.SlackBuild

or you can just use

sh google-chrome.SlackBuild


alkahest 04-13-2013 04:37 PM

Thanks everyone!

I am now typing this response to you from Chrome.

This has been a great learning experience for me.

May the schwartz be with you

ruario 04-23-2013 12:47 PM

If you want an easy way to keep Chrome up to date, you can run this script from time to time. It'll check what is the latest stable version of Chrome is and compare it to the version you have installed. If your version is different (or you don't have Chrome installed) it will automatically download the new version and repack into Slackware format. Otherwise it will just report that you are up to date. As a bonus you can run the script as a regular user (since it is able to make valid Slackware packages with root owned files even when not run as root).

P.S. If you want the same for Opera or Firefox I have similar scripts for them. It may not be immediately obvious why I have a Firefox script given that Slackware ships Firefox and provides updates but it can be handy as you can use it to track ESR releases (set FFESR=y) or if there is a delay in Pat updating the regular build. All of these scripts are doing binary repacks, not building from source. This has the advantage of being very fast and meaning you can take advantage of compilation optimisations that the upstream browser makers employ, e.g. PGO.

ponce 04-23-2013 03:39 PM

firefox in slackware64 is built with PGO too since january (and the slackbuild supports building of esr releases) ;)

ruario 04-23-2013 03:57 PM


Originally Posted by ponce (Post 4937500)
firefox in slackware64 is built with PGO too since january (and the slackbuild supports building of esr releases) ;)

Still I can instant upgrade as soon as the update is available, with no delay waiting for packages from Pat. Also no need to 'build' ESR with PGO, which would use a lot of time and resources. Mozilla already provide nice "official" binaries. I'd prefer just use them and get instant upgrades (SBo is currently 4 versions back 17.0.1 instead of 17.0.5 meaning it is lacking security fixes).

The other benefit is that the script not only automatically downloads the binary and makes the Slackware packages, it does the checking for updates and it'll do all this without having to be root. You only need to switch to root to install any packages that were made, if updates are found.

ponce 04-23-2013 04:25 PM

I agree with you, the script is very useful. :)
I just wanted to clarify that we have PGO (and esr support) in the official slackware package.

ruario 04-23-2013 04:32 PM


Originally Posted by ruario (Post 4937512)
SBo is currently 4 versions back 17.0.1 instead of 17.0.5 meaning it is lacking security fixes.

Including 19(!) critical security fixes:

Yes, I know I could tweak the version of the SlackBuild on ESR but this is manual. Additionally as previously stated it is resource and time consuming to compile Firefox ESR with PGO, it is far quicker and easier to repackage the binaries. And it is easier with the script to keep track of updates.

This is also true with my latest-chrome script. I imagine a large number of people used the SlackBuild in /extra once or twice and then never gave much thought to tracking new versions (which are very much needed to remain secure). It is actually quite annoying that with Chrome you cannot easily keep track what the latest version actually is for users of non rpm/deb distros.

At least with Opera you get a popup dialog telling you when a new release is out (from within the browser itself), thus helping to keep the user aware if he/she is not secure.

All times are GMT -5. The time now is 11:24 PM.