Wed Apr 16 08:49:18 PDT 2008
- Previous message: [Slony1-general] Slony 1.2.x on HP-UX 11.23 IA-64
- Next message: [Slony1-general] Slony 1.2.x on HP-UX 11.23 IA-64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Ed L." <pgsql at bluepolka.net> writes: > Building with gcc (and CFLAGS="-mlp64" LDFLAGS="-mlp64) results > in the exact same error output. If I built pg with ANSI C > compiler using "+DD64", is there any dependency requiring me to > build slony with the same compiler since it links with pg's > libs? Or should their end results be compatible due to same > architecture? Vendors (and GCC porters) try pretty hard, often with reasonable success, to have binary interoperability between C compilers. We can often use AIX libraries built using IBM's VisualAge C with programs compiled using GCC. The same is usually *not* true for C++; there's usually enough gross name mangling behind the scenes that tends to vary based on compiler strategy that linking programs compiled with one C++ compiler against libs compiled with another often doesn't work. (Indeed, it often doesn't work if the two compilers are varying versions of G++...) All that being said, I'd really want to use the same compiler to build Slony-I that I used to build PostgreSQL, particularly if the difference looked like it might be causing problems. -- (format nil "~S@~S" "cbbrowne" "cbbrowne.com") http://linuxfinances.info/info/linuxxian.html They have finally found the most ultimately useless thing on the web... Found at the Victoria's Secret website: "The online shop: Text Only Listing"
- Previous message: [Slony1-general] Slony 1.2.x on HP-UX 11.23 IA-64
- Next message: [Slony1-general] Slony 1.2.x on HP-UX 11.23 IA-64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list