RESOLVED FIXED 46602
new-run-webkit-httpd fails if Perl is not installed
https://bugs.webkit.org/show_bug.cgi?id=46602
Summary new-run-webkit-httpd fails if Perl is not installed
Mihai Parparita
Reported 2010-09-26 19:13:27 PDT
new-run-webkit-httpd fails if Perl is not installed
Attachments
Patch (3.60 KB, patch)
2010-09-26 19:17 PDT, Mihai Parparita
no flags
Mihai Parparita
Comment 1 2010-09-26 19:17:40 PDT
Mihai Parparita
Comment 2 2010-09-26 19:20:05 PDT
Adam, Eric or Ojan, would you mind taking a look? This is preventing Chromium WebKit rolls.
WebKit Commit Bot
Comment 3 2010-09-26 19:58:29 PDT
Comment on attachment 68869 [details] Patch Clearing flags on attachment: 68869 Committed r68365: <http://trac.webkit.org/changeset/68365>
WebKit Commit Bot
Comment 4 2010-09-26 19:58:35 PDT
All reviewed patches have been landed. Closing bug.
Tony Chang
Comment 5 2010-09-27 09:37:09 PDT
BTW, all the bots should have perl installed (e.g., generating bindings from IDL files is a perl script). Perhaps we need to fix a #! line or make sure cygwin is setup or something.
Mihai Parparita
Comment 6 2010-09-27 09:40:46 PDT
(In reply to comment #5) > BTW, all the bots should have perl installed (e.g., generating bindings from IDL files is a perl script). Perhaps we need to fix a #! line or make sure cygwin is setup or something. _webkit_build_directory assumes that perl is in the path: http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/layout_tests/port/base.py?rev=68365#L670 Not sure if that's valid under cygwin.
Tony Chang
Comment 7 2010-09-27 09:50:39 PDT
(In reply to comment #6) > _webkit_build_directory assumes that perl is in the path: > > http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/layout_tests/port/base.py?rev=68365#L670 > > Not sure if that's valid under cygwin. I think it is valid as long as third_party/cygwin/setup_mount.bat is run. It looks like there's code in ChromiumWinPort for this. Maybe that code isn't run when using new-run-webkit-httpd (but is when running NRWT)?
Note You need to log in before you can comment on or make changes to this bug.