David Brownlee wrote:
> 
> On Wed, 16 May 2001, Nick Hudson wrote:
> 
> > > > > ===> [Automatic a.out shared object handling]
> > > > > ls: /usr/X11R6/lib/libgck.so: No such file or directory
> > > > > ls: /usr/X11R6/lib/libgimp.so: No such file or directory
> > > > > ls: /usr/X11R6/lib/libgimpui.so: No such file or directory
> > > > > ===> Registering installation for gimp-1.2.1
> > > > > pkg_create: can't stat `/usr/X11R6/lib/libgck.so'
> > > > > pkg_create: can't stat `/usr/X11R6/lib/libgimp.so'
> > > > > pkg_create: can't stat `/usr/X11R6/lib/libgimpui.so'
> > > > >
> > > > > % ls /usr/X11R6/lib/libgck*
> > > > > /usr/X11R6/lib/libgck-1.2.so.0.1        /usr/X11R6/lib/libgck.la
> > > > > /usr/X11R6/lib/libgck.a                 /usr/X11R6/lib/libgck.so.0.1

> > After refreshing my memory I would expect to see symlinks for these
> > libraries that correspond to the missing PLIST entries. Do you have the
> > build log to hand? I am building gimp on my CATS at the moment, but that
> > may take some time.
> 
>         Sorry, no log. If a shark is any faster than your CATS then I
>         should have one soonish :)

No matter. I'm setting up a 1.4.x/i386 chroot environment on my PIII 650
which will help.

>         Why would there be symlinks for the missing PLIST entries -
>         something like jpeg installs /usr/pkg/lib/libjpeg.so.62.0
>         without any /usr/pkg/lib/libjpeg.so ?

OK. The refresh only partially completed. :-)

There is a symlink in the libtool -release case, but not the missing
entries. In the libgck example above I expect
/usr/X11R6/lib/libgck.so.0.1 to be a symlink to
/usr/X11R6/lib/libgck-1.2.so.0.1

The problem is definitely in the automatic shlib handling. I should have
a fix soon.

Nick
-- 
aka skrll@netbsd.org, skrll@excite.co.uk