[chromium-dev] Re: cryptoht.h not found
Hi, can you try running, gclient runhooks --force, gclient sync --force, clobber (delete build directory), and build again. On Sun, Apr 19, 2009 at 5:59 PM, Hassan wrote: > > Hello, > > I can't seem to compile chrome on my linux machine. It's complaining > that it couldn't find cryptoht.h (see below). After some digging, I > noticed g++ is possibly missing a -I/usr/include/nss flag since it > seems that cryptoht.h lives in /usr/include/nss/: > > has...@hassan-desktop:~/devel/chromium/src/build$ locate cryptoht.h > /usr/include/nss/cryptoht.h > > Could this be the reason? If so, what is the correct way of including > that flag to g++? > > Thanks, > - HR > > Here is the error message that I'm getting when compiling: > has...@hassan-desktop:~/devel/chromium/src/build$ ../../depot_tools/ > hammer app --verbose > scons: Reading SConscript files ... > scons: done reading SConscript files. > scons: Building targets ... > cd /home/hassan/devel/chromium/src/base && ../chrome/tools/build/linux/ > version.sh file_version_info_linux.h.version /home/hassan/devel/ > chromium/src/sconsbuild/Debug/obj/global_intermediate/base/ > file_version_info_linux.h > g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ > crypto/signature_verifier_nss.o -c -m32 -pthread -march=pentium4 -fno- > exceptions -msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/ > gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/ > include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/ > lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 - > I/usr/include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - > DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ > sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ > devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ > devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - > I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ > hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ > chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ > global_intermediate -I/home/hassan/devel/chromium/src/ > global_intermediate /home/hassan/devel/chromium/src/base/crypto/ > signature_verifier_nss.cc > g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ > file_util_posix.o -c -m32 -pthread -march=pentium4 -fno-exceptions - > msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/gtk-2.0 -I/ > usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/ > usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/ > include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/ > include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - > DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ > sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ > devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ > devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - > I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ > hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ > chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ > global_intermediate -I/home/hassan/devel/chromium/src/ > global_intermediate /home/hassan/devel/chromium/src/base/ > file_util_posix.cc > In file included from /home/hassan/devel/chromium/src/base/crypto/ > signature_verifier_nss.cc:5: > /home/hassan/devel/chromium/src/base/crypto/signature_verifier.h: > 11:22: error: cryptoht.h: No such file or directory > /home/hassan/devel/chromium/src/base/crypto/signature_verifier_nss.cc: > 7:22: error: cryptohi.h: No such file or directory > /home/hassan/devel/chromium/src/base/crypto/signature_verifier_nss.cc: > 8:19: error: keyhi.h: No such file or directory > ... > > And the version of Ubuntu and kernal I am running: > has...@hassan-desktop:~/devel/chromium/src/build$ lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 8.04.2 > Release:8.04 > Codename: hardy > has...@hassan-desktop:~/devel/chromium/src/build$ uname -a > Linux hassan-desktop 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC > 2009 i686 GNU/Linux > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cryptoht.h not found
Hi AFAIK the build system runs 'pkg-config --cflags nss' or something to figure out the correct paths. I'd poke at that to see if it yields any clues if Mohamed's suggestions don't help. See build/linux/system.gyp btw. --Craig On Mon, Apr 20, 2009 at 6:47 AM, Mohamed Mansour wrote: > Hi, can you try running, gclient runhooks --force, gclient sync --force, > clobber (delete build directory), and build again. > > On Sun, Apr 19, 2009 at 5:59 PM, Hassan wrote: >> >> Hello, >> >> I can't seem to compile chrome on my linux machine. It's complaining >> that it couldn't find cryptoht.h (see below). After some digging, I >> noticed g++ is possibly missing a -I/usr/include/nss flag since it >> seems that cryptoht.h lives in /usr/include/nss/: >> >> has...@hassan-desktop:~/devel/chromium/src/build$ locate cryptoht.h >> /usr/include/nss/cryptoht.h >> >> Could this be the reason? If so, what is the correct way of including >> that flag to g++? >> >> Thanks, >> - HR >> >> Here is the error message that I'm getting when compiling: >> has...@hassan-desktop:~/devel/chromium/src/build$ ../../depot_tools/ >> hammer app --verbose >> scons: Reading SConscript files ... >> scons: done reading SConscript files. >> scons: Building targets ... >> cd /home/hassan/devel/chromium/src/base && ../chrome/tools/build/linux/ >> version.sh file_version_info_linux.h.version /home/hassan/devel/ >> chromium/src/sconsbuild/Debug/obj/global_intermediate/base/ >> file_version_info_linux.h >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ >> crypto/signature_verifier_nss.o -c -m32 -pthread -march=pentium4 -fno- >> exceptions -msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/ >> gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/ >> include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/ >> lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 - >> I/usr/include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ >> devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - >> I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ >> hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ >> chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ >> global_intermediate -I/home/hassan/devel/chromium/src/ >> global_intermediate /home/hassan/devel/chromium/src/base/crypto/ >> signature_verifier_nss.cc >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ >> file_util_posix.o -c -m32 -pthread -march=pentium4 -fno-exceptions - >> msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/gtk-2.0 -I/ >> usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/ >> usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/ >> include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/ >> include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ >> devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - >> I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ >> hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ >> chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ >> global_intermediate -I/home/hassan/devel/chromium/src/ >> global_intermediate /home/hassan/devel/chromium/src/base/ >> file_util_posix.cc >> In file included from /home/hassan/devel/chromium/src/base/crypto/ >> signature_verifier_nss.cc:5: >> /home/hassan/devel/chromium/src/base/crypto/signature_verifier.h: >> 11:22: error: cryptoht.h: No such file or directory >> /home/hassan/devel/chromium/src/base/crypto/signature_verifier_nss.cc: >> 7:22: error: cryptohi.h: No such file or directory >> /home/hassan/devel/chromium/src/base/crypto/signature_verifier_nss.cc: >> 8:19: error: keyhi.h: No such file or directory >> ... >> >> And the version of Ubuntu and kernal I am running: >> has...@hassan-desktop:~/devel/chromium/src/build$ lsb_release -a >> No LSB modules are available. >> Distributor ID: Ubuntu >> Description: Ubuntu 8.04.2 >> Release: 8.04 >> Codename: hardy >> has...@hassan-desktop:~/devel/chromium/src/build$ uname -a >> Linux hassan-desktop 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC >> 2009 i686 GNU/Linux >> >> > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cryptoht.h not found
Thanks! Mohamed's suggestion worked fine, but now I'm getting a not enough memory error while linking. How do I get it to link dynamically instead? Presumably, linking dynamically would require less memory. - HR [error I'm getting..] flock /home/hassan/devel/chromium/src/sconsbuild/Debug/linker.lock g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/chrome -m32 -pthread /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_dll_main.o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_exe_main_gtk.o -L/home/hassan/devel/chromium/src/sconsbuild/Debug/lib -Wl,--start-group -lX11 -lXrender -lXext -lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -lpthread -ldl -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lfontconfig -lfreetype -lz -lrt -lcommon -lbrowser -lrenderer -lprinting -lviews -lbase -licui18n -licuuc -licudata -levent -lbase_gfx -lskia -lharfbuzz -lharfbuzz_interface -ljpeg -lpng -lz -lgoogleurl -lnet -lv8 -lv8_base -lsdch -lbz2 -lmodp_b64 -lxml2 -lglue -lwebcore -lpcre -lwtf -lxslt -lsqlite3 -lwebkit -lmedia -lhunspell -Wl,--end-group /lib/ld-linux.so.2: could not read symbols: Memory exhausted collect2: ld returned 1 exit status On Mon, Apr 20, 2009 at 7:25 AM, Craig Schlenter wrote: > Hi > > AFAIK the build system runs 'pkg-config --cflags nss' or something to > figure out the correct paths. I'd poke at that to see if it yields any > clues if Mohamed's suggestions don't help. > > See build/linux/system.gyp btw. > > --Craig > > On Mon, Apr 20, 2009 at 6:47 AM, Mohamed Mansour > wrote: > > Hi, can you try running, gclient runhooks --force, gclient sync --force, > > clobber (delete build directory), and build again. > > > > On Sun, Apr 19, 2009 at 5:59 PM, Hassan wrote: > >> > >> Hello, > >> > >> I can't seem to compile chrome on my linux machine. It's complaining > >> that it couldn't find cryptoht.h (see below). After some digging, I > >> noticed g++ is possibly missing a -I/usr/include/nss flag since it > >> seems that cryptoht.h lives in /usr/include/nss/: > >> > >> has...@hassan-desktop:~/devel/chromium/src/build$ locate cryptoht.h > >> /usr/include/nss/cryptoht.h > >> > >> Could this be the reason? If so, what is the correct way of including > >> that flag to g++? > >> > >> Thanks, > >> - HR > >> > >> Here is the error message that I'm getting when compiling: > >> has...@hassan-desktop:~/devel/chromium/src/build$ ../../depot_tools/ > >> hammer app --verbose > >> scons: Reading SConscript files ... > >> scons: done reading SConscript files. > >> scons: Building targets ... > >> cd /home/hassan/devel/chromium/src/base && ../chrome/tools/build/linux/ > >> version.sh file_version_info_linux.h.version /home/hassan/devel/ > >> chromium/src/sconsbuild/Debug/obj/global_intermediate/base/ > >> file_version_info_linux.h > >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ > >> crypto/signature_verifier_nss.o -c -m32 -pthread -march=pentium4 -fno- > >> exceptions -msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/ > >> gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/ > >> include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/ > >> lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 - > >> I/usr/include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - > >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ > >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ > >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ > >> devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - > >> I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ > >> hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ > >> chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ > >> global_intermediate -I/home/hassan/devel/chromium/src/ > >> global_intermediate /home/hassan/devel/chromium/src/base/crypto/ > >> signature_verifier_nss.cc > >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ > >> file_util_posix.o -c -m32 -pthread -march=pentium4 -fno-exceptions - > >> msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/gtk-2.0 -I/ > >> usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/ > >> usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/ > >> include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/ > >> include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - > >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ > >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ > >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ > >> devel/chromium/src/scons
[chromium-dev] Re: cryptoht.h not found
Hi Dynamic linking is not an option yet but it's being worked on. For now you should either use gold as the linker (see the wiki about faster linux builds) or perhaps try adding tons of swap space and take an extended holiday while you wait for it to link. --Craig On Mon, Apr 20, 2009 at 10:00 AM, Hassan Rom wrote: > Thanks! Mohamed's suggestion worked fine, but now I'm getting a not enough > memory error while linking. How do I get it to link dynamically instead? > Presumably, linking dynamically would require less memory. > > - HR > > [error I'm getting..] > flock /home/hassan/devel/chromium/src/sconsbuild/Debug/linker.lock g++ -o > /home/hassan/devel/chromium/src/sconsbuild/Debug/chrome -m32 -pthread > /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_dll_main.o > /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_exe_main_gtk.o > -L/home/hassan/devel/chromium/src/sconsbuild/Debug/lib -Wl,--start-group > -lX11 -lXrender -lXext -lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 > -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 > -lgmodule-2.0 -ldl -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 > -lplc4 -lnspr4 -lpthread -ldl -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm > -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl > -lglib-2.0 -lfontconfig -lfreetype -lz -lrt -lcommon -lbrowser -lrenderer > -lprinting -lviews -lbase -licui18n -licuuc -licudata -levent -lbase_gfx > -lskia -lharfbuzz -lharfbuzz_interface -ljpeg -lpng -lz -lgoogleurl -lnet > -lv8 -lv8_base -lsdch -lbz2 -lmodp_b64 -lxml2 -lglue -lwebcore -lpcre -lwtf > -lxslt -lsqlite3 -lwebkit -lmedia -lhunspell -Wl,--end-group > /lib/ld-linux.so.2: could not read symbols: Memory exhausted > collect2: ld returned 1 exit status > > > On Mon, Apr 20, 2009 at 7:25 AM, Craig Schlenter > wrote: >> >> Hi >> >> AFAIK the build system runs 'pkg-config --cflags nss' or something to >> figure out the correct paths. I'd poke at that to see if it yields any >> clues if Mohamed's suggestions don't help. >> >> See build/linux/system.gyp btw. >> >> --Craig >> >> On Mon, Apr 20, 2009 at 6:47 AM, Mohamed Mansour >> wrote: >> > Hi, can you try running, gclient runhooks --force, gclient sync --force, >> > clobber (delete build directory), and build again. >> > >> > On Sun, Apr 19, 2009 at 5:59 PM, Hassan wrote: >> >> >> >> Hello, >> >> >> >> I can't seem to compile chrome on my linux machine. It's complaining >> >> that it couldn't find cryptoht.h (see below). After some digging, I >> >> noticed g++ is possibly missing a -I/usr/include/nss flag since it >> >> seems that cryptoht.h lives in /usr/include/nss/: >> >> >> >> has...@hassan-desktop:~/devel/chromium/src/build$ locate cryptoht.h >> >> /usr/include/nss/cryptoht.h >> >> >> >> Could this be the reason? If so, what is the correct way of including >> >> that flag to g++? >> >> >> >> Thanks, >> >> - HR >> >> >> >> Here is the error message that I'm getting when compiling: >> >> has...@hassan-desktop:~/devel/chromium/src/build$ ../../depot_tools/ >> >> hammer app --verbose >> >> scons: Reading SConscript files ... >> >> scons: done reading SConscript files. >> >> scons: Building targets ... >> >> cd /home/hassan/devel/chromium/src/base && ../chrome/tools/build/linux/ >> >> version.sh file_version_info_linux.h.version /home/hassan/devel/ >> >> chromium/src/sconsbuild/Debug/obj/global_intermediate/base/ >> >> file_version_info_linux.h >> >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ >> >> crypto/signature_verifier_nss.o -c -m32 -pthread -march=pentium4 -fno- >> >> exceptions -msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/ >> >> gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/ >> >> include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/ >> >> lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 - >> >> I/usr/include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - >> >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ >> >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ >> >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ >> >> devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - >> >> I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ >> >> hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ >> >> chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ >> >> global_intermediate -I/home/hassan/devel/chromium/src/ >> >> global_intermediate /home/hassan/devel/chromium/src/base/crypto/ >> >> signature_verifier_nss.cc >> >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ >> >> file_util_posix.o -c -m32 -pthread -march=pentium4 -fno-exceptions - >> >> msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/gtk-2.0 -I/ >> >> usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/ >> >> usr/incl
[chromium-dev] Re: cryptoht.h not found
Definitely try gold. I think it was the only way I could get Chromium linking on my laptop. We ought to provide a binary of it somewhere, since few other projects seem to run into this. Maybe now that gyp is settled and most of temporary_link_stubs is gone we could reinvestigate dynamic linking... On Mon, Apr 20, 2009 at 1:56 AM, Craig Schlenter wrote: > > Hi > > Dynamic linking is not an option yet but it's being worked on. For now > you should either use gold as the linker (see the wiki about faster > linux builds) or perhaps try adding tons of swap space and take an > extended holiday while you wait for it to link. > > --Craig > > On Mon, Apr 20, 2009 at 10:00 AM, Hassan Rom wrote: >> Thanks! Mohamed's suggestion worked fine, but now I'm getting a not enough >> memory error while linking. How do I get it to link dynamically instead? >> Presumably, linking dynamically would require less memory. >> >> - HR >> >> [error I'm getting..] >> flock /home/hassan/devel/chromium/src/sconsbuild/Debug/linker.lock g++ -o >> /home/hassan/devel/chromium/src/sconsbuild/Debug/chrome -m32 -pthread >> /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_dll_main.o >> /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/chrome/app/chrome_exe_main_gtk.o >> -L/home/hassan/devel/chromium/src/sconsbuild/Debug/lib -Wl,--start-group >> -lX11 -lXrender -lXext -lrt -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 >> -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 >> -lgmodule-2.0 -ldl -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 >> -lplc4 -lnspr4 -lpthread -ldl -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm >> -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl >> -lglib-2.0 -lfontconfig -lfreetype -lz -lrt -lcommon -lbrowser -lrenderer >> -lprinting -lviews -lbase -licui18n -licuuc -licudata -levent -lbase_gfx >> -lskia -lharfbuzz -lharfbuzz_interface -ljpeg -lpng -lz -lgoogleurl -lnet >> -lv8 -lv8_base -lsdch -lbz2 -lmodp_b64 -lxml2 -lglue -lwebcore -lpcre -lwtf >> -lxslt -lsqlite3 -lwebkit -lmedia -lhunspell -Wl,--end-group >> /lib/ld-linux.so.2: could not read symbols: Memory exhausted >> collect2: ld returned 1 exit status >> >> >> On Mon, Apr 20, 2009 at 7:25 AM, Craig Schlenter >> wrote: >>> >>> Hi >>> >>> AFAIK the build system runs 'pkg-config --cflags nss' or something to >>> figure out the correct paths. I'd poke at that to see if it yields any >>> clues if Mohamed's suggestions don't help. >>> >>> See build/linux/system.gyp btw. >>> >>> --Craig >>> >>> On Mon, Apr 20, 2009 at 6:47 AM, Mohamed Mansour >>> wrote: >>> > Hi, can you try running, gclient runhooks --force, gclient sync --force, >>> > clobber (delete build directory), and build again. >>> > >>> > On Sun, Apr 19, 2009 at 5:59 PM, Hassan wrote: >>> >> >>> >> Hello, >>> >> >>> >> I can't seem to compile chrome on my linux machine. It's complaining >>> >> that it couldn't find cryptoht.h (see below). After some digging, I >>> >> noticed g++ is possibly missing a -I/usr/include/nss flag since it >>> >> seems that cryptoht.h lives in /usr/include/nss/: >>> >> >>> >> has...@hassan-desktop:~/devel/chromium/src/build$ locate cryptoht.h >>> >> /usr/include/nss/cryptoht.h >>> >> >>> >> Could this be the reason? If so, what is the correct way of including >>> >> that flag to g++? >>> >> >>> >> Thanks, >>> >> - HR >>> >> >>> >> Here is the error message that I'm getting when compiling: >>> >> has...@hassan-desktop:~/devel/chromium/src/build$ ../../depot_tools/ >>> >> hammer app --verbose >>> >> scons: Reading SConscript files ... >>> >> scons: done reading SConscript files. >>> >> scons: Building targets ... >>> >> cd /home/hassan/devel/chromium/src/base && ../chrome/tools/build/linux/ >>> >> version.sh file_version_info_linux.h.version /home/hassan/devel/ >>> >> chromium/src/sconsbuild/Debug/obj/global_intermediate/base/ >>> >> file_version_info_linux.h >>> >> g++ -o /home/hassan/devel/chromium/src/sconsbuild/Debug/obj/base/ >>> >> crypto/signature_verifier_nss.o -c -m32 -pthread -march=pentium4 -fno- >>> >> exceptions -msse2 -mfpmath=sse -Wall -Wno-write-strings -I/usr/include/ >>> >> gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/ >>> >> include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/ >>> >> lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 - >>> >> I/usr/include/pixman-1 -O0 -g -DCHROMIUM_BUILD -DTOOLKIT_GTK=1 - >>> >> DU_STATIC_IMPLEMENTATION -D_DEBUG -I/home/hassan/devel/chromium/src/ >>> >> sconsbuild/Debug/obj/third_party/icu38/public/common -I/home/hassan/ >>> >> devel/chromium/src/third_party/icu38/public/common -I/home/hassan/ >>> >> devel/chromium/src/sconsbuild/Debug/obj/third_party/icu38/public/i18n - >>> >> I/home/hassan/devel/chromium/src/third_party/icu38/public/i18n -I/home/ >>> >> hassan/devel/chromium/src/sconsbuild/Debug/obj -I/home/hassan/devel/ >>> >> chromium/src -I/home/hassan/devel/chromium/src/sconsbuild/Debug/obj/ >>> >> global_i
[chromium-dev] Re: cryptoht.h not found
On Mon, Apr 20, 2009 at 4:55 PM, Evan Martin wrote: [snip] > Maybe now that gyp is settled and most of temporary_link_stubs is gone > we could reinvestigate dynamic linking... It's working for me: http://codereview.chromium.org/67207 (changes to gyp itself, not really right) http://codereview.chromium.org/67212 (random other missing bits and pieces) Those changes are enough to get chrome working. The changes for test_shell etc. are also pretty easy but I doubt there's much interest in that so I haven't pushed that into review yet... --Craig --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cryptoht.h not found
Weird, I just received this error while compiling a "fresh" build on linux. Downloaded the tarball, and hammer (clean). The first error I saw on the screen was: cd: 1: can't cd to /auto/filer28.mtvvolmtvhome51/chrome-svn/tarball/chromium/src/base Then it stated: /home/m0/chromium/src/base/crypto/signature_verifier.h:11:22: error: cryptoht.h: No such file or directory I checked my pkg-config --cflags nss which returned: -I/usr/include/nss -I/usr/include/nspr I looked into it further and grep'd the gyp with mtvvolmtvhome51 and it appeared in couple. I had to do runhooks: gclient runhooks --force So my question, why does the tarball come with bad .scons files? Why doesn't the gclient sync regenerate them? Maybe add another step to the linux process that will tell the user to regenerate them after initial build. Many users having this problem it seems. -- Mohamed Mansour On Mon, Apr 20, 2009 at 12:07 PM, Craig Schlenter wrote: > On Mon, Apr 20, 2009 at 4:55 PM, Evan Martin wrote: > [snip] > > Maybe now that gyp is settled and most of temporary_link_stubs is gone > > we could reinvestigate dynamic linking... > > It's working for me: > > http://codereview.chromium.org/67207 (changes to gyp itself, not really > right) > http://codereview.chromium.org/67212 (random other missing bits and > pieces) > > Those changes are enough to get chrome working. The changes for test_shell > etc. are also pretty easy but I doubt there's much interest in that so I > haven't > pushed that into review yet... > > --Craig > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cryptoht.h not found
Hi Craig, Of course :) I have compiled Chromium numerous times in all platforms. I always run gclient sync --force in the "~/chromium directory (which has src, according to the wiki). Maybe it is just a hickup at my end, I will see if it happens again in the future. Thanks! -- Mohamed Mansour On Sat, May 16, 2009 at 12:18 PM, Craig Schlenter wrote: > > +chromium-dev > > --Craig > > -- Forwarded message -- > From: Craig Schlenter > Date: Sat, May 16, 2009 at 3:39 PM > Subject: Re: [chromium-dev] Re: cryptoht.h not found > To: Mohamed Mansour > > > Hi Mohamed > > The instructions at > http://dev.chromium.org/developers/how-tos/get-the-code say "6. > Updating your checkout once by running gclient sync --force in the > source code directory". Did you do that step? > > I'm not clued up on the inner details of gclient but from a quick > glance at the source reveals the following helpful comment: > > "Hooks > .gclient and DEPS files may optionally contain a list named "hooks" to > allow custom actions to be performed based on files that have changed in > the > working copy as a result of a "sync"/"update" or "revert" operation. > Hooks > can also be run based on what files have been modified in the working copy > with the "runhooks" operation. If any of these operation are run with > --force, all known hooks will run regardless of the state of the working > copy." > > That suggests that gclient sync --force should have run the hooks too > thus re-generating the scons files correctly. > > It is a bit strange that there are existing scons files in the tarball > but I suspect that's a side-effect of how the tarballs are generated. > BUG 6385 suggests that Pam or Tony might be able to shed some light on > that but I'd guess that gyp is being run in the tree before the > tarball is generated thus producing scons files that are incompatible > with your environment. > > --Craig > > On Sat, May 16, 2009 at 9:13 AM, Mohamed Mansour > wrote: > > Weird, > > > > I just received this error while compiling a "fresh" build on linux. > > Downloaded the tarball, and hammer (clean). The first error I saw on the > > screen was: > > cd: 1: can't cd to > > /auto/filer28.mtvvolmtvhome51/chrome-svn/tarball/chromium/src/base > > > > Then it stated: > > /home/m0/chromium/src/base/crypto/signature_verifier.h:11:22: error: > > cryptoht.h: No such file or directory > > > > I checked my pkg-config --cflags nss which returned: > > -I/usr/include/nss -I/usr/include/nspr > > > > I looked into it further and grep'd the gyp with mtvvolmtvhome51 and it > > appeared in couple. I had to do runhooks: > > gclient runhooks --force > > > > So my question, why does the tarball come with bad .scons files? Why > doesn't > > the gclient sync regenerate them? > > Maybe add another step to the linux process that will tell the user to > > regenerate them after initial build. Many users having this problem it > > seems. > > > > -- Mohamed Mansour > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: cryptoht.h not found
On Sat, May 16, 2009 at 12:13 AM, Mohamed Mansour wrote: > Weird, > > I just received this error while compiling a "fresh" build on linux. > Downloaded the tarball, and hammer (clean). The first error I saw on the > screen was: > cd: 1: can't cd to > /auto/filer28.mtvvolmtvhome51/chrome-svn/tarball/chromium/src/base > > Then it stated: > /home/m0/chromium/src/base/crypto/signature_verifier.h:11:22: error: > cryptoht.h: No such file or directory > > I checked my pkg-config --cflags nss which returned: > -I/usr/include/nss -I/usr/include/nspr > > I looked into it further and grep'd the gyp with mtvvolmtvhome51 and it > appeared in couple. I had to do runhooks: > gclient runhooks --force > > So my question, why does the tarball come with bad .scons files? Why doesn't > the gclient sync regenerate them? > Maybe add another step to the linux process that will tell the user to > regenerate them after initial build. Many users having this problem it > seems. I guess it's because when we used "gclient sync" to check out the source tree in the tarball, and that "gclient sync" command did runhooks at the end and generated .scons files that are only good on that computer. I don't know why another "gclient sync" didn't regenerate them. Perhaps because the timestamps of the .scons files were newer than the timestamps of the .gyp files? Wan-Teh --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
Fwd: [chromium-dev] Re: cryptoht.h not found
+chromium-dev --Craig -- Forwarded message -- From: Craig Schlenter Date: Sat, May 16, 2009 at 3:39 PM Subject: Re: [chromium-dev] Re: cryptoht.h not found To: Mohamed Mansour Hi Mohamed The instructions at http://dev.chromium.org/developers/how-tos/get-the-code say "6. Updating your checkout once by running gclient sync --force in the source code directory". Did you do that step? I'm not clued up on the inner details of gclient but from a quick glance at the source reveals the following helpful comment: "Hooks .gclient and DEPS files may optionally contain a list named "hooks" to allow custom actions to be performed based on files that have changed in the working copy as a result of a "sync"/"update" or "revert" operation. Hooks can also be run based on what files have been modified in the working copy with the "runhooks" operation. If any of these operation are run with --force, all known hooks will run regardless of the state of the working copy." That suggests that gclient sync --force should have run the hooks too thus re-generating the scons files correctly. It is a bit strange that there are existing scons files in the tarball but I suspect that's a side-effect of how the tarballs are generated. BUG 6385 suggests that Pam or Tony might be able to shed some light on that but I'd guess that gyp is being run in the tree before the tarball is generated thus producing scons files that are incompatible with your environment. --Craig On Sat, May 16, 2009 at 9:13 AM, Mohamed Mansour wrote: > Weird, > > I just received this error while compiling a "fresh" build on linux. > Downloaded the tarball, and hammer (clean). The first error I saw on the > screen was: > cd: 1: can't cd to > /auto/filer28.mtvvolmtvhome51/chrome-svn/tarball/chromium/src/base > > Then it stated: > /home/m0/chromium/src/base/crypto/signature_verifier.h:11:22: error: > cryptoht.h: No such file or directory > > I checked my pkg-config --cflags nss which returned: > -I/usr/include/nss -I/usr/include/nspr > > I looked into it further and grep'd the gyp with mtvvolmtvhome51 and it > appeared in couple. I had to do runhooks: > gclient runhooks --force > > So my question, why does the tarball come with bad .scons files? Why doesn't > the gclient sync regenerate them? > Maybe add another step to the linux process that will tell the user to > regenerate them after initial build. Many users having this problem it > seems. > > -- Mohamed Mansour --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
