[csw-maintainers] Runtime linker pathes in GAR

rupert THURNER rupert at opencsw.org
Wed Apr 1 07:25:23 CEST 2009


currently i get:
~$ ssh rupert at login.opencsw.org
PTY allocation request failed on channel 0
Received disconnect from 213.178.77.178: 2: fork failed: Not enough space


On Tue, Mar 31, 2009 at 23:04, Dagobert Michelsen <dam at opencsw.org> wrote:
> Hi,
>
> James is currently in the tedious task of reviewing all
> runtime linker pathes from the packages. To make it
> easier for you as maintainer I have a summary here how
> this works in GAR and how to fix things.
>
> Runtime pathes can be checked with
>  /usr/ccs/bin/dump -Lv <binary> | <library>
>
> A correct setting with ISALIST should look like
> [7]     RUNPATH         /opt/csw/lib/$ISALIST:/opt/csw/lib
> [8]     RPATH           /opt/csw/lib/$ISALIST:/opt/csw/lib
>
> A correct setting without ISALIST should look like
> [7]     RUNPATH         /opt/csw/lib
> [8]     RPATH           /opt/csw/lib
>
> GAR adds a runtime path with $ISALIST by default. To skip this
> entirely in GAR you can use
>  NOISALIST = 1
> How much shell escaping is necessary depends on if the application
> uses autoconf and/or libtool. The quoting-level can be reduced with
>  RUNPATHQUOTE = 1
> (quote for one expansion, e. g. only configure) as opposed to the default
>  RUNPATHQUOTE = 2
> (quote for double expansion, configure and libtool).
>
>
> Best regards
>
>  -- Dago
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
>



More information about the maintainers mailing list