New answers tagged

0

Looks like homebrew installed svn in /usr/local/Cellar/subversion/1.9.4 So I added it in $PATH export PATH=$PATH:/usr/local/Cellar/subversion/1.9.4/bin/ Added it in ~/.bash_profile. Then execute - source ~/.bash_profile and all seems good again


0

Here are the SVN binary packages: https://subversion.apache.org/packages.html I had previously faced a similar issue and this solved the issue for me. Also, when I tried using brew I had an issue, so I used MacPorts.


0

I got it working by creating an empty tar file and linking to that. But I'm curious if there are better ways. $ tar cvf empty.tar --files-from /dev/null


0

I found the answer provided by user vitorgalvao on the project's Github page: https://github.com/caskroom/homebrew-cask/issues/22317 Spotlight doesn’t index /usr/local/, that why we started using /opt in the first place. Reinstall your apps with --force and they’ll be moved (our new behaviour). Spotlight will see them then.


1

The problem here is just simply that brew is detecting an old version of Xcode. If it was objecting to the version of the command line tools that you have installed you'd be getting a different error message. A newer Command Line Tools release is available. Update them from Software Update in the App Store. You can see the actual code here yourself. The ...


0

Try rebuilding the spotlight index on your mac: Choose Apple  menu > System Preferences, then click Spotlight. Click the Privacy tab. Drag the folder or disk that you want to index again to the list of locations that Spotlight is prevented from searching. Click OK to confirm. Select the folder or disk you just added, then click the Remove (–) button to ...


0

I'm not sure with it's like this, but if I compile with gcc-4.9 (as the gcc version I have instaled is version 4.9.2) instead of gcc it works as it should. So the compilation sentence that seems to work is gcc-4.9 -o exec_name program.c. If someone knows why it is like this I would be interested to know.


1

The command is supposed to move the tmux process from a newly created bootstrap context under the root, to the user's login bootstrap context. To explain that in slightly more common terms: macOS (formerly OS X) is built with a Mach-kernel at the lowest layer. Programs executing at this layer are called tasks. On top of the Mach-kernel is the BSD ...


0

FYI, if you previously had the old version installed and haven't run brew cleanup (which deletes old versions), you can switch with something like brew switch node 5.7.0 All installed versions of node can be listed by running brew info node or ls -l /usr/local/Cellar/node/ See the brew command cheat sheet: http://ricostacruz.com/cheatsheets/homebrew.html


0

For these types of warnings specifically, you could probably use a custom installation prefix. The homebrew installation instructions (2016 Apr 3 permalink) say you can do that, but warn against it. In practice I've heard that issues are quite rarely encountered.


4

Homebrew on its own acts like a command-line App Store. It's safe, if you know what you're downloading. If you are concerned about downloading hijacked binaries, verify the SHA/SHA1 sum of the binary you've downloaded against the SHA/SHA1 sum published by the developer, usually on their webpage. Personally, I've never had any bad experiences with Homebrew. ...


1

Update: Current stable version (.67) of putty can't be build with gtk+2 support on OS X using homebrew. This is a know issue #40951. It seems you can install from HEAD version (brew install --HEAD --with-gtk+3 putty) and for me that is also broken. brew install putty by default installs from a pre-built bottle. The pre-built bottle for putty doesn't include ...


1

You have to add /usr/local/sbin to your path. It was installed to /usr/local/sbin but that directory is not in your $PATH by default. Add a line like this to your ~/.bashrc or equivalent: export PATH=/usr/local/sbin:$PATH


1

You should have a look at brew bundle, which installs as a subcommand of brew. It can install and update packages, taps, and casks specified in a Brewfile. You can also dump your current Homebrew environment into a new Brewfile or uninstall everything not listed.



Top 50 recent answers are included