Ignore:
Timestamp:
08/27/2014 05:43:54 PM (10 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
200e254
Parents:
d8805ba2
Message:

Archive xulrunner

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@14097 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • xsoft/graphweb/firefox.xml

    rd8805ba2 rb9f61df  
    1414  <!ENTITY firefox-size          "141 MB">
    1515  <!-- measured on LFS-7.5, x86_64 -->
    16   <!ENTITY firefox-buildsize     "5.0 GB (62 MB installed) (or 963 MB and 7.0 MB if using Xulrunner)">
    17   <!ENTITY firefox-time          "48 SBU (0.3 SBU if using Xulrunner)">
     16  <!ENTITY firefox-buildsize     "5.0 GB (62 MB installed)">
     17  <!ENTITY firefox-time          "48 SBU">
    1818]>
    1919
     
    9999    <note>
    100100      <para>
    101         If you don't install recommended dependencies,
    102         then internal copies of those packages will
    103         be used. They might be tested to work, but
    104         they can be out of date or contain security
    105         holes.
     101        If you don't install recommended dependencies, then internal copies of
     102        those packages will be used. They might be tested to work, but they can
     103        be out of date or contain security holes.
    106104      </para>
    107105    </note>
     
    111109        With <application>Firefox-31.0</application> and later versions, you
    112110        must have installed <application>Openssl</application> before
    113         <application>Python 2</application>, or the build system will quickly
     111        <application>Python 2</application> or the build system will quickly
    114112        fail with output including "ImportError: cannot import name
    115113        HTTPSHandler". If you are in any doubt about this (e.g. upgrading
     
    117115        <filename>/usr/lib/python2.7/lib-dynload/_ssl.so</filename> exists.
    118116        If it does not, reinstall <xref linkend="python2"/> (after
    119         installing <xref linkend="openssl"/>  - the latest version of any
     117        installing <xref linkend="openssl"/>.  The latest version of any
    120118        <emphasis>currently maintained</emphasis> version of Openssl should
    121         be satisfactory if already installed - if that package has not already
    122         been installed).
     119        be satisfactory if already installed.
    123120      </para>
    124121    </note>
     
    140137      <xref linkend="pulseaudio"/>,
    141138      <xref linkend="startup-notification"/>,
    142       <xref linkend="wget"/>,
    143       <xref linkend="wireless_tools"/> and
    144       <xref linkend="xulrunner"/>
     139      <xref linkend="wget"/>, and
     140      <xref linkend="wireless_tools"/>
    145141    </para>
    146142
     
    154150
    155151    <para>
    156       There are two major methods for building
    157       <application>Firefox</application>. In the standard case, the entire suite
    158       of libraries is built and installed. In the other, most of the system is
    159       built using the procedures found in <xref linkend="xulrunner"/>. This is
    160       advantageous if you are planning to build other related packages such as
    161       <xref linkend="icedtea-web"/>. With either build method, you need to run
    162       the main build procedure below with the appropriate options in the
    163       <filename>mozconfig</filename> file. Then use the appropriate install
    164       instructions depending on the chosen build method.
    165     </para>
    166 
    167     <para>
    168       The configuration of <application>Firefox</application> is accomplished by
    169       creating a <filename>mozconfig</filename> file containing the desired
    170       configuration options. A default <filename>mozconfig</filename> is created
    171       below. To see the entire list of available configuration options (and an
    172       abbreviated description of each one), issue <command>./configure
     152      The configuration of <application>Firefox</application> is accomplished
     153      by creating a <filename>mozconfig</filename> file containing the desired
     154      configuration options. A default <filename>mozconfig</filename> is
     155      created below. To see the entire list of available configuration options
     156      (and an abbreviated description of each one), issue <command>./configure
    173157      --help</command>. You may also wish to review the entire file and
    174       uncomment any other desired options.
    175       Create the file by issuing the following command:
     158      uncomment any other desired options.  Create the file by issuing the
     159      following command:
    176160    </para>
    177161
     
    209193# If you have not installed Yasm then uncomment this line:
    210194#ac_add_options --disable-webm
    211 
    212 # If you have installed xulrunner uncomment the next two ac_add_options lines
    213 # and check that the sdk will be set by running pkg-config in a subshell
    214 # and has not become hardcoded or empty when you created this file
    215 #ac_add_options --with-system-libxul
    216 #ac_add_options --with-libxul-sdk=$(pkg-config --variable=sdkdir libxul)
    217195
    218196# Comment out following options if you have not installed
     
    272250    </para>
    273251
    274 <!--    <para>
    275       If you have <emphasis>not</emphasis> linked
    276       <application>Firefox</application> against an installed
    277       <application>Xulrunner</application>:
    278     </para>
    279 
    280 <screen><userinput>make -C firefox-build-dir/browser/installer</userinput></screen>
    281 -->
    282     <para>
    283       Now, as the <systemitem class="username">root</systemitem> user, if you
    284       have <emphasis>not</emphasis> linked <application>Firefox</application>
    285       against an installed <application>Xulrunner</application>, install the
    286       package:
    287     </para>
    288 
    289 <!--<screen role="root"><userinput>rm -rf /usr/lib/firefox-&firefox-version; &amp;&amp;
    290 mkdir  /usr/lib/firefox-&firefox-version; &amp;&amp;
    291 
    292 tar -xvf firefox-build-dir/dist/firefox-&firefox-version;.en-US.linux-$(uname -m).tar.bz2 \
    293     -C /usr/lib/firefox-&firefox-version; -\-strip-components=1 &amp;&amp;
    294 chown -R -v root:root /usr/lib/firefox-&firefox-version; &amp;&amp;
    295 
    296 ln -sfv ../lib/firefox-&firefox-version;/firefox /usr/bin &amp;&amp;-->
     252    <para>
     253      Now, as the <systemitem class="username">root</systemitem> user:
     254    </para>
     255
    297256<screen role="root"><userinput>make -f client.mk install INSTALL_SDK= &amp;&amp;
    298 
    299 mkdir -pv /usr/lib/mozilla/plugins &amp;&amp;
    300 ln -sfv ../mozilla/plugins /usr/lib/firefox-&firefox-version;</userinput></screen>
    301 
    302     <para>
    303       If you <emphasis>have</emphasis> linked against an already installed
    304       <application>Xulrunner</application>, as the
    305       <systemitem class="username">root</systemitem> user:
    306     </para>
    307 
    308 <screen role="root"><userinput>make -C firefox-build-dir install &amp;&amp;
    309 ln -sfv ../lib/firefox-&firefox-version;/firefox /usr/bin &amp;&amp;
    310 ln -sfv ../xulrunner-&firefox-version; /usr/lib/firefox-&firefox-version;/xulrunner &amp;&amp;
    311257
    312258mkdir -pv /usr/lib/mozilla/plugins &amp;&amp;
Note: See TracChangeset for help on using the changeset viewer.