On Tue, 19 Nov 2002 16:45:58 -0500 (EST) Scott <[EMAIL PROTECTED]> wrote:
S> > Why did you use gcc2 together with gcc3? Thsi is just asking for S> > trouble. S> > Use one compiler for compiling *and* linking anything. S> S> I am sorry.. I should have been more clear. I used gcc3, when that failed S> I tried gcc2 and cleaning out the source. I did not mix gcc2 & gcc3 S> compiled code into one. gcc3 is the default with jaguar. Well, I had a look at the nm output and the library definitely was compiled by a different compiler. E.g. the first missing symbol is wxWindowBase::AddChild() or, mangled in the linker error message, _AddChild__12wxWindowBasePB0. This method is in the library but there it is mangled as __ZN12wxWindowBase8AddChildEPS_ -- no surprize the linker doesn't understand that it's the same symbol! The latter mangling scheme is gcc3 but the former one is gcc2. So, once again, you should rebuild M with the same compiler you used for wxWin (gcc3). In general, you can't link together programs and libraries compiled with different compilers. Regards, VZ ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
