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 <[email protected] > wrote: > On Mon, Apr 20, 2009 at 4:55 PM, Evan Martin <[email protected]> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
