On Fri, 10 Jan 2003, James K. Lowden wrote:

> To save time I tried the bash VAX binary package.  It installed fine, but
> didn't run.  I don't know what the policy is, so I thought I should
> mention it here.
>
> Building bash from pkgsrc (which took sup(1) many hours to create, and cc
> a couple more), I now have a binary that looks like this:
>
> $ ldd `which bash`
> /usr/pkg/bin/bash:
>          -ltermcap.0 => /usr/lib/libtermcap.so.0
>          -lintl.0 => /usr/lib/libintl.so.0
>          -lc.12 => /usr/lib/libc.so.12
>
> but last night, the report looked like this (from memory):
>
>          -ltermcap.0 => libtermcap.so.0
>          -lintl.0 => libintl.so.0
>          -lc.12 => libc.so.12
>
> As you might guess, ld.so complained about not finding libtermcap.so.0.4,
> because the default ld.so.conf has only "/usr/local/lib".
>
> Is the package wrong, or am I expected to reconfigure my machine?

At least on the system where the package was originally built, it looks
alright.  And just now I've downloaded and manually unpacked the
tarball.  Running ldd on the "bash" binary within it results in the
following:

  radiant# gzip -dc bash-2.05nb1.tgz | tar xvf -
  +CONTENTS
  +COMMENT+DESC
  +MTREE_DIRS
  +BUILD_VERSION
  +BUILD_INFO
  +SIZE_PKG
  +SIZE_ALL
  bin/bash
  bin/bashbug
  man/man1/bash.1
  man/man1/bashbug.1
  info/bash.info
  share/doc/bash/article.ps.gz
  share/doc/bash/article.txt
  share/doc/bash/bashref.ps.gz
  share/doc/html/bash/bash.html
  share/doc/html/bash/bashref.html
  radiant# cd bin
  radiant# ldd ./bash
           -ltermcap.0 => /usr/lib/libtermcap.so.0
           -lintl.0 => /usr/lib/libintl.so.0
           -lc.12 => /usr/lib/libc.so.12
  radiant#

I /think/ it's okay.  But I'll go through the process of removing and
reinstalling the package on my system, to double-check, when I get home.

-brian.