fix typo

Cameron Kaiser 2017-05-30 22:35:16 -07:00
parent a085126a49
commit 1e79f4f030

@ -29,8 +29,8 @@ These build instructions are always subject to change. You should be familiar wi
* **G4 and G5 owners:** if you want to test the AltiVec (VMX) code paths apart from the standard `mozcfg` files, you should include `--enable-tenfourfox-vmx` in your custom `.mozconfig` or it will be compiled without AltiVec/VMX acceleration.
* **G5 owners _ONLY_:** if you want to test the G5-specific code paths apart from the standard `G5.mozcfg`, you should include `--enable-tenfourfox-g5` in your custom `.mozconfig` or the regular code paths will be used instead of the G5-specific ones. This does not enable VMX; if you want that, specify it too. You may also need to add `-D_PPC970_` to your compiler strings so that non-Mozilla libraries and JavaScript properly select the correct architecture optimizations. Although you don't need this, the browser will run substantially more poorly if you don't.
* **Intel owners _ONLY_: Intel builds for TenFourFox 45 do not work.** You can fix this! Good luck; submit patches if you get it operational.
1. (Optional but recommended) Edit `netwerk/protocols/http/OptimizedFor.h` and set the string to something human-readable about the configuration you're building for. This string should be relatively short, and will appear after the `TenFourFox/` in the user agent string.
* **Warning:** if you don't do something like `git update-index --skip-worktree netwerk/protocols/http/OptimizedFor.h`, this change will end up in any pull requests you issue and _we won't accept them_!
1. (Optional but recommended) Edit `netwerk/protocol/http/OptimizedFor.h` and set the string to something human-readable about the configuration you're building for. This string should be relatively short, and will appear after the `TenFourFox/` in the user agent string.
* **Warning:** if you don't do something like `git update-index --skip-worktree netwerk/protocol/http/OptimizedFor.h`, this change will end up in any pull requests you issue and _we won't accept them_!
1. (Optional) If you want to change the reported version numbers, alter `browser/config/version.txt` for the reported browser version, `browser/config/version_display.txt` for the _displayed_ browser version (this is where we usually put the long FPR string), and `config/milestone.txt` for the reported Gecko version.
* We don't allow these changes in pull requests either! Consider setting `skip-worktree` on these files also if you change them!
1. Once you're ready, if you are cleaning out an old build, be sure to `rm -rf configure obj-ff-dbg/` first. Then,