An excerpt from the inconv docs:
After installing GNU libiconv for the first time, it is recommended to
recompile and reinstall GNU gettext, so that it can take advantage of
libiconv.
On systems other than GNU/Linux, the iconv program will be
internationalized only if GNU gettext has been built and installed
before GNU libiconv. This means that the first time GNU libiconv is
installed, we have a circular dependency between the GNU libiconv and
GNU gettext packages, which can be resolved by building and installing
either
* first libiconv, then gettext, then libiconv again,
or (on systems supporting shared libraries, excluding AIX)
* first gettext, then libiconv, then gettext again.
What a mess, so it seems it's intended and we have to live with it. Can
the install utils support co-dependent packages and James suggested?
James Lee wrote:
On 01/04/09, 14:18:35, Dagobert Michelsen <[email protected]> wrote regarding
[csw-maintainers] Another cyclic dependency:
From CSWggettextrt, needs libiconv which is in CSWiconv:
$ ldd /opt/csw/bin/ggettext
libintl.so.8 => /opt/csw/lib/libintl.so.8
libsec.so.1 => /lib/libsec.so.1
libc.so.1 => /lib/libc.so.1
libiconv.so.2 => /opt/csw/lib/libiconv.so.2
libavl.so.1 => /lib/libavl.so.1
libm.so.2 => /lib/libm.so.2
From CSWiconv, needs libintl which is in CSWggettextrt:
$ ldd /opt/csw/bin/iconv
libiconv.so.2 => /opt/csw/lib/i386/libiconv.so.2
libintl.so.3 => /opt/csw/lib/i386/libintl.so.3
libc.so.1 => /lib/libc.so.1
libm.so.2 => /lib/libm.so.2
Shouldn't the installer be tolerant of dependancy loops and just
install both when either is requested?
James.
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
