Summary: | app-text/calibre fails to build due to segfault in libuuid with >=sys-apps/util-linux-2.17.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Gaber <Michael.Gaber> |
Component: | [OLD] Unspecified | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Adrian.Bassett, chris, erikdenstore+gbugs, flameeyes, gentoo, hoea, mark+gentoobugs, nbkolchin, ninuje, rajat.vig, rich0, stentj, tante, tuxtor, yo |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 317557, 353224 | ||
Bug Blocks: | |||
Attachments: | build log |
Description
Michael Gaber
2010-04-14 21:32:58 UTC
Created attachment 227803 [details]
build log
I guess the segfault is in python or in a python module that's imported. Can you try rebuilding python? did it twice already, didnt help I have the same experience. During the calibre building or the adding the book into the previous version, python segfaults in libuuid.1.3.0 lib. (In reply to comment #4) > I have the same experience. During the calibre building or the adding the book > into the previous version, python segfaults in libuuid.1.3.0 lib. Calibre built successfully for me with /lib/libuuid.so.1.3.0 provided by sys-apps/util-linux-2.17.2 here. Maybe you just need to upgrade util-linux. > Calibre built successfully for me with /lib/libuuid.so.1.3.0 provided by
> sys-apps/util-linux-2.17.2 here. Maybe you just need to upgrade util-linux.
>
I have the same version of util-linux and python-2.6.5-r1. I tried to downgrade python to 2.6.4, but it didn't help.
It's working here with python-2.6.5-r1 and util-linux-2.17.2: [ebuild R ] sys-apps/util-linux-2.17.2 USE="crypt nls perl slang unicode -loop-aes -old-linux (-selinux) (-uclibc)" [ebuild R ] dev-lang/python-2.6.5-r1 USE="doc gdbm ipv6 ncurses readline sqlite ssl threads tk (wide-unicode) xml -berkdb -build -examples -wininst" Maybe it's a toolchain issue. It's working here with gcc-4.3.4 and here's my trimmed --info: Portage 2.2_rc67_p69 (default/linux/x86/10.0/desktop, gcc-4.3.4, glibc-2.11-r1, 2.6.33-0402-x86-64 i686) ================================================================= System uname: Linux-2.6.33-0402-x86-64-i686-Intel-R-_Core-TM-2_CPU_6300_@_1.86GHz-with-gentoo-2.0.1 Timestamp of tree: Wed, 31 Mar 2010 15:30:23 +0000 distcc 3.1 i686-pc-linux-gnu [disabled] ccache version 2.4 [disabled] app-shells/bash: 4.1_p2-r1 dev-java/java-config: 2.1.10 dev-lang/python: 2.6.5-r1, 3.1.2-r1 dev-python/pycrypto: 2.1.0 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.8.1 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.6.1-r1 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.13, 2.65 sys-devel/automake: 1.4_p6-r1, 1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1 sys-devel/gcc: 4.3.4, 4.4.3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.33 ACCEPT_KEYWORDS="x86 ~x86" CFLAGS="-march=i686 -pipe -O2" CHOST="i686-pc-linux-gnu" LDFLAGS="-Wl,--as-needed,--hash-style=gnu" You might try using this guide to get a backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml (In reply to comment #7) > It's working here with python-2.6.5-r1 and util-linux-2.17.2: > > [ebuild R ] sys-apps/util-linux-2.17.2 USE="crypt nls perl slang unicode > -loop-aes -old-linux (-selinux) (-uclibc)" > [ebuild R ] dev-lang/python-2.6.5-r1 USE="doc gdbm ipv6 ncurses readline > sqlite ssl threads tk (wide-unicode) xml -berkdb -build -examples -wininst" > Everything seem to be the same. The only difference that my world has been built with gcc-4.4.3 (In reply to comment #7) > It's working here with python-2.6.5-r1 and util-linux-2.17.2: > The downgrade to util-linux-2.16.2 has resolved this problem for me. util-linux-2.17-r1 also works downgrade to util-linux-2.16.2 worked, 2.17.1 did not, didn't test between versions. See http://bugs.gentoo.org/show_bug.cgi?id=317557 for details on this same problem with app-text/calibre-0.6.49 and app-text/calibre-0.6.50 same problem with app-text/calibre-0.6.49 but the util-linux-2.17-r1 fix the problem same problem with app-text/calibre-0.6.51 *** Bug 318765 has been marked as a duplicate of this bug. *** emerge =util-linux-2.16.2 && emerge calibre && emerge util-linux Will work to get past the problem until a real fix is available. (In reply to comment #17) > emerge =util-linux-2.16.2 && emerge calibre && emerge util-linux > > Will work to get past the problem until a real fix is available. > It doesn't help: in this case calibre can't add the book into its list. *** Bug 321183 has been marked as a duplicate of this bug. *** (In reply to comment #18) > (In reply to comment #17) > > emerge =util-linux-2.16.2 && emerge calibre && emerge util-linux > > > > Will work to get past the problem until a real fix is available. > > > > It doesn't help: in this case calibre can't add the book into its list. > You're correct. Trying the same thing with util-linux-2.17-r1 resulted in a calibre that wouldn't start. The only thing this work-past does is get calibre updated so that it's failure stops interfering with "emerge -uND world". The situation sucks. And while we're on the topic of calibre issues, it would be nice if the calibre udev rules were updated from the deprecated SYSFS{} directive to the ATTR{} directive. {sigh} (In reply to comment #20) > (In reply to comment #18) > > (In reply to comment #17) > > > emerge =util-linux-2.16.2 && emerge calibre && emerge util-linux > > > > > > Will work to get past the problem until a real fix is available. > > > > > > > It doesn't help: in this case calibre can't add the book into its list. > > > this appear to be also in =calibre-0.6.53 & =calibre-0.6.55 > You're correct. Trying the same thing with util-linux-2.17-r1 resulted in a > calibre that wouldn't start. > > The only thing this work-past does is get calibre updated so that it's failure > stops interfering with "emerge -uND world". > > The situation sucks. > > And while we're on the topic of calibre issues, it would be nice if the calibre > udev rules were updated from the deprecated SYSFS{} directive to the ATTR{} > directive. > > {sigh} > app-text/calibre-0.7.1 doesn't compile as well. 0.7.1 does compile, it's just failing to install. /var/tmp/portage/app-text/calibre-0.7.1/temp/environment: line 1424: 8487 Segmentation fault "$(PYTHON)" setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" install --root="${D}" --no-compile "$@" * ERROR: app-text/calibre-0.7.1 failed: * Installation failed * * Call stack: * ebuild.sh, line 54: Called src_install * environment, line 4853: Called distutils_src_install '--bindir=/var/tmp/portage/app-text/calibre-0.7.1/image/usr/bin' '--sharedir=/var/tmp/portage/app-text/calibre-0.7.1/image/usr/share' * environment, line 1441: Called die * The specific snippet of code: * "$(PYTHON)" setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" install --root="${D}" --no-compile "$@" || die "Installation failed"; The 0.7.2 ebuild has a workaround that looks like this: uuid=$(python -c 'import sys, uuid; sys.stdout.write(str(uuid.uuid4()))') sed -e "s:str(uuid.uuid4()):'$uuid':" -i src/calibre/utils/config.py According the the Changelog, upstream as included a workaround for this since calibre-0.7.15 (and it seems to work here). |