Build Chrome on Slackware-current fail--No package 'nss' found

grissiom · 09-04-2008, 10:13 AM

When I try to build Google Chrome on slackware-current, it fail on seeking package 'nss':

Code:

grissiom@gri:/usr/local/src/chromium/src/chrome$ ../third_party/scons/scons.py Hammer
scons: Reading SConscript files ...
Package nss was not found in the pkg-config search path.
Perhaps you should add the directory containing `nss.pc'
to the PKG_CONFIG_PATH environment variable
No package 'nss' found
OSError: 'pkg-config --cflags --libs nss' exited 1:
  File "/usr/local/src/chromium/src/chrome/SConstruct", line 7:
    exports=['build_component'])
  File "/usr/local/src/chromium/src/third_party/scons/scons-local-0.98.3/SCons/Script/SConscript.py", line 596:
    return apply(method, args, kw)
  File "/usr/local/src/chromium/src/third_party/scons/scons-local-0.98.3/SCons/Script/SConscript.py", line 533:
    return apply(_SConscript, [self.fs,] + files, subst_kw)
  File "/usr/local/src/chromium/src/third_party/scons/scons-local-0.98.3/SCons/Script/SConscript.py", line 256:
    exec _file_ in call_stack[-1].globals
  File "/usr/local/src/chromium/src/build/SConscript.main", line 371:
    env.ParseConfig('pkg-config --cflags --libs nss')
  File "/usr/local/src/chromium/src/third_party/scons/scons-local-0.98.3/SCons/Environment.py", line 1371:
    return function(self, self.backtick(command))
  File "/usr/local/src/chromium/src/third_party/scons/scons-local-0.98.3/SCons/Environment.py", line 549:
    raise OSError("'%s' exited %d" % (command, status))

I did some search on slackbuilds.org and packages.slackware.it but hardly to find any package meets the demand. The mozilla-firefox-3.0.1-i686-1 package contain usr/lib/firefox-3.0.1/libnss3.so but could not reslove the problem. Does anyone have any idea? Thanks in advance

crashmeister · 09-04-2008, 10:27 AM

Chrome doesn't work on Linux.At most it will build some modules and check them.

grissiom · 09-04-2008, 10:37 AM

Quote:

Originally Posted by crashmeister

Chrome doesn't work on Linux.At most it will build some modules and check them.

Hmm,,,,sad news....;(

Crashbox · 09-04-2008, 11:23 AM

actually, they have 'released' Chrome for linux:

arstechnica.com

or go right to the source:

Chromium

As for building it, I haven't tried yet. I'll check back if/when I do.

crashmeister · 09-04-2008, 11:47 AM

Quoting the build instructions:

Note: There is no working Chromium-based browser on Linux. Although many Chromium submodules build under Linux and a few unit tests pass, all that runs is a command-line "all tests pass" executable.

It's in a big red box on top of the page.

Road_map · 09-04-2008, 12:01 PM

1. Take the build files from here
2. Replace nss-3.11.4-with-nspr-4.6.4.tar.gz with nss-3.12-with-nspr-4.7.tar.gzfrom here
3. Modify mozilla-nss.SlackBuild:

Code:

(...)
VERSION=${VERSION:-3.12}
(...)
NSPR=4.7
(...)

4. Build the package
5. Install the package
6. Rename /usr/lib/pkgconfig/mozilla-nss.pc to /usr/lib/pkgconfig/nss.pc -- I forgot when exactly is needed this step, I think right before run

Code:

$ ../third_party/scons/scons.py Hammer

There is no functional build for Linux.

grissiom · 09-04-2008, 10:17 PM

Thanks Road_map, your post rocks~

But just as crashmeister said, There is no working Chromium-based browser on Linux. Chrome won't build on my box due to a v8 compile error... (src version 1754) Is Google truely Linux-friendly?

hitest · 09-04-2008, 10:53 PM

I'm very-much looking forward to a Linux version of Chrome.....heh....I don't do Winders.

Road_map · 09-05-2008, 10:09 AM

Quote:

Originally Posted by grissiom

Chrome won't build on my box due to a v8 compile error... (src version 1754)

After Build Instructions (Linux):

Code:

$mkdir ~/chromium
$ cd chromium
$ svn co http://src.chromium.org/svn/trunk/depot_tools/linux depot_tools
$ export LANG=C
$ ./depot_tools/gclient config http://src.chromium.org/svn/trunk/src
$ ./depot_tools/gclient sync
$ cd chromium/src/chrome
$ ../third_party/scons/scons.py Hammer

And the result is

Quote:

scons: done building targets.

Then, there are 2 tests (in ~/chromium/src/chrome/Hammer):

Code:

$ ./base_unittests
$ ./net_unittests

That is all, till now:

Quote:

[----------] Global test environment tear-down
[==========] 188 tests from 40 test cases ran.
[ PASSED ] 188 tests.
...
[----------] Global test environment tear-down
[==========] 174 tests from 17 test cases ran.
[ PASSED ] 174 tests.

grissiom · 09-05-2008, 09:10 PM

Quote:

Originally Posted by Road_map

After Build Instructions (Linux):

Code:

$mkdir ~/chromium
$ cd chromium
$ svn co http://src.chromium.org/svn/trunk/depot_tools/linux depot_tools
$ export LANG=C
$ ./depot_tools/gclient config http://src.chromium.org/svn/trunk/src
$ ./depot_tools/gclient sync
$ cd chromium/src/chrome
$ ../third_party/scons/scons.py Hammer

And the result is

Then, there are 2 tests (in ~/chromium/src/chrome/Hammer):

Code:

$ ./base_unittests
$ ./net_unittests

That is all, till now:

Hmm, that sounds exciting~ Is there only unittests but not chrome binary?

MS3FGX · 09-05-2008, 10:01 PM

Quote:

Is Google truely Linux-friendly?

This is the very first public release of a BETA product. It isn't surprising that they have only targeted the largest userbase for the test so they can collect the most amount of feedback possible (while targeting only one platform for the sake of simplicity).

Once the codebase is refined, the OS X and Linux specific changes will be put in and official versions of Chrome for those platforms can be released. As it is, we can clearly see that their codebase was at least designed from the start to be portable and Unix-compatible; which is already more than a lot of other developers are willing to go. Google is investing heavily in Linux (I.E. Android) and they are certainly progressing with an eye towards multiplatform applications.

grissiom · 09-06-2008, 12:26 AM

Quote:

Originally Posted by MS3FGX

This is the very first public release of a BETA product. It isn't surprising that they have only targeted the largest userbase for the test so they can collect the most amount of feedback possible (while targeting only one platform for the sake of simplicity).

Once the codebase is refined, the OS X and Linux specific changes will be put in and official versions of Chrome for those platforms can be released. As it is, we can clearly see that their codebase was at least designed from the start to be portable and Unix-compatible; which is already more than a lot of other developers are willing to go. Google is investing heavily in Linux (I.E. Android) and they are certainly progressing with an eye towards multiplatform applications.

Yes, you said the truth. Maybe I'm too hasted

crashmeister · 09-06-2008, 04:43 AM

They are working on Mac and Linux versions.http://googlemac.blogspot.com/2008/0...priorities.htm