Bug 31484 – 32-bit WebKit being built on 64-bit machine when building via crontab

• Component: Tools / Tests
• Status: RESOLVED INVALID

[Simon Welsh]

If I clean then build WebKit (using build-webkit --clean && build-webkit), running run-safari causes Safari to correctly load the WebKit build.

I have a crontab set up that daily runs /Volumes/SpeedMonkey/WebKitTools/Scripts/update-webkit && /Volumes/SpeedMonkey/WebKitTools/Scripts/build-webkit. Upon running run-safari after this, I get the expected message: "Starting Safari with DYLD_FRAMEWORK_PATH set to point to built WebKit in /Volumes/SpeedMonkey/WebKitBuild/Release", but the WebKit build is not loaded.

This is on Mac OS 10.6.1 and 10.6.2, running Safari 4.0.3 and 4.0.4 respectively.

[Mark Rowe (bdash)]

How are you determining that it is not used?

[Simon Welsh]

The useragent is the standard Safari one, without the newer WebKit version or the +

[Simon Welsh]

Further investigation has shown this to be because build-webkit being called from within a cron job is building a 32-bit version, rather than a 64-bit. I have since switched to using launchd.

[Mark Rowe (bdash)]

Please retitle the bug to describe what the problem actually is!

[Ahmad Saleem]

[e-mail] - Is it something still applicable? or Webkit 32-bit is gone now?

[Brent Fulgham]

I don't believe this is still an issue.

[Alexey Proskuryakov]

32-bit WebKit is gone, however:
- I strongly suspect that this wasn't the only thing that was going wrong in this scenario;
- and that it has nothing to do with WebKit, but with the environment that cron jobs run it (a different environment? maybe even as root?)

Using launchd is the right approach anyway.