Re: Build fails on OSX using wx 2.7.0

Dave Page wrote:
>>-----Original Message-----
>>From: Florian G. Pflug [mailto:fgp(at)phlo(dot)org]
>>Sent: 31 August 2006 15:14
>>To: Dave Page
>>Cc: pgadmin-hackers
>>Subject: Re: [pgadmin-hackers] Build fails on OSX using wx 2.7.0
>>
>>Dave Page wrote:
>>
>>>>-----Original Message-----
>>>>From: pgadmin-hackers-owner(at)postgresql(dot)org
>>>>[mailto:pgadmin-hackers-owner(at)postgresql(dot)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..

*Putting brown paper bag over my head*. Arg! Forget it, it was not
g++ that is buggy, it turned out that the biggest bug was sitting
*in front* of the computer...

I've "make clean"-ed the wrong sourcetree, so my pgadmin3-trunk tree
still contained some old object files built against 2.6.3...
I've now cleaned my tree, and am in the process of recompiling...

Sorry for the noise and confusion..

> Quite possibly. I've been successfully building on Tiger with 2.7 for a
> week or two. The problem I found last night is that the wx-config
> --rezflags option is deprecated in 2.7, thus preventing a non-debug
> appbundle working. Fixed that (used --rescomp instead), but then found
> that wx 2.7 has a --enable-universal_binary option which I've been
> battling with ever since. I've got pgAdmin to compile, but it won't link
> because my PG is not Universal. I can't for the life of me get that to
> build though (although there is a precompiled 8.1.3 on the net, but the
> configure line from that didn't work for me)

Interesting.. So "universal binaries" actually contain both i386 and ppc
code in one file? I've always though that universion apps just contain
two different binaries for both architectures (One in "MacOS", and one
in "MacOS86" or such...)

> Anyhoo, when I've figured out how to build PostgreSQL, we should be good
> to go. In the meantime though, I can't believe wx dropped support for
> Panther. Do the samples build and run OK?

Hm.. I think that complete-bundle.sh will need some work to "do the
right thing" for universal binaries - Or have you already found a
solution for that?

greetings, Florian Pflug