On 9/26/08, doth <[EMAIL PROTECTED]> wrote:
>
> The registry entry was not set, the Cygwin\mounts v0 was empty,
> I created a new entry manually, but still no luck.
Ok, then this is the problem. The build process needs to prepopulate
this data. I don't know why it would not.
You can try prepopulating it yourself:
1. Open command prompt
2. go to C:\chromiumtrunk\chromium\src\third_party\cygwin
3. type "setup_mount.bat"
Then kill your Debug directory, and try building chrome again.
Nicolas
>
>
> On Sep 26, 11:11 pm, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote:
> > On 9/26/08, doth <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > @Nicholas,
> > > The registry was cleaned of entries containing "Cygwin" and then
> > > rebuilt, but no luck.
> > > Still getting the same error:
> >
> > Can you verify now that the registry contains the right information?
> >
> > Under "HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v0\bin"
> > Do you have "native" =
> "C:\chromiumtrunk\chromium\src\third_party\cygwin\bin\"
> >
> > Do not clean it, this information is required.
> >
> > Nicolas
> >
> > >
> ###########################################################################
> ######
> >
> > > 8>make: /bin/sh: Command not found
> > > 8>make: /bin/sh: Command not found
> >
> > > 8>make: *** [CSSGrammar.cpp] Error 127
> >
> > > 8>make: *** Waiting for unfinished jobs....
> > > 8>make: *** [CSSPropertyNames.h] Error 127
> >
> > > 8>Project : error PRJ0002 : Error result 1 returned from 'C:\WINDOWS
> > > \system32\cmd.exe'.
> >
> > > 8>Build log was saved at "file://C:\chromium\src\chrome\Debug\obj
> >
> > > \V8Bindings_prebuild\BuildLog.htm"
> > > 8>V8Bindings_prebuild - 1 error(s), 0 warning(s)
> >
> > >
> ###########################################################################
> #####
> >
> > > @Marc
> > > Tried gclient sync --force --verbose, it updated the files.... output
> > > below:
> >
> > > # An element of this array (a "solution") describes a repository
> > > directory
> > > # that will be checked out into your working copy. Each solution may
> > > # optionally define additional dependencies (via its DEPS file) to be
> > > # checked out alongside the solution's directory. A solution may also
> > > # specify custom dependencies (via the "custom_deps" property) that
> > > # override or augment the dependencies specified by the DEPS file.
> > > solutions = [
> > > { "name" : "src",
> > > "url" : "http://src.chromium.org/svn/trunk/src";,
> > > "custom_deps" : {
> > > # To use the trunk of a component instead of what's in DEPS:
> > > #"component": "https://svnserver/component/trunk/";,
> > > # To exclude a component from your working copy:
> > > #"data/really_large_component": None,
> > > "src/webkit/data/layout_tests/LayoutTests": None,
> > > }
> > > }
> > > ]
> >
> > > ________ running 'svn info --xml src' in 'C:\chromium'
> >
> > > ________ running 'svn update' in 'C:\chromium\src'
> > > At revision 2630.
> >
> > > ________ running 'svn info --xml src/breakpad/src' in 'C:\chromium'
> >
> > > ________ running 'svn update -r 285' in 'C:\chromium\src\breakpad\src'
> > > At revision 285.
> >
> > > ________ running 'svn info --xml src/googleurl' in 'C:\chromium'
> >
> > > ________ running 'svn update -r 93' in 'C:\chromium\src\googleurl'
> > > At revision 93.
> >
> > > ________ running 'svn info --xml src/testing/gtest' in 'C:\chromium'
> >
> > > ________ running 'svn update -r 63' in 'C:\chromium\src\testing\gtest'
> > > At revision 63.
> >
> > > ________ running 'svn info --xml src/third_party/WebKit' in 'C:
> > > \chromium'
> >
> > > ________ running 'svn update -r 19' in 'C:\chromium\src\third_party
> > > \WebKit'
> > > At revision 19.
> >
> > > ________ running 'svn info --xml src/third_party/cygwin' in 'C:
> > > \chromium'
> >
> > > ________ running 'svn update -r 1788' in 'C:\chromium\src\third_party
> > > \cygwin'
> > > At revision 1788.
> >
> > > ________ running 'svn info --xml src/third_party/icu38' in 'C:
> > > \chromium'
> >
> > > ________ running 'svn update -r 2463' in 'C:\chromium\src\third_party
> > > \icu38'
> > > At revision 2463.
> >
> > > ________ running 'svn info --xml src/third_party/python_24' in 'C:
> > > \chromium'
> >
> > > ________ running 'svn update -r 1790' in 'C:\chromium\src\third_party
> > > \python_24'
> > > At revision 1790.
> >
> > > ________ running 'svn info --xml src/third_party/svn' in 'C:\chromium'
> >
> > > ________ running 'svn update -r 1791' in 'C:\chromium\src\third_party
> > > \svn'
> > > At revision 1791.
> >
> > > ________ running 'svn info --xml src/v8' in 'C:\chromium'
> >
> > > ________ running 'svn update -r 373' in 'C:\chromium\src\v8'
> > > At revision 373.
> >
> > > On Sep 26, 10:45 pm, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote:
> >
> > > > On 9/26/08, doth <[EMAIL PROTECTED]> wrote:
> >
> > > > > I tried the following:
> > > > > - Delete the "Debug" folder and tried recompiling, no luck.
> > > > > - ran gclient sync,
> > > > > - Built the solution file, no luck, most errors are due to
> HTMLNames.h
> > > > > file missing in third_party \ webkit \ webcore \ html
> directory.....
> >
> > > > > @HLS,
> > > > > I'll try out your suggestion of installing SDK6.0, hope it
> > > > > works :-) ....
> >
> > > > I doubt it's going to work, but you can always try.
> >
> > > > From your build output it's clear what the problem is. The solution is
> > > > not that clear thought:
> >
> > > > > 1>Building DerivedSources /cygdrive/c/CHROMI~1/chromium/src/webkit/
> > > > > 1>make: /bin/sh: Command not found
> >
> > > > For some reasons it can't find "/bin/sh". It looks like the cygwin
> > > > that we have in the tree does not work well for you. The only time
> > > > I've seen that error was because the registry key I told you about
> > > > earlier was not being set correctly.
> >
> > > > Maruel: Any idea?
> >
> > > > Nicolas
> >
> > > > > On Sep 26, 10:21 pm, HLS <[EMAIL PROTECTED]> wrote:
> > > > > > Sounds like what I went through. There are few threads in the
> > > > > > Chromium-discuss fora.
> >
> > > > > > In the end, althought I think it should work with SDK v6.1
> (2008), it
> > > > > > appears the team is using v6.0 (VISTA SDK). After going thru
> that
> > > > > > process of download/installing v6.0, I was finally able to
> compile
> > > > > > after
> >
> > > > > > - Running
> >
> > > > > > gclient sync -force
> >
> > > > > > to make sure it gets the updates. There are 3-4 folders I had to
> > > > > > manually delete before gclient was successful. You can't trust
> > > > > > gclient reporting success, if there any aborts.
> >
> > > > > > - cleaning the solution first and do a full build.
> >
> > > > > > One mistake I did was to erroneously presume (slap across the
> head)
> > > > > > that you can compile the projects individually and/or via the
> command
> > > > > > line with VCBUILD. In fact, you can not without running into
> solution
> > > > > > build problems. So clean the solution first and use the IDE
> only.
> >
> > > > > > - Then take your wife and/or girlfiend to dinner, a movie, and
> when
> > > > > > you come back, maybe you will be lucky - multiple ways. :-)
> >
> > > > > > I really wish they would break down this project (oops, solution)
> > > > > > better. I noticed that a good bit of the total build time is
> used up
> > > > > > in building the test units. The next time I rebuild, I am going
> to
> > > > > > try to unload these projects to save some time.
> >
> > > > > > ---
> >
> > > > > > doth wrote:
> > > > > > > Great, i'll rebuild and keep the thread updated.
> >
> > > > > > > @Marc-Antoine
> > > > > > > Meanwhile i am trying the --force option with gclient, thanks
> Marc-
> > > > > > > Antoine for the suggestion
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
