Re: Bug#760865: calibre: FTBFS on mips: thread.error: can't start new thread
Martin Pitt <[email protected]>
| Newsgroups | gmane.linux.debian.ports.mips |
|---|---|
| Message-ID | <[email protected]> |
Emilio Pozuelo Monfort [2014-09-08 18:07 +0200]: > Your package has failed to build on mips since version 2.0.0: > File "/usr/lib/python2.7/threading.py", line 745, in start > _start_new_thread(self.__bootstrap, ()) > thread.error: can't start new thread This looks like a bug in the mips kernel/python/buildd. It should be possible to at least start as many threads as there are CPU cores (that's what calibre's build system uses to determine how many parallel build threads to use), but apparently that's not the case. I'll work around it in calibre to force cpu_count to 1 in the build system on mips in the meantime. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUEBsoAAoJENFO8V2v4RNHDKgP/0bJ0tEW1HhoORsHsvyDih4G J4uOh4axtWcxBuQgi8bFU1ejK3fuhlLATRPlX42X9K59XEUFh4A8NqlIoebnG5NK QT3hlyyTMySeGOWQ04aOnlffgGHENMl5iDidNsjhAUDfN+2/9WzMD9Wh89KYS50s yI78fMDyGQoczGF8Qja0LKLRgO39ZoAc/1ZmXKSRNR4D8NC5pJ8CrOGuIVZp6kj0 4GcWEf4JZNAGWSC3XGtF9AZrM2aeHJ/J6ZOzr5P9t0EQvfxXS0vgKWZY5mnRK55s s9OGaiPBWay8pG7IOo8V+Gpo5Iyx/9cGnkbdgTTo3Z5CvQIXFnctvQYl5fF6DISt Pu08D5AntUEsdTcLDbXPt/oBezn3nzQPPMQ4eYqxXi7gd7h2BkP8H6fZXYqapG8k WyMV+P+u+V//UbOd4Ot3L4zE/ug/dX2XES4KMHRu3+NtY3rYFoksN/2LTWXXD6ix j8H2EPDTsYcefktyh/8MHysdJCqYqh7SdvjPkX+EBcGytQHIa1zs/56z+gXGpEUf zsWBWqKhO+kdMTTzn/UHZARD/Kn9gEEmMvWhpw4dWOlKiceqvO3AYWDb03OWmqjr hDX1u2KTG+CNyEfRapYRqBa8+alWoIxtU6Omwgxr0Dv3skgtGAWOrapojNBA6vZz rSgQRdBaNVrQG7KyjZyZ =yFhz -----END PGP SIGNATURE-----