Creating config.status Reticulating splines... Traceback (most recent call last): File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/configure.py", line 128, in <module> sys.exit(main(sys.argv)) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/configure.py", line 35, in main return config_status(config) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/configure.py", line 123, in config_status return config_status(args=[], **encode(sanitized_config, encoding)) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/config_status.py", line 147, in config_status definitions = list(definitions) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/emitter.py", line 177, in emit for out in output: File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/reader.py", line 899, in read_topsrcdir for r in self.read_mozbuild(path, self.config): File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/reader.py", line 1061, in read_mozbuild raise bre mozbuild.frontend.reader.BuildReaderError: ============================== ERROR PROCESSING MOZBUILD FILE ============================== The error occurred while processing the following file: /var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/security/moz.build The error appears to be part of the mozbuild.frontend.reader Python module itself! It is possible you have stumbled across a legitimate bug. Traceback (most recent call last): File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/reader.py", line 1057, in read_mozbuild metadata=metadata): File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/reader.py", line 1165, in _read_mozbuild non_unified_sources) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/python/mozbuild/mozbuild/frontend/gyp_reader.py", line 410, in __init__ encode(depth), params) File "/var/tmp/portage/www-client/seamonkey-2.53.6/work/seamonkey-2.53.6/third_party/python/futures/concurrent/futures/process.py", line 336, in submit self._result_queue.put(None) File "/usr/lib64/python2.7/multiprocessing/queues.py", line 107, in put self._start_thread() File "/usr/lib64/python2.7/multiprocessing/queues.py", line 195, in _start_thread self._thread.start() File "/usr/lib64/python2.7/threading.py", line 736, in start _start_new_thread(self.__bootstrap, ()) error: can't start new thread *** Fix above errors and then restart with\ "make -f client.mk build" make: *** [client.mk:316: configure] Error 1 Reproducible: Always Steps to Reproduce: It also happens with seamonkey-2.53.5.1 as well. Any ideas?
Please add the output of emerge --info seamonkey as a comment to this bug and attach the build.log file as well.
There was a problem with my system disturbing thread creation and memory operations unrelated to this package, but I first realized this during this emerge.
