Okay, I think I've figured this out and it's a relatively undocumented aspect of our win builds (from what I can tell).
The third_party/cygwin install we have has a modified version of cygwin1.dll , which has been patched to tell cygwin the root is third_party/cygwin rather than /. In order for this to work correctly, you need to run third_party/cygwin/setup_mount.bat to stuff the right entries into the registry. We should probably change run_layout_tests to automatically run this script prior to running the regression (running it every time should be harmless). -- Dirk On Thu, Jul 2, 2009 at 7:27 PM, Dirk Pranke<[email protected]> wrote: > Debugging this a bit more ... it seems to be some sort of XP vs. Vista > thing. If I run "wdiff exp.txt act.txt" in a bash shell or a command > prompt on Vista, it works. On XP, it works in a bash shell, but in a > command prompt, I get the "/tmp" error. It looks like XP is expecting > to find the cygwin environment, but isn't, and it is finding it on > Vista. I don't see anything obvious in my environment that is > different. > > I am running Cygwin 1.5.25, though. At this point, my knowledge of > cygwin falters, so I'm out of ideas. Anyone else? > > -- Dirk > > On Thu, Jul 2, 2009 at 6:08 PM, Dirk Pranke<[email protected]> wrote: >> Oh, I should add that if I run the same binaries under Vista, >> everything works fine (no error from wdiff). >> >> -- Dirk >> >> On Thu, Jul 2, 2009 at 6:07 PM, Dirk Pranke<[email protected]> wrote: >>> Hi Marc-Antoine, >>> >>> I am getting the same "wdiff: /tmp/t101c.0: No such file or directory" >>> errors ... I'm running an XP VM on a Vista 64 host, but I've tried >>> both local files (running the tests on a virtual drive) as well as a >>> network share to the host VM. I've tried the /etc/fstab, the >>> CYGWIN=nontsec, and the changing of directory ACLs, all to no avail. >>> Any other ideas? >>> >>> -- Dirk >>> >>> On Thu, Jul 2, 2009 at 5:53 PM, Marc-Antoine Ruel<[email protected]> >>> wrote: >>>> 2009/7/1 Bradley Nelson <[email protected]> >>>>> >>>>> gyp should be setting CYGWIN=nontsec for actions and rules (unless you use >>>>> the msvs_use_cygwin_shell:0). >>>> >>>> FYI, cygwin 1.7 doesn't honour CYGWIN=NONTSEC anymore. You need to modify >>>> /etc/fstab, e.g. c:\cygwin\etc\fstab to add something line: >>>> none /cygdrive cygdrive binary,posix=0,user,noacl 0 0 >>>> to have the same effect. >>>> M-A >>>> >>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
