Dave Page wrote:
>>-----Original Message-----
>>From: pgadmin-hackers-owner@postgresql.org
>>[mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
>>Florian G. Pflug
>>Sent: 31 August 2006 09:35
>>To: pgadmin-hackers
>>Subject: [pgadmin-hackers] Build fails on OSX using wx 2.7.0
>>
>>ld: Undefined symbols:
>>wxString::mb_str(wxMBConv&) const
>>wxString::wxString(char const*, wxMBConv&, unsigned long)
>>wxWindow::SetTitle(wxString const&)
>>wxWindow::GetTitle() const
>>wxFont::Init()
>>make[2]: *** [pgadmin3] Error 1
>>make[1]: *** [all-recursive] Error 1
>>make: *** [all] Error 2
>>
>>Any ideas what might be going on?
>
> Nope that's really odd - but I found a problem on Mac late last night so
> am hacking on it later today when I've finished with psqlODBC. Can you
> wait until I'm happy with the build here before we debug yours?
Sure.. but note that I'm be on vacation for 3 weeks starting on sunday -
so it's note rudeness if I don't answer my mails in the coming weeks ;-)
Still, I debugged this further, and though I's share the results, even
if you don't have time at the moment.
"otool -t -v ~/Installs/wxMac/2.7.0/lib/libwx_base_carbonu-2.7.a | grep
mb_str | c++filt"
gives:
wxString::mb_str(wxMBConv const&) const
Note that additional "const" flag for the wxMBConv argument. I never
knew that const-modifiers are recorded in c++ mangled names - but
it seems they are, and it seems that this is causing the trouble..
I've absolutly no idea yet why c++ uses the signature including "const"
when compiling wx, but the one without "const" when linking against it...
My build server is still running 10.3.9, btw, with gcc 3.3 - so I guess
it's this version of gcc causing the trouble..
> As an extra benefit to fixing the problem I found, we should also be
> building Universal binaries by the time I've finished :-)
Cool! How did you archive that?
greetings, Florian Pflug
