Subject: Re: Is ldconfig b0rken?
To: Research Labs. <wgu@research-labs.co.uk>
From: Lubomir Sedlacik <salo@Xtrmntr.org>
List: port-sparc
Date: 06/08/2005 13:35:44
--8M+gQFKLhTGBxzRu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 08, 2005 at 12:16:10PM +0100, Research Labs. wrote:
> I'm running an SMP NetBSD 2.0.2 on an SS20 and I've just compiled
> pglogd when trying to start the daemon it said it couldn't find
> libpq.so.3, so I did an ldconfig -m /usr/local/pgslq/lib and
> re-executed the daemon but I got the same error.
>=20
> I know this approach works as I did it only yesterday on an OpenBSD
> box for the same daemon, which leads me to suspect ldconfig may have a
> problem.
>=20
> Can anyone shed some light on this?

ldconfig on NetBSD is used only for a.out libraries.  you seem to
link pglogd without providing suitable rpath.  see ld(1) for details
about -R and -rpath flags.


regards,

--=20
-- Lubomir Sedlacik <salo@{NetBSD,Xtrmntr,silcnet}.org>   --

--8M+gQFKLhTGBxzRu
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFCptgPiwjDDlS8cmMRAmmlAJ4pHYiS7ENBNiC00Y2U+eOI/0zelgCfVWFW
rwKIOEoYzyPeBs6TdWa/PbE=
=TxSF
-----END PGP SIGNATURE-----

--8M+gQFKLhTGBxzRu--