Ignore:
Timestamp:
08/28/2022 07:03:28 PM (20 months ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal
Children:
96923ef
Parents:
9737271
git-author:
Pierre Labastie <pierre.labastie@…> (08/28/2022 07:00:05 PM)
git-committer:
Pierre Labastie <pierre.labastie@…> (08/28/2022 07:03:28 PM)
Message:

Building mozilla apps with gcc is broken on i686

We used to sed the double_t definition to allow building, but now
we use clang, so that the build passes without sed. Say that using
GCC breaks the build in command explanations too.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • xsoft/graphweb/seamonkey.xml

    r9737271 rf572dbb  
    116116      <xref linkend="libevent"/>,
    117117      <!--<xref linkend="libvpx"/>, Causes build failures similar to Firefox -->
    118       <xref linkend="libwebp"/>
     118      <xref linkend="libwebp"/>,
     119      <xref linkend="llvm"/> (with clang),
    119120      <xref linkend="nasm"/>,
    120121      <xref linkend="nspr"/>,
     
    313314      With the introduction of <application>gcc-12</application>, many
    314315      more warnings are generated when compiling mozilla applications
    315       and that results in a much slower, and larger, build.
     316      and that results in a much slower, and larger, build. Furthermore,
     317      building with GCC on i?86 is currently broken.
    316318      Although upstream mozilla code defaults to using
    317319      <application>llvm</application> unless overridden, the older configure
Note: See TracChangeset for help on using the changeset viewer.