FireBurn / Overlay

Gentoo Overly
GNU General Public License v3.0
21 stars 6 forks source link

lcms-1.19-r2 and python issues #48

Closed pjansen33621 closed 8 years ago

pjansen33621 commented 11 years ago

I tried installing emul-linux-x86-baselibs package but have been having issues with building lcms-1.19-r2. I get an error dealing with LONG_BIT during the python portion of the compile.
In file included from /usr/include/python3.3/Python.h:8:0, from /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx:154: /usr/include/python3.3/pyconfig.h:1207:0: warning: "SIZEOF_LONG" redefined [enabled by default]

define SIZEOF_LONG 8

^

:0:0: note: this is the location of the previous definition In file included from /usr/include/python2.7/Python.h:8:0, from /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx:154: /usr/include/python2.7/pyconfig.h:1004:0: warning: "SIZEOF_LONG" redefined [enabled by default] #define SIZEOF_LONG 8 ^ :0:0: note: this is the location of the previous definition In file included from /usr/include/python3.3/Python.h:50:0, from /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx:154: /usr/include/python3.3/pyport.h:820:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." ^ In file included from /usr/include/python2.7/Python.h:58:0, from /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx:154: /usr/include/python2.7/pyport.h:886:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." ^ /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx: In function 'void init_lcms()': /var/tmp/portage/media-libs/lcms-1.19-r2/work/lcms-1.19/python/lcms_wrap.cxx:34371:58: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] lcmsError = PyErr_NewException("lcms.error", NULL, NULL); ^
pjansen33621 commented 11 years ago

I tested compiling just 64 bit or 32 bit and the 64 bit only build compiled but the 32 bit build failed with the same error as above.
edit: I was able to get it to build by disabling python.

FireBurn commented 11 years ago

I might need to restrict python on the 33bit builds On 15 Oct 2013 23:42, "Peter Jansen" notifications@github.com wrote:

I tested compiling just 64 bit or 32 bit and the 64 bit only build compiled but the 32 bit build failed with the same error as above.

— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/issues/48#issuecomment-26379086 .

FireBurn commented 11 years ago

32 even On 16 Oct 2013 08:36, mike@fireburn.co.uk wrote:

I might need to restrict python on the 33bit builds On 15 Oct 2013 23:42, "Peter Jansen" notifications@github.com wrote:

I tested compiling just 64 bit or 32 bit and the 64 bit only build compiled but the 32 bit build failed with the same error as above.

— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/issues/48#issuecomment-26379086 .

Displacer commented 11 years ago

I have the same issue for x86_64 build

FireBurn commented 11 years ago

Can you send the build log? On 14 Nov 2013 10:03, "Displacer" notifications@github.com wrote:

I have the same issue for x86_64 build

— Reply to this email directly or view it on GitHubhttps://github.com/FireBurn/Overlay/issues/48#issuecomment-28472002 .

Displacer commented 11 years ago

sorry, it is for x86, is build log steel needed?

Haifen commented 10 years ago

Multilib support for Python is in the works as per the Multilib porting status page on the Gentoo Wiki, but not there yet. One option would be to not build in Python support for the abi_x86_32 build, but then the package could end up advertizing support for Python to 32-bit/multilib ebuilds when in fact it's not there. This isn't too major of a problem as I don't have any packages on my system that simultaneously have media-libs/lcms (with or without [python]) in their ${DEPEND} and abi_x86_32 in their IUSE, so that may be a reasonable option while we wait for Python Multilib support.