From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "isaac flemmin" <isaac(at)knox(dot)net> |
Cc: | "'Tim Barnard'" <tbarnard(at)povn(dot)com>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Linker Problems |
Date: | 2002-06-04 23:32:43 |
Message-ID: | 20058.1023233563@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
"isaac flemmin" <isaac(at)knox(dot)net> writes:
> Yes I did double check that line in ld.so.conf and it is okay. I even
> ran ldconfig -p to check the ld.so.cache file and see if the actual
> files from the directory were in the cache and they were. So I am rather
> confused as to why it will not link unless I specifically use -L to show
> the path.
AFAIR, ld.so.conf only affects the behavior of the dynamic loader.
You *also* need to persuade the compiler/linker to find the library
during link.
I believe gcc's default link search path can be configured if you're
willing to futz with its config file, but it might be a lot easier
just to drop the library in one of the standard places, eg,
/usr/local/lib...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretzer | 2002-06-05 06:03:15 | Re: lo_import problem under Windows+BCB5 |
Previous Message | isaac flemmin | 2002-06-04 22:15:34 | Re: Linker Problems |