I built postgresql 6.5.2 for SGI IRIX 6.x systems, and ran into a few
problems.  I've have diffs if anyone needs them, but they all boil down
to files in src/interfaces/odbc that use C++ comments in C code.  I
built --without-CXX because libpq++ requires "<string>", and so can only
be built with g++.

Some potentially serious warnings from the compiler:
"gist.c", line 716: warning(1551): variable "tmpentry" is used before
its
          value is set
                                   (OffsetNumber) 0, tmpentry.bytes, FALSE);
                                                     ^
"ipc.c", line 264: warning(1551): variable "semun" is used before its
value is
          set
        semctl(semId, 0, IPC_RMID, semun);
                                   ^

"ipc.c", line 428: warning(1551): variable "semun" is used before its
value is
          set
                semctl(semId, 0, IPC_RMID, semun);
                                           ^

"ipc.c", line 526: warning(1551): variable "dummy" is used before its
value is
          set
        semncnt = semctl(semId, sem, GETNCNT, dummy);
                                              ^

"ipc.c", line 536: warning(1551): variable "dummy" is used before its
value is
          set
        semval = semctl(semId, sem, GETVAL, dummy);
                                            ^

"info.c", line 2142: warning(1551): variable "htbl_stmt" is used before
its
          value is set
                SQLFreeStmt(htbl_stmt, SQL_DROP);
                            ^

There were some "pointless comparison of unsigned integer with zero"
messages too.  The linker also whined because fmgr_pl_finfo is multiply
defined, as are CacheCxt and various yacc symbols.

I also had some regression failures:
- int2, int4: error message was "Result too large" instead of
  "Numerical result out of range"
- geometry: "0" appears where "-0" was expected, rounding differences.
- abstime, tinterval, horology: timezone problems (PST vs. PDT)
- oidjoins, type_sanity: lots of differences cause by
  "ERROR:  typeidTypeRelid: Invalid type - oid = 0" messages.
- opr_sanity: "ERROR:  Unable to locate type oid 0 in catalog" diffs.
- random: "ERROR:  typeidTypeRelid: Invalid type - oid = 0" followed
  by "ERROR:  random_tbl: Table does not exist." diffs.
- misc: random_tbl missing from user_relns
- rules: the final two queries returned empty results.

Are these particular tests supposed to succeed?

        Thanks,
        David

PS: I'm not on the mailing list, so please include me on any replies.

-- 
David KAELBLING <[EMAIL PROTECTED]>       Silicon Graphics Computer Systems
1 Cabot Rd, suite 250; Hudson, MA 01749     781.839.2157, fax ...2357

Reply via email to