Linking problems on T64 UNIX 4.0F

From: Nikola Milutinovic <Nikola.Milutinovic_at_ev.co.yu>
Date: Fri, 25 Aug 2000 08:18:07 +0200

Hi all.

Arch: Alpha Station 200 4/233
OS: Tru64 UNIX 4.0F
PK: Patch Kit 4

I was installing Berkeley DB 3.0.55, this went OK. Then I tried
installing Cyrus SASL 1.5.24. During "configure" phase, I was greeted
with "No Berkeley DB support" - "disabling SASL DB". So, I started
digging...

The first thing to do was to figure out what the test was. Test was a
linking attempt, which I made to be:

test.c
------
char db_open();

int main() {
  db_open();
  return 0;
  }
------

cc test.c -ldb

After a lot of fiddling around, I realized that the OS libdb.* files in
default directories were interfering, so I moved them and placed (links)
Berkeley DB files, instead. Cyrus SASL still woed. Then I started
playing with "ld".

# cc -shared -c test.c
# ld -L -L/usr/local/BerkeleyDB.3.0/lib -ldb test.o
ld:
Error: Undefined:
db_create
# cc -shared test.c -ldb
# odump -Dl a.out


                        ***LIBRARY LIST SECTION***
        Name Time-Stamp CheckSum Flags Version
a.out:
        libdb-3.0.so Aug 24 14:01:34 2000 0x2e3bea79 0
        libc.so Feb 24 22:19:15 2000 0xbad758ae 0 osf.1

So, "cc" links OK, creates a shared object OK. "ld" woes. I've been
talking to Sleepy Cat (Berkeley DB) representative, who took my case and
he is as puzzled, as I am.

--------

Anyway, the test is going through OK and was able to build SASL, but
this was a rather frustrating experience and we would both like to know
what was bugging us (the guy from Sleepy Cat managed to reproduce the
error).

Anybody can shed some light?

Nix.
-- 
I Used up all my sick days, so I'm calling in dead.
Received on Fri Aug 25 2000 - 06:17:41 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT