[Slackbuilds-users] google-chrome for 13.37

occam occam at internode.on.net
Tue May 3 07:18:07 UTC 2011

On Tue, 3 May 2011 08:47:13 Phillip Warner wrote:
> --- On Mon, 5/2/11, Carlos Corbacho <carlos at strangeworlds.co.uk> wrote:
> > Yes - you need
> > extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz
> > 
> > from your local, friendly Slackware mirror.
> A *really* important thing to note, however, is that the Chrome Slackware
> slackbuild and the SBo slackbuild are NOT the same.  The Slackware one
> specifies certain seamonkey header files to link to while the SBo
> slackbuild tries to link to any seamonkey libs that aren't already in the
> chrome sources.  This is a problem with pam since the SBo package will
> attempt to link to a pam seamonkey header that does not exist (The
> slackware package in /extra puts the header in the chrome program
> directory).
> Therefore, if you continue using the SBo chrome slackbuild for convenience
> (via sbopkg), you need to make sure it does not try to link the pam lib. 
> Otherwise, you will need to manually remove it and relink to the correct
> directory (or just reinstall the google-pam slackware package).

Thanks for the help - I am now running Chrome without any problems. The SBo 
scripts are a great resource; I used to do everything manually - including 
compiling and installing new versions of KDE but SBo scripts are so much 

More information about the SlackBuilds-users mailing list