source: xsoft/graphweb/firefox.xml@ ca73053a

11.0 lazarus qt5new trunk
Last change on this file since ca73053a was ca73053a, checked in by Ken Moffat <ken@…>, 5 months ago

Firefox-78.10.1 and JS-78.10.1.

  • Property mode set to 100644
File size: 23.7 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
8 <!ENTITY firefox-download-ftp " ">
9 <!ENTITY firefox-md5sum "0aa9c735305304373f9fddc35c56e81b">
10 <!ENTITY firefox-size "319 MB">
11 <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
12 But the extra cached cargo files, if any, seem to be minimal -->
13 <!ENTITY firefox-buildsize "5.2 GB (186 MB installed) without tests">
14 <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
15 most practical way to get a timing on a machine with more cores, if taking
16 cores offline is not practical. If in doubt, round up -->
17 <!ENTITY firefox-time "30 SBU (on a 4-core machine) without tests">
18]>
19
20<sect1 id="firefox" xreflabel="Firefox-&firefox-version;">
21 <?dbhtml filename="firefox.html" ?>
22
23 <sect1info>
24 <date>$Date$</date>
25 </sect1info>
26
27 <title>Firefox-&firefox-version;</title>
28
29 <indexterm zone="firefox">
30 <primary sortas="a-Firefox">Firefox</primary>
31 </indexterm>
32
33 <sect2 role="package">
34 <title>Introduction to Firefox</title>
35
36 <para>
37 <application>Firefox</application> is a stand-alone browser based on the
38 <application>Mozilla</application> codebase.
39 </para>
40
41 &lfs101_checked;
42
43 <bridgehead renderas="sect3">Package Information</bridgehead>
44 <itemizedlist spacing="compact">
45 <listitem>
46 <para>
47 Download (HTTP): <ulink url="&firefox-download-http;"/>
48 </para>
49 </listitem>
50 <listitem>
51 <para>
52 Download (FTP): <ulink url="&firefox-download-ftp;"/>
53 </para>
54 </listitem>
55 <listitem>
56 <para>
57 Download MD5 sum: &firefox-md5sum;
58 </para>
59 </listitem>
60 <listitem>
61 <para>
62 Download size: &firefox-size;
63 </para>
64 </listitem>
65 <listitem>
66 <para>
67 Estimated disk space required: &firefox-buildsize;
68 </para>
69 </listitem>
70 <listitem>
71 <para>
72 Estimated build time: &firefox-time;
73 </para>
74 </listitem>
75 </itemizedlist>
76
77<!--<bridgehead renderas="sect3">Additional Downloads</bridgehead>
78 <itemizedlist spacing="compact">
79 <listitem>
80 <para>
81 Required patch:
82 <ulink url="&patch-root;/firefox-&firefox-version;esr-rustc1470-1.patch"/>
83 </para>
84 </listitem>
85 </itemizedlist>-->
86
87 <note>
88 <para>
89 The directory name is firefox-&firefox-version;
90 </para>
91
92 <para>
93 Extracting the tarball
94 will reset the permissions of the current directory to 0755 if you
95 have permission to do that. If you do this in a directory where
96 the sticky bit is set, such
97 as <filename class="directory">/tmp</filename> it will end with error
98 messages:
99 </para>
100
101<literallayout>tar: .: Cannot utime: Operation not permitted
102tar: .: Cannot change mode to rwxr-xr-t: Operation not permitted
103tar: Exiting with failure status due to previous errors
104</literallayout>
105
106 <para>
107 This does finish with non-zero status, but it does
108 <emphasis>NOT</emphasis> mean there is a real problem.
109 Do not untar as the <systemitem class="username">root</systemitem> user
110 in a directory where the sticky bit is set - that will unset it.
111 </para>
112
113 <para>
114 As with other large packages which use C++ (or rust), the SBU times
115 to build this vary more widely than you might expect. The build times
116 will increase significantly if your machine has to swap.
117 </para>
118
119 <!-- commented, by 78.0 it seems to work reliably
120 <para>
121 The mach build system (Python scripts) can be somewhat unreliable: if
122 the build fails and reports an Error, it can still return a status of
123 success, causing a scripted build to try to install (which does not rerun
124 the build), fail during the preparations for installing, but still exit
125 with a status of success. Also, on occasion it may limit itself to only
126 running one set of jobs - that will make the build take about 3 times as
127 long as running with four sets of jobs.
128 </para>-->
129
130 <para>
131 Although upstream prefer to use <application>PulseAudio</application>,
132 for the moment <application>Alsa</application> can still be used. Both
133 may need runtime configuration to get sound working.
134 </para>
135 </note>
136
137 <bridgehead renderas="sect3">Firefox Dependencies</bridgehead>
138
139 <bridgehead renderas="sect4">Required</bridgehead>
140 <para role="required">
141 <xref linkend="autoconf213"/>,
142 <xref linkend="cbindgen"/>,
143 <xref linkend="dbus-glib"/>,
144 both <xref linkend="gtk3"/> and
145 <xref linkend="gtk2"/>,
146 <xref linkend="libnotify"/>,
147 <xref linkend="llvm"/> (clang, used for bindgen even if using gcc),
148 <xref linkend="nodejs"/>,
149 <xref linkend="nss"/>,
150 <xref linkend="pulseaudio"/>
151 (or
152 <xref linkend="alsa-lib"/> if you edit the mozconfig;
153 now deprecated by mozilla), in either case please read the
154 Configuration Information,
155 <!-- rustc is required by cbindgen so not needed here
156 <xref linkend="rust"/>,-->
157 <xref linkend="python3"/> (rebuilt after installing <xref linkend="sqlite"/>),
158 <xref linkend="startup-notification"/>,
159 <xref linkend="unzip"/>,
160 <xref linkend="yasm"/>, and
161 <xref linkend="zip"/>
162 </para>
163
164 <bridgehead renderas="sect4">Recommended</bridgehead>
165 <para role="recommended">
166 <xref linkend="icu"/>,
167 <xref linkend="libevent"/>,
168 <xref linkend="libwebp"/>,
169 <xref linkend="nasm"/>
170 </para>
171
172 <note>
173 <para>
174 If you don't install recommended dependencies, then internal copies of
175 those packages will be used. They might be tested to work, but they can
176 be out of date or contain security holes.
177 </para>
178 </note>
179
180 <bridgehead renderas="sect4">Optional</bridgehead>
181 <para role="optional">
182 <xref linkend="curl"/>,
183 <xref linkend="doxygen"/>,
184 <xref role="runtime" linkend="ffmpeg"/> (runtime, to play mov, mp3 or mp4 files),
185 <!-- <phrase revision="sysv"><ulink url="https://sourceforge.net/projects/liboauth/files/">liboauth</ulink></phrase> -->
186 <xref linkend="liboauth"/>,
187 <xref linkend="openjdk"/>,
188 <xref linkend="valgrind"/>,
189 <xref linkend="wget"/>,
190 <xref linkend="wireless_tools"/>,
191 <ulink url="https://github.com/libproxy/libproxy">libproxy</ulink>
192 </para>
193
194 <para condition="html" role="usernotes">
195 User Notes: <ulink url="&blfs-wiki;/firefox"/>
196 </para>
197 </sect2>
198
199 <sect2 role="installation">
200 <title>Installation of Firefox</title>
201
202 <para>
203 The configuration of <application>Firefox</application> is accomplished
204 by creating a <filename>mozconfig</filename> file containing the desired
205 configuration options. A default <filename>mozconfig</filename> is
206 created below. To see the entire list of available configuration options
207 (and an abbreviated description of some of them), issue <command>./mach
208 configure &amp;&amp; ./configure --help | less</command>. You may also
209 wish to review the entire file and uncomment any other desired options.
210 Create the file by issuing the following command:
211 </para>
212
213<screen><userinput>cat &gt; mozconfig &lt;&lt; "EOF"
214<literal># If you have a multicore machine, all cores will be used by default.
215
216# If you have installed (or will install) wireless-tools, and you wish
217# to use geolocation web services, comment out this line
218ac_add_options --disable-necko-wifi
219
220# API Keys for geolocation APIs - necko-wifi (above) is required for MLS
221# Uncomment the following line if you wish to use Mozilla Location Service
222#ac_add_options --with-mozilla-api-keyfile=$PWD/mozilla-key
223
224# Uncomment the following line if you wish to use Google's geolocaton API
225# (needed for use with saved maps with Google Maps)
226#ac_add_options --with-google-location-service-api-keyfile=$PWD/google-key
227
228# startup-notification is required since firefox-78
229
230# Uncomment the following option if you have not installed PulseAudio
231#ac_add_options --disable-pulseaudio
232# or uncomment this if you installed alsa-lib instead of PulseAudio
233#ac_add_options --enable-alsa
234
235# Comment out following options if you have not installed
236# recommended dependencies:
237ac_add_options --with-system-libevent
238ac_add_options --with-system-webp
239ac_add_options --with-system-nspr
240ac_add_options --with-system-nss
241ac_add_options --with-system-icu
242
243# Do not specify the gold linker which is not the default. It will take
244# longer and use more disk space when debug symbols are disabled.
245
246# libdavid (av1 decoder) requires nasm. Uncomment this if nasm
247# has not been installed.
248#ac_add_options --disable-av1
249
250# You cannot distribute the binary if you do this
251ac_add_options --enable-official-branding
252
253# Stripping is now enabled by default.
254# Uncomment these lines if you need to run a debugger:
255#ac_add_options --disable-strip
256#ac_add_options --disable-install-strip
257
258# Disabling debug symbols makes the build much smaller and a little
259# faster. Comment this if you need to run a debugger. Note: This is
260# required for compilation on i686.
261ac_add_options --disable-debug-symbols
262
263# The elf-hack is reported to cause failed installs (after successful builds)
264# on some machines. It is supposed to improve startup time and it shrinks
265# libxul.so by a few MB - comment this if you know your machine is not affected.
266ac_add_options --disable-elf-hack
267
268# The BLFS editors recommend not changing anything below this line:
269ac_add_options --prefix=/usr
270ac_add_options --enable-application=browser
271ac_add_options --disable-crashreporter
272ac_add_options --disable-updater
273# enabling the tests will use a lot more space and significantly
274# increase the build time, for no obvious benefit.
275ac_add_options --disable-tests
276
277# The default level of optimization again produces a working build with gcc.
278ac_add_options --enable-optimize
279
280ac_add_options --enable-system-ffi
281ac_add_options --enable-system-pixman
282
283# --with-system-bz2 was removed in firefox-78
284ac_add_options --with-system-jpeg
285ac_add_options --with-system-png
286ac_add_options --with-system-zlib
287
288# The following option unsets Telemetry Reporting. With the Addons Fiasco,
289# Mozilla was found to be collecting user's data, including saved passwords and
290# web form data, without users consent. Mozilla was also found shipping updates
291# to systems without the user's knowledge or permission.
292# As a result of this, use the following command to permanently disable
293# telemetry reporting in Firefox.
294unset MOZ_TELEMETRY_REPORTING
295
296mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/firefox-build-dir</literal>
297EOF</userinput></screen>
298
299 <para>
300 Compile <application>Firefox</application> by issuing the following
301 commands:
302 </para>
303
304 <para>
305 In the esr version of firefox-78, the code to ensure that add-ons
306 are signed by the trusted root has been disabled, presumably for
307 organizations which require their own add-ons. To enable it as an
308 added security measure issue the following command:
309 </para>
310
311<screen><userinput>sed -e 's/Disable/Enable/' \
312 -e '/^MOZ_REQUIRE_SIGNING/s/0/1/' \
313 -i build/mozconfig.common</userinput></screen>
314
315 <para>
316 If the geolocation APIs are needed:
317 </para>
318
319 <note>
320 <para>
321 <!-- Taken from Arch Linux - an immensely helpful link - Thanks -->
322 The Google and Mozilla API Keys below are specific to LFS. If using
323 these instructions for another distro, or if you intend to distribute
324 binary copies of the software using these instructions, please obtain
325 your own keys following the instructions located at
326 <ulink url="http://www.chromium.org/developers/how-tos/api-keys"/> and
327 <ulink url="https://location.services.mozilla.com/api"/> respectively.
328 <!-- BLFS Devs, register an account at Google with your
329 @linuxfromscratch.org email address, and I'll make you an administrator
330 for the 'Google APIs for LFS' project (where the API and OAuth keys
331 were created for use in the book).-->
332 </para>
333 </note>
334
335<screen><userinput>echo "AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ" > google-key
336echo "613364a7-9418-4c86-bcee-57e32fd70c23" > mozilla-key</userinput></screen>
337
338 <note>
339
340 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
341 href="../../xincludes/mozshm.xml"/>
342
343 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
344 href="../../xincludes/mozmach.xml"/>
345
346 </note>
347 <!--
348 <para>
349 If you are building on i686, apply a fix to prevent Internal Compiler
350 Errors in GCC-7+:
351 </para>
352
353<screen><userinput remap="pre">case $(uname -m) in
354 i?86) sed -i "562 s/mips64/i386/" gfx/skia/skia/third_party/skcms/src/Transform_inl.h ;;
355esac</userinput></screen>
356 -->
357<!--<para>
358 Apply a patch to allow this to be compiled with <xref linkend="rust"/>:
359 </para>
360
361<screen><userinput remap="pre">patch -p1 -i ../firefox-&firefox-version;esr-rustc1470-1.patch</userinput></screen>-->
362
363 <para>
364 Now invoke the Python script to compile the package.
365 </para>
366
367<screen><userinput>export CC=gcc CXX=g++ &amp;&amp;
368export MOZBUILD_STATE_PATH=${PWD}/mozbuild &amp;&amp;
369./mach configure &amp;&amp;
370./mach build</userinput></screen>
371
372 <para>
373 The <filename>mozconfig</filename> above disables the tests because
374 they use a lot more time and disk space for no obvious benefit. If
375 you have nevertheless enabled them, you can run the tests by executing
376 <command>./mach gtest</command>. This will require a network connection,
377 and to be run from within an Xorg session - there is a popup dialog
378 when it fails to connect to ALSA (that does not create a failed test).
379 One or two tests will fail. To see the details of the failure(s) you
380 will need to log the output from that command so that you can review it.
381 </para>
382
383 <para>
384 Now, as the <systemitem class="username">root</systemitem> user:
385 </para>
386
387<screen role="root"><userinput>./mach install</userinput></screen>
388
389 <para>
390 Set environment variables back to their values:
391 </para>
392
393<screen><userinput>unset CC CXX MOZBUILD_STATE_PATH</userinput></screen>
394
395 </sect2>
396
397 <sect2 role="commands">
398 <title>Command Explanations</title>
399
400<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
401 href="../../xincludes/SIOCGSTAMP.xml"/>-->
402
403 <para>
404 <command>export CC=gcc CXX=g++ ...</command>: Upstream now prefer
405 <application>clang</application> so that they can use one compiler
406 everywhere. On the X86 architectures <application>clang</application>
407 now appears to support most of the same security-hardening options as
408 <application>GCC</application>.
409 <!-- supported in llvm-11
410 but the newer
411 <literal>-fstack-clash-protection</literal> is still not supported.-->
412 With the current versions and the default flags,
413 <application>GCC</application> creates a marginally bigger build but
414 takes typically 2 SBU less time on a 4-core machine using the mozconfig
415 above.
416 </para>
417
418 <para>
419 <command>export MOZBUILD_STATE_PATH=${PWD}/mozbuild</command>: The build
420 is now supposed to tell you that it intends to create <filename
421 class="directory">~/.mozbuild</filename>, and offer you an option to
422 press &lt;ENTER&gt; to accept this, or Ctrl-C to cancel and restart the
423 build after specifying the directory. In practice, the message may not
424 appear until after &lt;ENTER&gt; is keyed, i.e. the build stalls.
425 </para>
426
427 <para>
428 That directory is used for a (probably random) telemetry identifier.
429 Creating this in the build directory, and deleting that after the
430 installation, prevents it being used. If you wish to participate in
431 telemetry, export MOZBUILD_STATE_PATH to point to its default directory.
432 </para>
433
434 <para>
435 <command>./mach build</command>: <application>Firefox</application>
436 now uses this <application>python</application> script to run the
437 build and install.
438 </para>
439
440 <para>
441 <option>./mach build --verbose</option>: Use this alternative if you
442 need details of which files are being compiled, together with any C or
443 C++ flags being used. But do not add '--verbose' to the install command,
444 it is not accepted there.
445 </para>
446
447 <para>
448 <option>./mach build -jN</option>: The build should, by default, use
449 all the online CPU cores. If using all the cores causes the build to swap
450 because you have insufficient memory, using fewer cores can be faster.
451 </para>
452
453 <para>
454 <command>mkdir -pv /usr/lib/mozilla/plugins</command>: This ensures
455 that <filename class="directory">/usr/lib/mozilla/plugins/</filename>
456 exists.
457 </para>
458
459 <para>
460 <command>ln -sv ... /usr/lib/firefox/browser</command>:
461 This command creates a symbolic link to <filename
462 class="directory">/usr/lib/mozilla/plugins</filename>. It's not really
463 needed, as <application>Firefox</application> checks <filename
464 class="directory">/usr/lib/mozilla/plugins</filename> by default, but the
465 symbolic link is made to keep all the plugins installed in one folder.
466 </para>
467
468 </sect2>
469
470 <sect2 role="configuration">
471 <title>Configuring Firefox</title>
472
473 <para>
474 If you use a desktop environment like <application>Gnome</application> or
475 <application>KDE</application> you may like to create a
476 <filename>firefox.desktop</filename> file so that
477 <application>Firefox</application> appears in the panel's menus. <!--If you
478 didn't enable startup-notification in your mozconfig change the
479 StartupNotify line to false.--> As the
480 <systemitem class="username">root</systemitem> user:
481 </para>
482
483<screen role="root"><userinput>mkdir -pv /usr/share/applications &amp;&amp;
484mkdir -pv /usr/share/pixmaps &amp;&amp;
485
486cat &gt; /usr/share/applications/firefox.desktop &lt;&lt; "EOF" &amp;&amp;
487<literal>[Desktop Entry]
488Encoding=UTF-8
489Name=Firefox Web Browser
490Comment=Browse the World Wide Web
491GenericName=Web Browser
492Exec=firefox %u
493Terminal=false
494Type=Application
495Icon=firefox
496Categories=GNOME;GTK;Network;WebBrowser;
497MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
498StartupNotify=true</literal>
499EOF
500
501ln -sfv /usr/lib/firefox/browser/chrome/icons/default/default128.png \
502 /usr/share/pixmaps/firefox.png</userinput></screen>
503
504 <sect3><title>Configuration Information</title>
505
506 <para>
507 The application settings for firefox are accessible by keying
508 <command>about:config</command> in the address bar.
509 </para>
510
511 <para>
512 Occasionally, getting working sound in
513 <application>firefox</application> can be a problem. Although upstream
514 prefers pulseaudio,
515 on balance using <application>Alsa</application> may be easier.
516 </para>
517
518 <para>
519 If you enabled <application>Alsa</application> for sound, you may need
520 to alter one variable to get working sound. If you run
521 <command>firefox</command> from a term and try to play something with
522 sound you might encounter error messages like:
523 </para>
524
525 <para>
526 <literal>Sandbox: seccomp sandbox violation: pid 3941, tid 4030,
527 syscall 16, args 48 2147767296 139909894784796 0 0 0.</literal>
528 </para>
529
530 <para>
531 That was on x86_64, on i686 the syscall number is 54. To allow this
532 syscall, in <command>about:config</command> change
533 <command>security.sandbox.content.syscall_whitelist</command> to 16
534 (or 54 if using i686).
535 </para>
536
537 <para>
538 If you use <command>pulseaudio</command> in a Desktop Environment, it
539 might already be started by that DE. But if it is not, although
540 firefox-57 managed to start it, firefox-58 did not. If you run
541 <command>firefox</command> from a term and this problem is present,
542 trying to play sound will
543 encounter error messages warning <literal>Can't get cubeb
544 context!</literal>
545 </para>
546
547 <para>
548 The fix for this is to close firefox, start pulseaudio to check it
549 does start (if not, read the information on Configuring in <xref
550 linkend="pulseaudio"/>) and restart firefox to check it is working.
551 If it now works, add the following to your <filename>~/.xinitrc</filename>:
552<phrase revision="sysv">
553<literal>pulseaudio --verbose --log-target=syslog&amp;</literal></phrase>
554<phrase revision="systemd">
555<literal>pulseaudio --verbose --log-target=journald&amp;</literal></phrase>
556 (unfortunately, on some systems this does not work).
557 </para>
558
559 <para>
560 You may wish to use multiple profiles within firefox. To do that, invoke
561 firefox as <command>firefox --ProfileManager</command>. You can also
562 check which profile is currently in use from
563 <command>about:profiles</command>.
564 </para>
565
566 <para>
567 Although WebRender (using the GPU for compositing) is not used by
568 default, it now appears to work well on supported hardware (ATI, Nvidia
569 and Intel GPUs with Mesa-18 or later. For an explanation, please see
570 <ulink
571 url="https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/">hacks.mozilla.org</ulink>.
572 The only downside seems to be that on a machine with limited RAM it might
573 use more RAM.
574 </para>
575
576 <para>
577 To check if WebRender is being used, look in about:support. In the Graphics
578 section Compositing will either show 'Basic' (i.e. not in use) or
579 'WebRender'. To enable it, go to about:config and change gfx.webrender.all
580 to True. You will need to restart firefox.
581 </para>
582
583 <para>
584 It may be useful to mention the processes from firefox which can appear in
585 <command>top</command> - as well as firefox itself, there may be multiple
586 Web Content processes, and now an RDD Process (Remote Data Decoder) which
587 appears when playing web videos encoded with av1 (libdav1d). If WebRender
588 has been enabled, a GPU Process will also appear when firefox has to
589 repaint (e.g. scrolling, opening a new tab, or playing a video).
590 </para>
591
592 </sect3>
593 </sect2>
594
595 <sect2 role="content">
596 <title>Contents</title>
597
598 <segmentedlist>
599 <segtitle>Installed Programs</segtitle>
600 <segtitle>Installed Libraries</segtitle>
601 <segtitle>Installed Directory</segtitle>
602
603 <seglistitem>
604 <seg>
605 firefox
606 </seg>
607 <seg>
608 Numerous libraries, browser components, plugins, extensions, and
609 helper modules installed in /usr/lib/firefox
610 </seg>
611 <seg>
612 /usr/lib/firefox and /usr/lib/mozilla
613 </seg>
614 </seglistitem>
615 </segmentedlist>
616
617 <variablelist>
618 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
619 <?dbfo list-presentation="list"?>
620 <?dbhtml list-presentation="table"?>
621
622 <varlistentry id="firefox-prog">
623 <term><command>firefox</command></term>
624 <listitem>
625 <para>
626 is a <application>GTK+-3</application> internet browser that uses
627 the Mozilla Gecko rendering engine
628 </para>
629 <indexterm zone="firefox firefox-prog">
630 <primary sortas="b-firefox">firefox</primary>
631 </indexterm>
632 </listitem>
633 </varlistentry>
634
635 </variablelist>
636
637 </sect2>
638
639</sect1>
Note: See TracBrowser for help on using the repository browser.