Summary: | dev-libs/boost-1.57.0: fails to build with app-eselect/eselect-python-20151117-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gangræna Gorgeous <trupanka> |
Component: | [OLD] Library | Assignee: | C++ Team [disbanded] <cpp+disabled> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bugs, franz.trischberger, jstein, python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
emerge --info |
Description
Gangræna Gorgeous
2015-12-12 09:51:52 UTC
Created attachment 419022 [details]
build.log
I can confirm the issue with trying to build boost, for me version dev-libs/boost-1.56.0-r1 though. I tried to mask eselect-python-20151117-r1 and use an older one, but the older one conflicts with python-exec-2.1 which you definitely should NOT unmerge (breaks emerge command)... Which python versions do you have installed? Which pyhton did you eselect? I am not able to reproduce it here. Same issue here. Installed python versions: 2.7.11 and 3.4.3-r5 eselected python version is 3.4 IMHO the issue could be the location of the pyconfig.h from the 3.4 install: /usr/include/python3.4m/pyconfig.h Note the "m" in the version. Created attachment 419136 [details]
emerge --info
The issue is python itself. $ python3.4-config --includes -I/usr/include/python3.4 -I/usr/include/python3.4 There is no "python3.4m" in that line, so boost passes that wrong line to the compiler. Eeek, sorry for the noise... Fired the command on the wrong terminal, the laptop does not yet have the update to "python:3.4/3.4m". On the already updated machine the command returns valid include dirs: $ python3.4-config --includes -I/usr/include/python3.4m -I/usr/include/python3.4m *** This bug has been marked as a duplicate of bug 565090 *** |