Wayne,
Comments inlined " || " below.
- Ross
-----Original Message-----
<snip>
When trying to build all 3 as 32-bit, I get this when building postgresql: ./configure --prefix=/scratch/slocal/schroede/test2/pgsql --enable-odbc --without-readline gmake
/usr/bin/ld: Relocatable linking with relocations from format elf32-i386
(heaptuple.o) to format elf64-x86-64 (SUBSYS.o) is not supported
gmake[4]: *** [SUBSYS.o] Error 1
gmake[3]: *** [common-recursive] Error 2
gmake[2]: *** [access-recursive] Error 2
gmake[1]: *** [all] Error 2
gmake: *** [all] Error 2
|| I do believe you'll eventually need to tell your linking-loader/ld that you
are trying to do 32-bit as well. For me, the flag is "-b32".
When I try to build postgresql 64-bit and odbc 32-bit, postgresql builds fine, but I get this when trying odbc: ./configure --prefix=/scratch/slocal/schroede/test2/pgsql --enable-static gmake
/usr/bin/ld: warning: i386 architecture of input file `info.lo' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `bind.lo' is incompatible with i386:x86-64 output and the same warning for: columninfo.lo, connection.lo, convert.lo, drvconn.lo, environ.lo, execute.lo, lobj.lo, win_md5.lo, misc.lo options.lo, pgtypes.lo, psqlodbc.lo, qresult.lo, results.lo, socket.lo, parse.lo, statement.lo, tuple.lo, tuplelist.lo, dlg_specific.lo, odbcapi.lo, multibyte.lo, gpps.lo, odbcapi30.lo, pgapi30.lo, and info30.lo. Those are warnings, but apparently it makes the library 64-bit because then when it tries to link my MCAT/SRB app, I get: gmake
/usr/bin/ld: skipping incompatible /scratch/slocal/schroede/test2/pgsql/lib/libpsqlodbc.a when searching for -lpsqlodbc
/usr/bin/ld: cannot find -lpsqlodbc
collect2: ld returned 1 exit status
So is this second mode, 64 bit postgresql and 32 bit odbc, that I should try to get working? Or would the all-32-bit have a better chance?
|| same comment as above. specify in LDFLAGS. configure/gmake should pick it up and pass to ld correctly...
Am I the only one with this 32/64-bit problem?
|| nope.
We will convert our app to 64-bit sometime, but if there is a fairly easy workaround for now, I'd like to make use of it. Otherwise, we'll just continue to say we can't support MCAT on 64-bit linux boxes (for now).
|| The Force has power over weak minds.
- Wayne -
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
