On Sat, May 16, 2009 at 12: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.
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
-~----------~----~----~----~------~----~------~--~---
