Subject: pkgsrc documentation, digest and undefined reference to `RMD160Init'
To: None <>
From: Jeremy C. Reed <>
List: tech-pkg
Date: 03/09/2001 12:02:30
Where is pkgsrc documented for telling the user that they need to update
certain things to use it (after updating via CVS)?

I have been following this digest thread for a few days.

Today, I tried building audio/vorbis and I received:

rainier:/usr/pkgsrc/audio/vorbis$ make
===> Cleaning for digest-20010302
===> Extracting for digest-20010302
===> Patching for digest-20010302
===> Configuring for digest-20010302
~===> Building for digest-20010302
cc -O2  -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wno-uninitialized -Wreturn-type -Wcast-qual -Wpointer-arith
-Wwrite-strings -Wswitch -Wshadow -Werror   -DVERSION=20010302
-DVERSION=20010302 -I/usr/pkg/pkgsrc/pkgtools/digest/work
cc  -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -Wl,-R/usr/pkg/lib -L/usr/pkg/lib
-static -o digest digest.o 
digest.o: In function `rmd160_digest_file':
digest.o(.text+0x15b): undefined reference to `RMD160Init'
digest.o(.text+0x170): undefined reference to `RMD160Update'
digest.o(.text+0x194): undefined reference to `RMD160End'
digest.o(.text+0x1b1): undefined reference to `RMD160File'
collect2: ld returned 1 exit status
*** Error code 1


(I am using 1.5.1_ALPHA under i386.)

$ ident ../../pkgtools/digest/Makefile 
     $NetBSD: Makefile,v 1.3 2001/03/07 07:43:00 tron Exp $

So I updated my pkgsrc (via anoncvs).

$ ident ../../pkgtools/digest/Makefile
     $NetBSD: Makefile,v 1.4 2001/03/07 23:03:19 kim Exp $

But I received the same "undefined reference to `RMD160..." errors.

As far as I know, there is not a current (development) tree and a stable
tree for pkgsrc. Why would the pkgsrc tree be available if it doesn't
work? (Can we have a development/testing tree for pkgsrc?)

I think that the documentation at needs to be
updated to explain to the pkgsrc user what they really need to do to use
it. Or maybe a paragraph can be added to the "Problems compiling
packages" section.

(Should I send-pr this?)

   Jeremy C. Reed