Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Unable to run brew --config, doctor, audit. #10055

Closed
ghost opened this issue Feb 9, 2012 · 7 comments
Closed

Unable to run brew --config, doctor, audit. #10055

ghost opened this issue Feb 9, 2012 · 7 comments

Comments

@ghost
Copy link

ghost commented Feb 9, 2012

Hello,

Just got a weird problem regarding brew and some of it various options. These are brew --config, audit, doctor, etc.

The process just stalls, nothing happens, and the bash process just eats my CPU usage. And often locks my system down.

I would of course check my install via brew doctor, but since I can't run it. I'm out of luck :/

Any known instances of this before? Any help is really appreciated.

@ghost
Copy link
Author

ghost commented Feb 9, 2012

Even installing Mercurial isn't possible. Not sure how long a compile takes, but I left it be for around two/three hours, and still no completion.

@jacknagel
Copy link
Contributor

(Keep in mind that I'm shooting in the dark here) At what point do things hang? Before or after the output?

@ghost
Copy link
Author

ghost commented Feb 9, 2012

It hangs before. And almost no verbose output when starting a Mercurial compile.

https://gist.github.com/1777333
Been like this for twenty minutes. (Ed1t: 30min)

My env: https://gist.github.com/1777392

@jacknagel
Copy link
Contributor

Does it happen using Terminal.app as well?

@ghost
Copy link
Author

ghost commented Feb 9, 2012

Does indeed I'm sorry :/ I have no real clue what can cause this. Like there is something just hanging. Or don't get past a step or something.

Been like this for a few days. Not noticed it before now really, when brew doctor wouldn't work.

@ghost
Copy link
Author

ghost commented Feb 9, 2012

Fixed this by reinstalling Xcode. This time the original sample, not the gcc-without-xcode.

I suspect this were caused by the 10.7.3 update.

Thanks for taking the time though :)

@ghost ghost closed this as completed Feb 9, 2012
@gpaul
Copy link

gpaul commented May 24, 2013

macos.rb: runs /usr/bin/mdfind
with a properly configured system it gets the first results really quickly but then proceeds to search the rest of the filesystem.
I've patched mine to do mdfind -onlyin /Applications and now it runs properly.
An alternative fix might be to read the output of the mdfind process until you've got your first result, then kill it and continue.

@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants