+chromium-dev --Craig
---------- Forwarded message ---------- From: Craig Schlenter <craig.schlen...@gmail.com> Date: Sat, May 16, 2009 at 3:39 PM Subject: Re: [chromium-dev] Re: cryptoht.h not found To: Mohamed Mansour <m0.interact...@gmail.com> 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 <m0.interact...@gmail.com> 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 -~----------~----~----~----~------~----~------~--~---
