Changeset 0f1ea40
- Timestamp:
- 11/09/2014 10:45:27 PM (9 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 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, 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:
- 615961f
- Parents:
- 637f310
- Location:
- xsoft/graphweb
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
xsoft/graphweb/firefox.xml
r637f310 r0f1ea40 229 229 EOF</userinput></screen> 230 230 231 <para> 232 There is a problem in i686 systems, when build with 233 <application>gcc</application> ranging from 4.8 to 4.9.1, and using the 234 switch <quote>--enable-optimize</quote>. You have two alternatives, best 235 one being the upgrade of <application>gcc</application> to version 4.9.2, 236 because that switch implies better perfomance and smaller binaries. 237 However, if you do not wish to upgrade gcc, disable the switch with: 238 </para> 239 240 <screen><userinput>test $(uname -m) = "i686" && sed -i 's/enable-optimize/disable-optimize/' mozconfig || true</userinput></screen> 231 <note><para> 232 There is a problem on i686 systems when building 233 <application>Firefox</application> with <application>gcc</application> 234 versions ranging from 4.8 to 4.9.1 and using the switch 235 <quote>--enable-optimize</quote>. There are two alternatives. The best 236 one is to upgrade <application>gcc</application> to version 4.9.2 or later 237 because it will give better perfomance and smaller binaries. However, if 238 you do not wish to upgrade gcc, reduce the level of optimization with: 239 </para> 240 241 <screen><userinput>test $(uname -m) = "i686" && sed -i 's/enable-optimize/&=-O2/' mozconfig || true</userinput></screen> 242 </note> 241 243 242 244 <para> … … 287 289 <sect2 role="commands"> 288 290 <title>Command Explanations</title> 289 290 <para>291 <command>test $(uname -m) = "i686" && sed ...</command>:292 On this version of seamonkey, an old bug has reappeared in 32-bit builds.293 With optimization, the install fails<!-- with a Python error-->. This294 command will fix i686 builds and preserve the optimization on x86_64.295 </para>296 291 297 292 <para> -
xsoft/graphweb/seamonkey.xml
r637f310 r0f1ea40 242 242 EOF</userinput></screen> 243 243 244 < para>244 <note><para> 245 245 There is a problem on i686 systems when building 246 246 <application>SeaMonkey</application> with <application>gcc</application> 247 247 versions ranging from 4.8 to 4.9.1 and using the switch 248 248 <quote>--enable-optimize</quote>. There are two alternatives. The best 249 one is to upgrade <application>gcc</application> to version 4.9.2 or later ,249 one is to upgrade <application>gcc</application> to version 4.9.2 or later 250 250 because it will give better perfomance and smaller binaries. However, if 251 251 you do not wish to upgrade gcc, reduce the level of optimization with: … … 253 253 254 254 <screen><userinput>test $(uname -m) = "i686" && sed -i 's/enable-optimize/&=-O2/' mozconfig || true</userinput></screen> 255 </note> 255 256 256 257 <note><para> … … 308 309 <sect2 role="commands"> 309 310 <title>Command Explanations</title> 310 311 <para>312 <command>test $(uname -m) = "i686" && sed ...</command>:313 On this version of seamonkey, an old bug has reappeared in 32-bit builds.314 With optimization, the install fails<!-- with a Python error-->. This315 command will fix i686 builds and preserve the optimization on x86_64.316 </para>317 311 318 312 <para>
Note:
See TracChangeset
for help on using the changeset viewer.