dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid

Why would that make any difference?

If that doesn't help, add the following to two lines to .bash_profile:

unset LD_LIBRARY_PATH

unset DYLD_LIBRARY_PATH

This is not a sulution. If these variables are set it is for a reason. Unsetting them might make something else stop working (e.g., MacPorts, ...).

Even shutting down the computer will make the messages disappear but this is clearly not a solution.

Contrary to other reports, installing the 10.8.1 update did NOT resolve this issue for me.

It's also an issue with /bin/ps. Now some of my logs look like this:

I hope Apple will address this soon. It's a good error, because it tells me when these environment variables are being ignored (which is important). I don't think that removing the error would be a solution either.. How can this be resolved?

Just to let it known that the problem stays there even after upgrading to OS 10.8.2, and upgrading the XCode, including the Command Tools.

Not a big issue for me at the moment ... but I'm wondering if it signals something weird.

Check your /etc/profile file.

I had some cruft from on old belkin UPS upspilot installer. It was setting the DYLD_LIBRARY_PATH here. Once I deleted those lines the error is gone.

There is a good reason for people to set DYLD_LIBRARY_PATH. Telling them not to set it is not the right answer and can cause software to stop working if you don't know what you're doing. The right thing is for Apple to fix this ******** behavior. They are too busy working on phones to do so.

Right. After paying more attention to the error, I'm thinking the only thing that is wrong is that some core system binaries were compiled with a debug flag turned on that shouldn't be.

The error can be safely ignored.

However, a system that puts out warning messages like this when nothing is wrong isn't maintainable, so it is a bug. I've noticed Mac OS has been getting better about this, on and off. Seems to take 'em a while, but spurious warnings and errors on a completely fresh, stock OS install do seem to get addressed, thankfully.

Wow, I don't know how this many people have been misleading the issue. I'm very disappointed this thread even comes up so highly in search results on the internet.

Let's look carefully at the error again:

dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid

This particular executable (sudo in this case) has the "sticky bit" set on its file permissions (see http://en.wikipedia.org/wiki/Sticky_bit). For some reason this new Mac OS has set certain executables to with these file permissions and is throwing these warnings.

You can `chmod` these executables if you reall like and the warning will go away. Look at the executable using `ls -l` and you'll see the "s" is set there. Most other executables are set to standard 0755.

Hope that helps and this should be instructive to any of us developers to better grasp Unix fundamentals that have not changed much and are the foundation upon which most of us develop software today.

Well people, don't do what Dylan says! You'll regret it. After doing what he recommends you can't use the sudo command anymore, and you can't get it back to the sticky bit (because you need sudo rights for that). You'll get the message: sudo: must be setuid root. If you choose to go ahead anyways, you can get the correct permissions back by going to Utilities > Disk Utility and choose "Repair Disk Permissions".

Use disk utility to revert, hope it helps

Yes, SOME OF US need to better grasp our Unix fundamentals, like maybe YOU. Yes, let's "look very carefully" at why "for some reason sudo has its sticky bit set." Now why would a program that elevates a user to root privileges need its sticky bit set? Gee, I don't know, 5 minutes of Googling makes me a genius. Ah, ****, let's just go ahead and tell everyone to unset it and see how it goes, at the same time complaining about the ignorance of others.

This is again a wrong solution. Sudo always had the sticky bit on Mac OS X and other systems. It would not work without it. You should read the article you are linking.