On Fri, May 17, 2013 at 4:25 AM, Chris Jones <[email protected]>wrote:
> Hi, > > The warning means you either have the environment variable > > DYLD_LIBRARY_PATH > > *or* > > LD_LIBRARY_PATH > > set to some value ? Generally this is not a good idea, so try removing > these settings. If you do need them, you have to just put up with the > warning. > > I agree The problem is I cannot find anywhere where that variable has been defined and it is certainly not present in my '.bashrc' or related files Some people think this is an Apple bug? But why then is the second admin account impervious to it? Thanks Chris > > > On 17/05/13 07:41, Rodolfo Aramayo wrote: > >> People, >> >> This is NOT a MacPorts issue, but since I started using MacOS X 10.8.3 >> (from 10.6.8--so I am shy...what do you know), I am getting this >> annoying message every time I try to sudo >> >> >sudo -i >> dyld: DYLD_ environment variables being ignored because main executable >> (/usr/bin/sudo) is setuid or setgid >> >> The thing is that if I generate a second admin account, that account >> does behave as expected (i.e., no message is reported) >> This seems to be an innocuous message, that can be ignored...? but I am >> wondering if any of you encountered it and if you did what did you do to >> correct it? >> Nothing I found on the internet seems to be a reasonable risk-free >> approach... >> >> Thanks >> >> --R >> >> >> ______________________________**_________________ >> macports-users mailing list >> macports-users@lists.**macosforge.org<[email protected]> >> https://lists.macosforge.org/**mailman/listinfo/macports-**users<https://lists.macosforge.org/mailman/listinfo/macports-users> >> >> >
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
