Re: odbc/UnixWare 7.1.1: No Go. - Mailing list pgsql-hackers
From | Larry Rosenman |
---|---|
Subject | Re: odbc/UnixWare 7.1.1: No Go. |
Date | |
Msg-id | 20010322.20542200@ler-freebie.iadfw.net Whole thread Raw |
In response to | Re: odbc/UnixWare 7.1.1: No Go. (Peter Eisentraut <peter_e@gmx.net>) |
Responses |
Re: odbc/UnixWare 7.1.1: No Go.
(Tom Lane <tgl@sss.pgh.pa.us>)
|
List | pgsql-hackers |
My question is WHY are we using -Bsymbolic and/or -z text anyway? These options don't appear to buy us anything but grief on SVR[45] ELF systems.. The -lpq is NOT needed, that was my f*** up. LER >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/22/01, 2:50:53 PM, Peter Eisentraut <peter_e@gmx.net> wrote regarding Re: [HACKERS] odbc/UnixWare 7.1.1: No Go. : > Larry Rosenman writes: > > need to kill the _init too. Then we get other symbol issues, I think due > > to -Wl,z,text, but I'm not sure. > These look to be due to the -Bsymbolic. Note they're only warnings, but > you could really only tell by trying out the driver. I have a slight > suspicion that -z text plus -Bsymbolic is an idiosyncratic combination, > but I might be off. > > > > ar crs libpsqlodbc.a `lorder info.o bind.o columninfo.o connection.o > > convert.o drvconn.o environ.o execute.o lobj.o misc.o options.o pgtypes.o > > psqlodbc.o qresult.o results.o socket.o parse.o statement.o gpps.o > > tuple.o tuplelist.o dlg_specific.o | tsort` > > UX:tsort: WARNING: Cycle in data > > UX:tsort: INFO: results.o > > UX:tsort: INFO: parse.o > > UX:tsort: INFO: info.o > > UX:tsort: WARNING: Cycle in data > > UX:tsort: INFO: execute.o > > UX:tsort: INFO: environ.o > > UX:tsort: INFO: dlg_specific.o > > UX:tsort: INFO: convert.o > > UX:tsort: INFO: connection.o > > UX:tsort: INFO: results.o > > UX:tsort: INFO: parse.o > > UX:tsort: INFO: statement.o > > UX:tsort: INFO: bind.o > > UX:tsort: WARNING: Cycle in data > > UX:tsort: INFO: execute.o > > UX:tsort: INFO: environ.o > > UX:tsort: INFO: dlg_specific.o > > UX:tsort: INFO: convert.o > > UX:tsort: INFO: connection.o > > UX:tsort: INFO: results.o > > UX:tsort: INFO: qresult.o > > UX:tsort: INFO: columninfo.o > > : libpsqlodbc.a > > cc -G -Wl,-z,text -Wl,-h,libpsqlodbc.so.0 -Wl,-Bsymbolic info.o bind.o > > columninfo.o connection.o convert.o drvconn.o environ.o execute.o lobj.o > > misc.o options.o pgtypes.o psqlodbc.o qresult.o results.o socket.o > > parse.o statement.o gpps.o tuple.o tuplelist.o dlg_specific.o -lm > > -Wl,-R/usr/local/pgsql/lib -o libpsqlodbc.so.0.26 > > Undefined first referenced > > symbol in file > > close socket.o > > strcat info.o > > getpwuid misc.o > > atof connection.o > > atoi info.o > > atol convert.o > > malloc info.o > > labs tuplelist.o > > strchr info.o > > ldexpf libm.so > > ldexpl libm.so > > fgets gpps.o > > strcmp info.o > > strstr info.o > > _lib_version libm.so > > strcasecmp convert.o > > _modf libm.so > > strcpy info.o > > memcpy convert.o > > strlen info.o > > __ctype convert.o > > strrchr results.o > > strtok info.o > > modff libm.so > > modfl libm.so > > time convert.o > > localtime convert.o > > multibyte_char_check convert.o > > __thr_errno libm.so > > getpid misc.o > > sprintf info.o > > setbuf misc.o > > inet_addr socket.o > > multibyte_strchr convert.o > > strdup columninfo.o > > strncasecmp convert.o > > getuid misc.o > > check_client_encoding connection.o > > ldexp libm.so > > realloc info.o > > multibyte_init convert.o > > fclose gpps.o > > fopen misc.o > > strncat convert.o > > strncpy connection.o > > gethostbyname socket.o > > strncmp info.o > > sscanf connection.o > > vfprintf misc.o > > free info.o > > _write libm.so > > ilogb libm.so > > frexpl libm.so > > UX:ld: WARNING: Symbol referencing errors. > > rm -f libpsqlodbc.so.0 > > ln -s libpsqlodbc.so.0.26 libpsqlodbc.so.0 > > rm -f libpsqlodbc.so > > ln -s libpsqlodbc.so.0.26 libpsqlodbc.so > > > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > > > On 3/22/01, 12:23:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote regarding Re: > > [HACKERS] odbc/UnixWare 7.1.1: No Go. : > > > > > > > Larry Rosenman <ler@lerctr.org> writes: > > > > Does this mean it's eligible to be fixed for 7.1? > > > > > We can talk about it anyway. Does removing the _fini alone make it work > > > for you, or do we have to remove _init too? > > > > > regards, tom lane > > > > > -- > Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
pgsql-hackers by date: