Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Alexandre Oliva
On Apr 14, 2000, Kevin Atkinson <[EMAIL PROTECTED]> wrote: > I honestly don't see what the hell is wrong with using a shell script to > do this so a binary can be relocating. 1) You have to figure out whether to use LD_LIBRARY_PATH, SHLIB_PATH, LD32_LIBRARY_PATH, LD64_LIBRARY_PATH, etc. 2) You

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Alexandre Oliva
On Apr 14, 2000, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > Note that since free software is available with full source code, it > can be compiled to specifically match a particular system > configuration if an appropriate binary distribuition for that system > is not available. As long as the

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Kevin Atkinson
On Fri, 14 Apr 2000, Bob Friesenhahn wrote: > On Fri, 14 Apr 2000, Kevin Atkinson wrote: > > > On Fri, 14 Apr 2000, Bob Friesenhahn wrote: > > > > > Commercial programs typically include a shell script which sets > > > LD_LIBRARY_PATH (and other variables) in order to find the package > > > com

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Bob Friesenhahn
On Fri, 14 Apr 2000, Kevin Atkinson wrote: > On Fri, 14 Apr 2000, Bob Friesenhahn wrote: > > > Commercial programs typically include a shell script which sets > > LD_LIBRARY_PATH (and other variables) in order to find the package > > components. While this may be fine for commercial software, i

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Kevin Atkinson
On Fri, 14 Apr 2000, Bob Friesenhahn wrote: > Commercial programs typically include a shell script which sets > LD_LIBRARY_PATH (and other variables) in order to find the package > components. While this may be fine for commercial software, it is not > acceptable for free software since free sof

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Bob Friesenhahn
On Fri, 14 Apr 2000, Kevin Atkinson wrote: > > Try supporting this for 5000 users of your installed program across > > 5000 workstations/PCs. This approach fails miserably. Besides the > > effort to get your users to use the same LD_LIBRARY_PATH, there is the > > problem with conflicts between si

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Kevin Atkinson
On Fri, 14 Apr 2000, Bob Friesenhahn wrote: > On Fri, 14 Apr 2000, Kevin Atkinson wrote: > > Doesn't either setting LD_LIBRARY_PATH (or the equivalent variable for > > your particular system) or adding the weird location to /etc/ld.so.conf > > (or the equivalent file for your particular system)

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Bob Friesenhahn
On Fri, 14 Apr 2000, Kevin Atkinson wrote: > Doesn't either setting LD_LIBRARY_PATH (or the equivalent variable for > your particular system) or adding the weird location to /etc/ld.so.conf > (or the equivalent file for your particular system) generally solve the > problem? Try supporting this f

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Kevin Atkinson
On 14 Apr 2000, Alexandre Oliva wrote: > On Apr 14, 2000, Kevin Atkinson <[EMAIL PROTECTED]> wrote: > > > Doesn't either setting LD_LIBRARY_PATH (or the equivalent variable for > > your particular system) or adding the weird location to /etc/ld.so.conf > > (or the equivalent file for your partic

Re: Solution to Preload problem & Feature Request

2000-04-14 Thread Alexandre Oliva
On Apr 14, 2000, Kevin Atkinson <[EMAIL PROTECTED]> wrote: > Doesn't either setting LD_LIBRARY_PATH (or the equivalent variable for > your particular system) or adding the weird location to /etc/ld.so.conf > (or the equivalent file for your particular system) generally solve the > problem? It s