On Fri, Apr 5, 2013 at 2:51 PM, Julian Taylor
wrote:
> I filed an issue:
> https://github.com/matplotlib/matplotlib/issues/1884
Go figure, it was an actual bug! Well, thanks a lot for tracking it down :)
I guess for now I'll just remove pycxx-dev from my system.
Fortunately I don't need it for
On 05.04.2013 23:35, Julian Taylor wrote:
> On 05.04.2013 23:16, Fernando Perez wrote:
>> On Fri, Apr 5, 2013 at 1:49 PM, Julian Taylor
>> wrote:
>>
>>> strange, it isn't linked against libpng at all. I can't reproduce that
>>> on my Ubuntu machine with git head.
>>>
>>> Do you still have a buildl
On 05.04.2013 23:16, Fernando Perez wrote:
> On Fri, Apr 5, 2013 at 1:49 PM, Julian Taylor
> wrote:
>
>> strange, it isn't linked against libpng at all. I can't reproduce that
>> on my Ubuntu machine with git head.
>>
>> Do you still have a buildlog?
>> Maybe do a new build from a clean folder (a
On Fri, Apr 5, 2013 at 1:49 PM, Julian Taylor
wrote:
> strange, it isn't linked against libpng at all. I can't reproduce that
> on my Ubuntu machine with git head.
>
> Do you still have a buildlog?
> Maybe do a new build from a clean folder (and save the log).
I just did a fully clean rebuild in
On 05.04.2013 22:32, Fernando Perez wrote:
> On Fri, Apr 5, 2013 at 10:06 AM, Julian Taylor
> wrote:
>>
>> whats the output of:
>> ldd
>> /home/fperez/usr/opt/lib/python2.7/site-packages/matplotlib-1.3.x-py2.7-linux-x86_64.egg/matplotlib/_png.so
>> apt-cache policy libpng12-dev
>>
>> the system li
On Fri, Apr 5, 2013 at 10:06 AM, Julian Taylor
wrote:
>
> whats the output of:
> ldd
> /home/fperez/usr/opt/lib/python2.7/site-packages/matplotlib-1.3.x-py2.7-linux-x86_64.egg/matplotlib/_png.so
> apt-cache policy libpng12-dev
>
> the system libpng in ubuntu 12.10 does have this symbol defined, ma
On 05.04.2013 07:37, Fernando Perez wrote:
> Well, I'm using the system libpng, which is what puzzles me: there
> should be no need for me to modify my LD_..., and I haven't done so in
> the past. I'll have to dig into the build tomorrow to figure out
> exactly what's going on there...
>
whats t
I've had problems like this using a git-source matplotlib and macports.
This usually happens after libpng is upgraded.
Turns out a 'python setup.py install ...' in matplotlib will not solve
things until you manually delete the contents of the matplotlib build/
directory. After which new go at s
