Excerpts from rupert THURNER's message of Sun May 08 16:17:03 -0400 2011:
Hi Rupert,
> when upgrding lzlib the following error is thrown:
> if [ -f
> "/home/rupert/mgar/pkg/lzlib/trunk/work/solaris9-sparc/install-isa-sparcv8/opt/csw/lib/liblz.so.1"
> ] ; then \
> run_ldconfig=no ; rm -f
> "/home/rupert/mgar/pkg/lzlib/trunk/work/solaris9-sparc/install-isa-sparcv8/opt/csw/lib/liblz.so.1"
> ; \
> else run_ldconfig=yes ; \
> fi ; \
> cd
> "/home/rupert/mgar/pkg/lzlib/trunk/work/solaris9-sparc/install-isa-sparcv8/opt/csw/lib"
> && ln -s liblz.so.1.1 liblz.so.1 ; \
> if [ ${run_ldconfig} = yes ] ; then ldconfig
> "/home/rupert/mgar/pkg/lzlib/trunk/work/solaris9-sparc/install-isa-sparcv8/opt/csw/lib"
> ; fi ; \
> fi
> /bin/sh: ldconfig: not found
This looks to be a linuxism that has been coded into the build
process. I'd question it's correctness in the form above if run on a
linux box as that would manipulate /etc/ld.so.conf. This is a rough
equivalent of crle.
If you disable it via patching, what happens? Maybe just turn that
line into a no-op?
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.
