Confirmed users
328
edits
Javascript:Hazard Builds: Difference between revisions
→Running the analysis: debian fix
(→Running the analysis: default directory would not work) |
(→Running the analysis: debian fix) |
||
| Line 12: | Line 12: | ||
=== Running the analysis === | === Running the analysis === | ||
To run the browser analysis, you must be on linux64 and do: | To run the browser analysis, you must be on a Fedora/RedHat/CentOS linux64 machine and do: | ||
cd <gecko> | cd <gecko> | ||
| Line 20: | Line 20: | ||
It doesn't matter what directory you run from, as long as it's not at the top of a source checkout. | It doesn't matter what directory you run from, as long as it's not at the top of a source checkout. | ||
If you are running Debian or Ubuntu, you may be able to get it to work by: | |||
sudo ln -s autoconf2.13 /usr/bin/autoconf-2.13 | |||
export CFLAGS="-B/usr/lib/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu" | |||
export CXXFLAGS="-B/usr/lib/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu" | |||
before running the script. | |||
If your hazards are all contained within js/src, you could use hazards/build_shell.py in place of hazards/build_browser.py. It will complete much more quickly. | If your hazards are all contained within js/src, you could use hazards/build_shell.py in place of hazards/build_browser.py. It will complete much more quickly. | ||