Dave Page wrote:
-----Original Message-----
From: Florian G. Pflug [mailto:[EMAIL PROTECTED]
Sent: 31 August 2006 16:00
To: Dave Page
Cc: pgadmin-hackers
Subject: Re: [pgadmin-hackers] Build fails on OSX using wx 2.7.0
*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..
Bah - that would have been my normal suggestion but I figured no,
Florian knows what he's doing :-p
Yeah, well, I've thought that too... ;-)
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...)
Yeah. They can include ppc64 as well. GCC will create them just fine, or
you can build them individually and combine the resulting executables
and libs using the lipo tool.
Hm.. So why not compile to versions of postgres, and combine the two
into one library? It's a bit hacky, but I guess it'd work for all libs
that pgadmin needs, and you don't have to got fix all libs...
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?
I haven't fully tested it, but last time I looked it didn't appear to be
much work to tweak for i386 binaries. Hopefully Universal will be
similarly simple.
Hm.. depends.. If the universal binary references a universal library,
in the same way that a ppc binary references a ppc lib, then it should
be easy...
If, on the other hand, you get two references, one for the ppc-part
referencing the ppc-part of the lib, and the same for the i386 parts,
then fixing complete-bundle.sh will be hard
greetings, Florian Pflug
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
