[gentoo-user] Building firefox-61 with distcc

[Daniel Frey]

Well, I discovered some of my plugins stopped working on Firefox because
they've been updated to the new plugin format.

I've been using distcc for a long time now, and I've tried to build
firefox and it fails with:

--------------
Traceback (most recent call last):
File "/usr/lib64/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib64/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/testing/mozbase/mozprocess/mozprocess/processhandler.py",
line 1028, in _read
callback(line.rstrip())
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/testing/mozbase/mozprocess/mozprocess/processhandler.py",
line 944, in __call__
e(*args, **kwargs)
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/python/mach/mach/mixin/process.py",
line 86, in handleLine
line_handler(line)
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/python/mozbuild/mozbuild/controller/building.py",
line 681, in on_line
self.log(logging.INFO, 'build_output', {'line': message}, '{line}')
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/python/mach/mach/mixin/logging.py",
line 54, in log
extra={'action': action, 'params': params})
File "/usr/lib64/python2.7/logging/__init__.py", line 1231, in log
self._log(level, msg, args, **kwargs)
File "/usr/lib64/python2.7/logging/__init__.py", line 1286, in _log
self.handle(record)
File "/usr/lib64/python2.7/logging/__init__.py", line 1296, in handle
self.callHandlers(record)
File "/usr/lib64/python2.7/logging/__init__.py", line 1336, in
callHandlers
hdlr.handle(record)
File "/usr/lib64/python2.7/logging/__init__.py", line 759, in handle
self.emit(record)
File
"/var/tmp/portage/www-client/firefox-61.0-r1/work/firefox-61.0/python/mozbuild/mozbuild/controller/building.py",
line 564, in emit
self.fh.write(msg)
UnicodeEncodeError: 'ascii' codec can't encode characters in position
138-140: ordinal not in range(128)

----------

What I'm trying to figure out is if this is due to the recent python
changes or if it really is a distcc problem as per:

https://bugs.gentoo.org/662516

(I just noticed they tagged it wontfix. :( )

Has anyone found a solution for this other than disabling distcc
altogether? I'm going to try that now and see if it compiles.

If it does turn out to be distcc is there a method to disable distcc
just for the firefox package? The distcc article @ gentoo wiki doesn't
mention anything.

Dan

[Branko Grubic]

Same issue here with FF and distcc, it's happening for few releases
now, whenever I tried to find a solution I was going over some old
build system issues with FF on their bugzilla.

You can disable distcc for specific package using package.use[1].
I have just two things set:
FEATURES="-distcc -distcc-pump"
and MAKEOPTS reduced in the nodistcc.conf


[1] https://wiki.gentoo.org/wiki//etc/portage/package.env

[Branko Grubic]

On Thu, 2 Aug 2018 22:33:15 +0200
Branko Grubic <bitlo...@gmail.com> wrote:

> On Thu, 2 Aug 2018 13:14:22 -0700
> Daniel Frey <djq...@gmail.com> wrote:
>
> > Well, I discovered some of my plugins stopped working on Firefox
> > because they've been updated to the new plugin format.
> >
> > I've been using distcc for a long time now, and I've tried to build
> > firefox and it fails with:

...

> > Dan
> >
>
> Same issue here with FF and distcc, it's happening for few releases
> now, whenever I tried to find a solution I was going over some old
> build system issues with FF on their bugzilla.
>
> You can disable distcc for specific package using package.use[1].
> I have just two things set:
> FEATURES="-distcc -distcc-pump"
> and MAKEOPTS reduced in the nodistcc.conf
>
>
> [1] https://wiki.gentoo.org/wiki//etc/portage/package.env

It's not package.use but package.env, documentation url is right, just
what I wrote before isn't, no idea what I was thinking at the time.
Sorry for the confusion.

[Daniel Frey]

Thanks for that, I'll implement that. After I disabled distcc it
compiles fine. I wasn't using distcc-pump, just distcc. I guess I should
ignore the distcc article suggesting to file a bug when distcc breaks a
package, it doesn't look like they're going to fix it.

Dan