Hi,

Thanks for your reply.

On 24/11/11 18:54, Friedrich Romstedt wrote:
>...
> building on a Mac. Did you modify CFLAGS or CC?
>

There was in the ebuild some additional flags like
fno-strict-aliasing, but nothing change by removing the aditional
flags. The strange thing is that it still builds for 2.7, but not for
3.2.

>...
>...
> I actually don't know if it'll work if you say e.g. pythonX.Y
> matplotlib.git/setup.py build ...... might be an mistake in either
> distutils or the matplotlib build engine which I don't know at all (if
> there are additions from the mpl side to building at all.....). If
> I'm right a ``cd ........./matplotlib`` should do the trick. :-)


It did not help :(...

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?

Cheers,
Ignas A.

--
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?