LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Google-chrome Slackbuild under multilib (http://www.linuxquestions.org/questions/slackware-14/google-chrome-slackbuild-under-multilib-800894/)

damgar 04-08-2010 07:05 PM

Google-chrome Slackbuild under multilib
 
I'm quite confused by this slackbuild. I installed multilib just for better flash support and while things work well enough for FF I prefer google-chrome. So the google-chrome slackbuild doesn't actually compile anything so in the slackbuild I used ARCH=i386. Which may have been wrong. I also had to compile Gconf and ORBit2. According to Alien Bob's directions I ran the script to change my shell for compiling 32 bit binaries, then I edited the Slackbuilds for LIBSDIRSUFFIX="" but left the ARCH=-x86_64. Everything built and installed, but when I tried to run google-chrome I get
Code:

bash-4.1# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libgconf-2.so.4: wrong ELF class: ELFCLASS64

Ultimately I got sick of doing the back and forth so I just grabbed 32 bit Orbit and Gconf from the Salix repositories (those repos REALLY ARE NICE!) and everything is working now. but I feel like a cheater and I'd like to know if I screwed up something building the dependenies, or if I screwed up the Google-chrome Slackbuild. Any thoughts

slackass 04-08-2010 07:29 PM

I'm running the most recent Slack64-C Multilib and I just ran off Orbit2, Gconf & Chrome with sbopkg and it worked perfect.
seamonkey-solibs from Slackware's patches is also listed as a dep at SlackBuilds.

ARCH=${ARCH:-i386}
should be changed to:
ARCH=${ARCH:-x86_64}

hope this helps

damgar 04-08-2010 08:16 PM

Quote:

Originally Posted by slackass (Post 3929256)
I'm running the most recent Slack64-C Multilib and I just ran off Orbit2, Gconf & Chrome with sbopkg and it worked perfect.
seamonkey-solibs from Slackware's patches is also listed as a dep at SlackBuilds.

ARCH=${ARCH:-i386}
should be changed to:
ARCH=${ARCH:-x86_64}

hope this helps

Is that 32bit chrome or 64 that you built. Also does flash work in your new google chrome? This "bundled internal flash plugin" thing just isn't working for me.

slackass 04-08-2010 08:53 PM

It's the amd64 version.
It worked for a few minuets but now it freezes every time I open a video... :-(

slackass 04-08-2010 08:59 PM

Just did a re-boot & now flash works again. ... ???

damgar 04-08-2010 09:20 PM

Yeah I have no problems doing the 64 bit chrome (which supposedly doesn't include the internal flash) it's the 32 bit chrome and it's dependencies on a multilib system that are/have been giving me fits. I managed to get ggogle chrome 5.0.371.0 working and flash even worked ONCE. But google has decided that it's smart to bundle flash with chrome which seems to ignore the perfectly good flash plugin (perfect and good are both used relatively here) in .../mozilla/plugins/ and I can't make it work. In addition I've found that I can't even use gmail oddly enough because ssl is broken. I'm getting rather irritated by the whole thing. I was really liking google-chrome, and even though this is probably something I'm missing that's breaking 32 bit chrome in multilib my hatred for flash and the time I'm wasting JUST TO GET DECENT YOUTUBE (sorry, but this is ridiculous and adobe can rot in hell) is bleeding over to chrome since they seem to now be in bed together. Sorry for the rant, but I have a rather time consuming sledgehammer of an answer brewing and have time and anger to waste as a result! :)


All times are GMT -5. The time now is 10:09 PM.