| 24 | | |
| 25 | | == Changes to the build since 78.0 == |
| 26 | | |
| 27 | | In firefox-81.0, creating the python virtual environments was separated out. Trying to run ./mach build reported |
| 28 | | {{{ |
| 29 | | Consider running 'mach bootstrap' or 'mach create-mach-environment' to create the mach virtualenvs, or set MACH_USE_SYSTEM_PYTHON to use the system Python installation over a virtualenv. |
| 30 | | }}} |
| 31 | | |
| 32 | | Trying ./mach bootstrap failed: |
| 33 | | {{{ |
| 34 | | NotImplementedError: Bootstrap support for this Linux distro not yet available: lfs |
| 35 | | }}} |
| 36 | | |
| 37 | | I was reluctant to try the system python option because that looked as if it would use pip to download required packages and perhaps try to install them on the system. |
| 38 | | |
| 39 | | Using './mach create-mach-environment' before running other mach commands (but after the exports) worked. |
| 40 | | |
| 41 | | Later, somebody reported that this prevents offline builds. The better solution is |
| 42 | | {{{ |
| 43 | | export MACH_USE_SYSTEM_PYTHON=1 |
| 44 | | }}} |
| 45 | | |
| 46 | | I now see that creating the mach environment (with python-3.8) took 72MB in .mozbuild/ (noticed because I forgot the export on a manual build and libpython-3.8.so.1 was not found). |
| 47 | | |
| 48 | | From 78.7.0 I changed the './mach build' invocation to first run './mach configure' (just checking deps and creating the build files ("reticulating splines") to be more consistent with conventional packages, followed by './mach build' after noticing this in an AUR thunderbird build. For those of us who do not have rust on their normal PATH, or have multiple versions of rust, this allows a quick check that all is ok rather than running './mach build', leaving it and coming back to find it failed during the configure. |
| 49 | | |
| 50 | | == Withdrawal of ftp == |
| 51 | | |
| 52 | | Not a change to the build process, but in 90.0 the ability to use ftp links was removed. |
| 53 | | If this bothers you, consider using firefox-legacy (currently 78.14.0 - does not work on glibc-2.34) as a short-term workaround until you find an alternative (current seamonkey and falkon permit this, but seamonkey tends to lag behind the firefox vulnerability fixes, while seamonkey requires qtwebengine which is a heavy overhead). |
