For the record, I build on win7 (both x86 and x64) on vs2008 without
problem here.
M-A
On Tue, Oct 6, 2009 at 9:21 PM, vha14 wrote:
>
> Still having the same issue after following John's suggestions. Being
> forced to use a separate cygwin's bash.exe.
>
> On Oct 2, 12:16 am, Abubakar wrote:
>>
Still having the same issue after following John's suggestions. Being
forced to use a separate cygwin's bash.exe.
On Oct 2, 12:16 am, Abubakar wrote:
> cygwin is supposed to be inside the chrome source that u download. Not to be
> done anything about it separately.
>
>
>
> On Fri, Oct 2, 2009 at
cygwin is supposed to be inside the chrome source that u download. Not to be
done anything about it separately.
On Fri, Oct 2, 2009 at 4:05 AM, Dan Kegel wrote:
>
> It's not supposed to be that way... maybe we need to check in a new cygwin.
>
> On Thu, Oct 1, 2009 at 4:03 PM, vha14 wrote:
> >
>
John, I'll try to reproduce the error as you suggested tomorrow. In
the mean time, I enlisted from another (much cleaner) Win7-x64 box and
was able to build successfully.
With respect to your question about the crash, please refer to my
initial post. Yes, gclient sync finished successfully.
On O
Chrome's cygwin installation is hermetic. It works for a number of Google
devs on Windows 7/64 bit so I don't think it's a simple case of the cygwin
installation being broken. What do you mean the binaries crash, did they
not resolve any dependent dlls? Are you sure your gclient sync finished
su
Ok, I fixed the problem by installing Cygwin (1.5.25-15), copying sh.exe
and bash.exe over to src\third_party\cygwin\bin.
So it may be a good idea to check in this Cygwin version.
On Oct 1, 2009 4:43pm, John Abd-El-Malek wrote:
> I built using the instructions on Windows 7 64 bit without insta
Ok, got this one fixed. The problem is that in my enlistment, sh.exe
and bash.exe both crashed. I installed cygwin (1.5.25-15) and then
copied these shells from the cygwin installation over to src
\third_party\cygwin\bin. So maybe it's a good idea to check in this
version of cygwin.
On Oct 1, 4:0
I built using the instructions on Windows 7 64 bit without installing
another cygwin.
On Thu, Oct 1, 2009 at 4:03 PM, vha14 wrote:
>
> So it looks like I need to install Cygwin separately before I can
> build Chrome? If so this should be added to the Windows build
> instruction page.
>
> On Oct
It's not supposed to be that way... maybe we need to check in a new cygwin.
On Thu, Oct 1, 2009 at 4:03 PM, vha14 wrote:
>
> So it looks like I need to install Cygwin separately before I can
> build Chrome? If so this should be added to the Windows build
> instruction page.
>
> On Oct 1, 2:59 pm
So it looks like I need to install Cygwin separately before I can
build Chrome? If so this should be added to the Windows build
instruction page.
On Oct 1, 2:59 pm, Mohamed Mansour wrote:
> I run "Cygwin Bash Shell" not from Command Prompt:
>
> moha...@mohamed-pc ~$ bash
>
> -Mohamed
>
>
>
> On
I run "Cygwin Bash Shell" not from Command Prompt:
moha...@mohamed-pc ~$ bash
-Mohamed
On Thu, Oct 1, 2009 at 5:32 PM, vha14 wrote:
>
> Hi Mohamed, can you run bash.exe from cmd? I get the following error:
>
> E:\chromium\home\chrome-svn\tarball\chromium\src\third_party\cygwin
> \bin>bash
>
Hi Mohamed, can you run bash.exe from cmd? I get the following error:
E:\chromium\home\chrome-svn\tarball\chromium\src\third_party\cygwin
\bin>bash
9 [main] bash 8384 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
9964 [main] bash 8384 open_stackdumpfile: Dumping stack tr
Windows 7 64bit works fine here (using the default settings from
dev.chromium.org) Make sure you have access to the folder your writing to.
Some folders require admin mode.
-Mohamed
On Thu, Oct 1, 2009 at 4:10 PM, vha14 wrote:
>
> Detailed error message:
>
> 1>-- Build started: Project: j
13 matches
Mail list logo
