matplotlib-devel Mailing List for matplotlib

I was on the wx list a little and got some help, but no solutions.=20
Basically I get the same linker errors if I pass no wx libs, so mingw
is not finding any symbols in the libraries. It is not complaining
about the libraries either. Someone on the list said the c++ symbols
are mangled by visual studio, so the only way to get it to work is
compile _wxagg wil vs. Kinda hit a road block now.
On 1/7/06, Ken McIvor <mc...@ii...> wrote:
> On Jan 6, 2006, at 1:04 PM, Charlie Moad wrote:
> > I am now just using the provided wxPython2.6-win32-devel download
> > and getting the exact same error, after renaming all the .lib files to
> > .a.
>
> Curiouser and curiouser. I'll try to get to a windows machine later
> today and attempt to reproduce/diagnose the problem.
>
> > What version of wxPython was _wxagg originally built with?
>
> It was originally developed using version 2.5.3.1 under Mac OS 10.3.
>
> Ken
>

On Jan 6, 2006, at 1:04 PM, Charlie Moad wrote:
> I am now just using the provided wxPython2.6-win32-devel download
> and getting the exact same error, after renaming all the .lib files to
> .a.
Curiouser and curiouser. I'll try to get to a windows machine later 
today and attempt to reproduce/diagnose the problem.
> What version of wxPython was _wxagg originally built with?
It was originally developed using version 2.5.3.1 under Mac OS 10.3.
Ken

On Jan 6, 2006, at 12:11 PM, Charlie Moad wrote:
> Googling these errors hasn't led me to anything obvious.
> There are a lot of mentions of the vtable for xxx undefined
> references. Does anybody have any clues?
I was able to find one clear explanation of what g++ means when it 
starts carrying on about undefined references to vtables:
	http://gcc.gnu.org/ml/gcc-bugs/2002-09/msg00083.html
It sounds to me like a build environment problem, but I can't see any 
obvious problems in the output you pasted.
Ken