[M3devel] runpath/unshipped vs. shipped binaries

Mika Nystrom mika at async.caltech.edu
Mon Apr 6 17:32:56 CEST 2009


Would this mean that users of CM3 have to set LD_LIBRARY_PATH for
things they build themselves but don't ship?

I almost never ship binaries because I don't want user "mika" to
have write access to the place whither the Modula-3 compiler normally
ships.  But I use them... from cron and other places.  Other users
may use them too...

     Mika

Olaf Wagner writes:
>Quoting Jay <jay.krell at cornell.edu>:
>
>> Running uninstalled binaries shall require either LD_LIBRARY_PATH   
>> or build_standalone(). m3tests uses build_standalone. This is maybe   
>> why more stuff is build_standalone -- anything that runs uninstalled  
>>  when doing buildlobal, the various stub code generators.
>
>Please just use build_standalone for all binaries that are needed
>by the build system itself. That shouldn't be many.
>
>Otherwise, I think setting LD_LIBRARY_PATH is acceptable.
>
>Olaf
>-- 
>Olaf Wagner -- elego Software Solutions GmbH
>                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
>    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194



More information about the M3devel mailing list