On Tue, Jan 27, 2009 at 7:09 AM, Marcin Krol <mrk...@gmail.com> wrote: > John Hunter wrote: >> It might help if you recursively remove the buld directory, do a clean >> rebuld, capture the build output in a file, and post that here so we >> can see if we can get an idea what is going on > > Since it's over 250kB, I pasted it here: > > http://pastebin.com/f466bd0db
First of all, on the clean build, when you do import matplotlib._path do you still get the same error. I don't know a ton about windows and even less about visual studio, but according to the build output you posted a _path.pyd file is built and apparently installed. It may be that it is trying to linking against some dll that is not on your system. There is a windows freeware program I used to use to debug this stuff, in which you could load the pyd file and see what it links against, which reported failures. Perhaps a windows guru can advise here. In the past, there was a bug in distutils that was forcing the compiler to link against msvcp71.dll which could be fixed by patching distutils. Don't know if this is related ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
