| Summary: | dev-python/pylibmc-1.2.3 fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Patrick Lauer
2012-10-17 03:09:19 UTC
What version of libmemcached are you building against? This occurs with libmemcached 0.12. It seems to be an upstream bug: libmemcached-1.0/configure.h:#define LIBMEMCACHED_VERSION_HEX @PANDORA_HEX_VERSION@ # USE_PYTHON="2.5 2.6 2.7-pypy-1.9" ebuild pylibmc-1.2.3.ebuild clean install
Writing /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/temp/images/2.7-pypy-1.9/usr/lib64/pypy1.9/site-packages/pylibmc-1.2.3-py2.7.egg-info
>>> Completed installing pylibmc-1.2.3 into /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/image/
built fine here. libmemcached 0.12 would be 2007-8 vintage.
This
x86_64-pc-linux-gnu-gcc -pthread -march=athlon64 -pipe -fomit-frame-pointer -O2 -fPIC -DUSE_ZLIB -I/usr/include/python2.6 -c _pylibmcmodule.c -o build-2.6/temp.linux-x86_64-2.6/_pylibmcmodule.o -fno-strict-aliasing
is the line where it trips. I can display the 'what' but certainly not the 'why'
from above traceback; "token "@" is not valid in preprocessor expressions"
unless I'm missing something,
# grep "@" /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/work/pylibmc-1.2.3/{_pylibmcmodule.h,_pylibmcmodule.c}
yields blank. In the build that fails the preprocessor expressions appear to feature token '@', build in my system they're absent. Someone knowing more than I can give this more meaning.
(In reply to comment #3) > # USE_PYTHON="2.5 2.6 2.7-pypy-1.9" ebuild pylibmc-1.2.3.ebuild clean install > Writing > /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/temp/images/2.7-pypy-1.9/ > usr/lib64/pypy1.9/site-packages/pylibmc-1.2.3-py2.7.egg-info > >>> Completed installing pylibmc-1.2.3 into /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/image/ > > built fine here. libmemcached 0.12 would be 2007-8 vintage. > > This > x86_64-pc-linux-gnu-gcc -pthread -march=athlon64 -pipe -fomit-frame-pointer > -O2 -fPIC -DUSE_ZLIB -I/usr/include/python2.6 -c _pylibmcmodule.c -o > build-2.6/temp.linux-x86_64-2.6/_pylibmcmodule.o -fno-strict-aliasing > > is the line where it trips. I can display the 'what' but certainly not the > 'why' > from above traceback; "token "@" is not valid in preprocessor expressions" > unless I'm missing something, > > # grep "@" > /mnt/gen2/TmpDir/portage/dev-python/pylibmc-1.2.3/work/pylibmc-1.2.3/ > {_pylibmcmodule.h,_pylibmcmodule.c} > > yields blank. In the build that fails the preprocessor expressions appear > to feature token '@', build in my system they're absent. Someone knowing > more than I can give this more meaning. I'm not sure what you're talking about here. As I already noted, it's from a bad m4 expansion (It never expanded). My above comment was a typo - 0.12 should be 1.0.12. The bug Patrick is hitting was notified upstream and was fixed in 1.0.13 (couldn't find the bug I filed in launchpad for whatever reason). You can find the patch at our bugzilla here: https://bugs.gentoo.org/show_bug.cgi?id=438166 Since we don't have 1.0.12 in tree, this bug should probably be closed anyway. Closing - libmemcached 1.0.12 not in tree and bug is filed against pylibmc. |