pkg_libchk(1) error

[Janos Dohanics]

On Wed, 18 Oct 2017 17:45:03 -0500
Adam Vande More <amvandemore at gmail.com> wrote:

> [...]
> > # mount
> > zroot on / (zfs, local, noatime, nfsv4acls)
> > devfs on /dev (devfs, local, multilabel)
> > data on /data (zfs, local, nfsv4acls)
> > data/VirtualBoxVMs on /data/VirtualBoxVMs (zfs, local, nfsv4acls)
> > data/almaviva_backup on /data/almaviva_backup (zfs, local,
> > nfsv4acls) data/cortina_cyrus on /data/cortina_cyrus (zfs, local,
> > nfsv4acls) data/cortina_spool on /data/cortina_spool (zfs, local,
> > nfsv4acls) data/maillogs on /data/maillogs (zfs, local, nfsv4acls)
> > data/music on /data/music (zfs, local, nfsv4acls)
> > data/win_images on /data/win_images (zfs, local, nfsv4acls)
> >
> 
> I doubt it is the port that is outputting that error message so you
> can try trying it under truss(1) -f to find out what is.

Well, truss(1) -f generated a file which is about 550 MB, I'll upload
it somewhere if you want to see it...

> What is the point of that tool and why is it better than bases's
> pkg-check(8)?

It's been just habit and inertia, I have been using
ports-mgmt/bsdadminscripts for years and switched to
ports-mgmt/bsdadminscripts2 out of curiosity.

However, my initial post was a false alarm: I Ctrl-C-d pkg_libchk(1) as
it started to show 'ELF binary type "0" not known' messages. I now
played with pkg_libchk(1) more - it does show a lot of 'ELF binary type
"0" not known' messages, which it didn't do before, but it does finish
successfully.

Thank you for your replies.

-- 
Janos Dohanics