Hi, > 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?
No, its not an Apple bug. Something in your dot files is setting it. What does > grep LD_LIBRARY_PATH ~/.* > grep DYLD_LIBRARY ~/.* Give ? > But why then is the second admin account impervious to it? Because it doesn't have the settings in one of the ~/.* files that the other one does, I would guess. Chris > > 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 > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-users > > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
