Re: [Matplotlib-users] ft2font error while building with python3 support

[Friedrich R. <fri...@gm...>]

2011/11/24 Ignas Anikevicius <ani...@gm...>:
> I have probably found out the cause in the difference. The relevant
> part of the log for the Python 2.7 build:
> ---------------------------
> running build_ext
> building 'matplotlib.ft2font' extension
> creating build-2.7/temp.linux-x86_64-2.7
> creating build-2.7/temp.linux-x86_64-2.7/src
> creating build-2.7/temp.linux-x86_64-2.7/CXX
> x86_64-pc-linux-gnu-g++ -pthread -march=native -O2 -fno-strict-aliasing
> -fPIC -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1
> -I/usr/local/include -I/usr/include
> -I/usr/lib64/python2.7/site-packages/numpy/core/include
> -I/usr/include/freetype2 -I/usr/include -I. -I/usr/include/python2.7 -c
> src/ft2font.cpp -o build-2.7/temp.linux-x86_64-2.7/src/ft2font.o
> ---------------------------
>
> And know for the Python 3.2 build:
> ---------------------------
> running build_ext
> building 'matplotlib.ft2font' extension
> creating build-3.2/temp.linux-x86_64-3.2
> creating build-3.2/temp.linux-x86_64-3.2/src
> ---------------------------
> <<< !!!!!!!!!!!!!!!!!!!!!!!!!!!!!missing line
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>>>
> ---------------------------
> x86_64-pc-linux-gnu-g++ -pthread -march=native -O2 -fPIC
> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1
> -DPYCXX_PYTHON_2TO3=1 -I/usr/local/include -I/usr/include
> -I/usr/lib64/python3.2/site-packages/numpy/core/include
> -I/usr/include/freetype2 -I/usr/include -I. -I/usr/include/python3.2 -c
> src/ft2font.cpp -o build-3.2/temp.linux-x86_64-3.2/src/ft2font.o
> ---------------------------
>
> Note that there is a missing line for the 3.2 build as it does not
> create the build-3.2/temp.linux-x86_64-3.2/CXX directory.
>
> Hence, my question is whether this behaviour is due to some code in
> the MPL building system, or should I research my ebuild more?

Good research!  Unfortunately, this beyond my level.  Keep us posted.
I would suspect some bug in distutils, but this can be completely off.
  Normally the obvious guesses are rather wrong in such cases as this.

How does the ebuild work?  Does it invoke setup.py?  If yes, maybe
matplotlib installs the CXX dir s.t. it does not work for py3k?  Maybe
just the attribute matplotlib is monkeypatching. if at all, changed
its name?  All this ideas do not claim that they explain it, they just
are meant to help you being let to the real cause of the malfunction.

Good luck, and a lot of inspiration
Friedrich

P.S.: "Luck – has nothing to do with it.  Faith, and hard work, girl,
'cause I'll be damned if ..." [Final Fantasy]