[bug-notifications] [libgamin_dev 0005085]: libgamin_dev creates broken symlink for libfam.so

Mantis Bug Tracker noreply at opencsw.org
Tue Jul 9 18:24:47 CEST 2013

A NOTE has been added to this issue. 
Reported By:                mi
Assigned To:                raos
Project:                    libgamin_dev
Issue ID:                   5085
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Date Submitted:             2013-07-01 20:23 CEST
Last Modified:              2013-07-09 18:24 CEST
Summary:                    libgamin_dev creates broken symlink for libfam.so
After installing libgamin_dev I got the following files:

% grep libfam /var/sadm/install/contents
/opt/csw/lib/libfam.so=libfam.so.0.0.0 s none CSWlibgamin-dev
/opt/csw/lib/sparcv9/libfam.so=libfam.so.0.0.0 s none CSWlibgamin-dev

Note, that there are two symlinks -- but not the files they are pointing
at. The libfam.so.0.0.0 does not exist neither in /opt/csw/lib nor in

Perhaps, the symlink should point at libgamin.so?

 (0010487) mi (reporter) - 2013-07-09 18:24
You are right, that FreeBSD does not create libgamin.so. The gamin package
(we don't split things into foo and foo_dev -- that seems like a Linux
thing) installs simply libfam.so, which is a symlink to libfam.so.0. The
CSW package does install the same library as libgamin-1.so.*, which is
fine. All that's needed is for the libfam.so to exist and point to a valid,
Gamin-provided library.

When I reported the broken symlink, I expected the symlink to be fixed to
point to libgamin.so. Dragging in the actual FAM in order to install Gamin
(or Gamin_dev) is crazy -- Gamin is a replacement for FAM, it can not
require FAM to function.

If CSWlibfam0's libfam.so.0.0.0 and CSWgamin's libgamin-1.so.0.1.10 are not
identical, then either CSWlibfam0 is installing an older version of Gamin
implementation or it is simply the FAM implementation. Neither choice is a
good one.

Pointing libfam.so to libgamin-1.so.0.1.0 seems like the best solution at
this time -- it is what I did by hand here and my application is working...

More information about the bug-notifications mailing list