'brew doctor' failed to run on 10.8.2 | broken symlinks #18257

vaLinBSD opened this Issue Mar 5, 2013 · 4 comments

3 participants


This happens frequently when I run 'brew upgrade' mostly on libraries-related formulas, such as libogg, libsigc++, freetype, glib etc. In /usr/local/include or /usr/local/lib then occurs broken symlinks.



This looks like a problem with your computer. (Notice how libpng's link contains data from a Garage Band plist.) Check to make sure you don't have a hardware problem such as dying RAM or hard drive.


I'm aware of that, I've done these tests before the post and all passed without errors. The problems are only related to the brew created symlinks (no other symlinks are affected in the system, or other storage problems appears) after doing 'upgrade' ...weird. I've tried couple of times uninstalling the whole brew and then install it again. It all goes thru without any problems until some of the installed formulas get new version and I do the mentioned 'upgrade'.

Any other advise would be appreciated, thanks.


I really can't think of anything to suggest here beyond bad hardware. Have you run a hard drive scan with Disk Utility? Also try running memtest86 if you haven't already.


I've done some more investigation and it starts looking as not homebrew-related problem, so I must apologize. All these tests (diskutil, memtest86, etc.) past without errors as I mentioned in previous post. It looks like I have the same issues as others in this apple discussions: https://discussions.apple.com/thread/3891215?start=0&tstart=0

@dougluce dougluce added a commit to dougluce/homebrew that referenced this issue Apr 27, 2013
@dougluce dougluce Robust in the face of really bad symlinks.
`ArgumentError` is thrown when Ruby's pathname lib hits a symlink with
binary zeros in it ('\0').  These links have shown up in
/usr/local/bin for a couple users (#18257,
https://gist.github.com/barttenbrinke/2948629 and others).  As a
result, caused `brew doctor`/`brew prune` to fail and exit mid-run.

`brew doctor` will now report those links as bad, and `brew prune`
will remove them.
@adamv adamv closed this Apr 30, 2013
@xu-cheng xu-cheng locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.