[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [E-devel] export of LD_LIBRARY_PATH in e_start_main.c
On Fri, 29 Dec 2006 04:03:26 -0500 Mike Frysinger <firstname.lastname@example.org> babbled:
> On Thursday 28 December 2006 21:40, Carsten Haitzler wrote:
> > hmm - actually this will work - often, but not all the time. if prefix/bin
> > is a symlink to for example prefix/.exec/i386/ (which i actually have seen
> > for multi-arch shared nfs filesystems) this breaks down
> ok, but the way it's done now wont work either, so i dont see what you're
> getting at here
yes it will - it handles this too. check the code. :) or it at least tries.
> > also is this ldso
> > feature something that exists outside of linux's ldso? as it's not
> > documented...
> it is documented ... it isnt glibc-specific or linux-specific at all ...
> sun's ldso supports it as well since it's part of the elf library searching
> > i think a more portable solution might be for e to "revert" its ld_lib_path
> > changes e_start did (as its only really needed on app runtime link) or to
> > remove it on exec of anything.
> they're equally portable but if you're going to pollute the env, then yes you
> should make sure the crap is cleansed before spawning sub processes ... of
> course, this wont help any modules that other people write and do exec's
sure - though there are exec wrappers in e's code that modules should use :)
> at the very least, there should be an option for people to remove the option
> for package maintainers to use since the target audience here is simply
i can see an option for package maintainers to build with when they know the
package will never move anywhere.
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) email@example.com
Tokyo, Japan (東京 日本)