newpg won't compile (RANT!)

[John B]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 14 July 2003 07:52, John Aldrich wrote:
> On Monday 14 July 2003 03:13 am, Werner Koch wrote:
> > On Sun, 13 Jul 2003 22:04:10 -0400, John Aldrich said:
> > > I can't seem to get "newpg" to compile for me because it can't find
> > > libgcrypt-config, despite the fact that it's in the same bloody
> > > directory as
> >
> > You need to run "make install" for libgcrypt (as root), do an ldconfig
> > as the make output indicates and finally  make sure that
> > /usr/local/bin is in your $PATH.
>
> Werner, please re-read the section where I said I've been using linux for
> over 4 years now and building packages, etc for most of that. I *think* I
> know how to install a file. Granted, I prefer to use RPMs so that I can
> uninstall/upgrade, so I am using "checkinstall" to build / install, but I
> *am* doing it as root.

  I like checkinstall, but I've found that once in a while it doesn't seem =
to=20
'install' the rpm I had it make. I'd locate the libgcrypt rpm, and manually=
=20
do an rpm -Uvh libgcrypt.rpm (or newpg, whichever) on it just for the heck =
of=20
it, and then like another reply said, do an ldconfig, and a rhconfig (or=20
whatever the equivalent to my SuSEconfig is for RH).

  John
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/EsYpH5oDXyLKXKQRAh65AJ47Sq+mgSNqLwoYVnowJF+F0bOMWwCdHbcU
0XKzs8O6EOk0GC9emSyd+Lc=3D
=3Dlb2B
=2D----END PGP SIGNATURE-----