On Mon, Apr 17, 2017 at 02:18:16PM +0100, Peter Humphrey wrote > On Monday 17 Apr 2017 13:41:45 I wrote: > > > You see it couldn't even find a rule to make the object files. I tried > > setting MAKEOPTS="-j 1" to override the --jobs=24 that I usually have set, > > but that just changed the logged error, substituting 1 for 24. > > > > Does this ring a bell with anyone? I wanted to look for clues in the make > > file, but /usr/bin/find returns well over 1000 results. > > Well, I made it work by setting MAKEOPTS="" on the command line, but it > seems odd that portage's compiler settings are being misinterpreted this > way.
A couple of things to note, which also apply to building Firefox 1) When using the Palemoon overlay, I found that USE="optimize" turns off Gentoo's optimization, and replaces it with limited "optimization" by the mozconfig. If you're going to build it, I recommend USE="-optimize" 2) USE="-system-libs" is recommended. Yes, this does make the binary slightly larger. But it avoids problems where changing API/ABI in the system lib causes subtle problems for the program. It may also reduce dependancies pulled in, depending on what your other programs have pulled in. Consider taking the easy way out, and installing it locally from the tarball, e.g... * download the tarball from http://linux.palemoon.org/download/mainline/ * mkdir $HOME/pm * tar -C $HOME/pm -xvjf palemoon.*.bz2 *THE ENTIRE PROGRAM* is contained in the directory $HOME/pm/palemoon/ Extracting the tarball does *NOT* splatter libraries all over the place. "Uninstalling" consists of "rm -rf $HOME/pm/palemoon". The executable file will be $HOME/pm/palemoon/palemoon One more hint for graphics acceleration, which also applies to Firefox * set "layers.acceleration.force-enabled" to true in "about:config" * export MOZ_USE_OMTC=1 MOZ_USE_OMTC has to be set before launching Pale Moon -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
