On January 3, 2019 8:59:09 AM Dale <rdalek1...@gmail.com> wrote:

Davyd McColl wrote:


On January 3, 2019 12:29:34 AM Dale <rdalek1...@gmail.com> wrote:

Nikos Chantziaras wrote:
On 02/01/2019 22:45, Dale wrote:
I changed some USE flags.  I figure that is one thing that would make
Firefox different from say the average user who just downloads Firefox
from the website.
Is there a reason you don't want to try the firefox-bin package I
meantion in my previous post?





That will be if I can't get a source build to work.  Thing is, I won't
be surprised if it does the same thing.  I suspect this is a bug related
to some permission issue or something related to it within Firefox
itself.  I've wondered if I should allow Firefox to store the files in
its own download directory and then move them after it is completed.  I
may try that as well. 

Long term tho, I do prefer building from source.  It's sort of why I
like Gentoo.  ;-)  It's on the list of options tho.  It would eliminate
any local build configs too.  It is a good idea to at least test it.  I
may try that next.  If it still does it, it isn't me for sure.  It's
Firefox itself. 
I agree it's a good idea to try the bin. Also perhaps to try to to
back to as vanilla USE flags as possible. IIRC, my only deviances from
the default USE flags are to disable pulseaudio and enable clang
(though that was only recently after the announcement about how it was
supposed to improve performance so much, and was to become the
mozilla-preferred method).

Fortunately, at least Firefox builds relatively quickly, unlike
chromium (~40 min vs ~2.5h on my machine).

Yea, it is a good idea.  Thing is, my network is busy right now.  I'm on
a video download binge again.  -_O

Question.  Just what is clang?  I did a eix for it but its description
is minimal and not to informative, if one doesn't already know what it
is.  If you know, what does it add to Firefox and briefly how does it do
it?  The reason I ask, could that help with my current issue?  I'm all
for Firefox being faster, even on this pretty fast rig, but I'd also
give it a try as well if it would fix this issue and as a bonus make
Firefox work better/faster/whatever as well. 
It's a front-end for llvm (a kind of generic compiler) - bascially a compiler replacement for gcc which has shown good compile times and the Mozilla team is claiming fairly reasonable performance gains when compiled with clang. It's been around a while, so it's not like you're taking a huge chance or anything. It's just not quite as venerable as gcc.

Thanks.

Dale

:-)  :-) 




Reply via email to