Databases
StackOverflow2013
Postsdbo
POError: The 'brew link' step did not complete successfully
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError: The 'brew link' step did not complete successfully
    primarykey
    data
    text
    <p>I'm trying to install node.js via Homebrew. Unfortunately, I get this error:</p> <pre><code>➜ ~ brew install node ==&gt; Downloading http://nodejs.org/dist/v0.8.10/node-v0.8.10.tar.gz ######################################################################## 100.0% ==&gt; ./configure --prefix=/usr/local/Cellar/node/0.8.10 ==&gt; make install ==&gt; Caveats Homebrew installed npm. We recommend prepending the following path to your PATH environment variable to have npm-installed binaries picked up: /usr/local/share/npm/bin Warning: Could not link node. Unlinking... Error: The `brew link` step did not complete successfully The formula built, but is not symlinked into /usr/local You can try again using `brew link node' ==&gt; Summary /usr/local/Cellar/node/0.8.10: 856 files, 13M, built in 103 seconds </code></pre> <p>So then I try to link node manually...</p> <pre><code>➜ ~ brew link node Linking /usr/local/Cellar/node/0.8.10... Warning: Could not link node. Unlinking... Error: Could not symlink file: /usr/local/Cellar/node/0.8.10/lib/node_modules/npm/scripts/relocate.sh Target /usr/local/lib/node_modules/npm/scripts/relocate.sh already exists. You may need to delete it. To force the link and delete this file, do: brew link -f formula_name To list all files that would be deleted: brew link -n formula_name </code></pre> <p>No luck, so I try forcefully linking node...</p> <pre><code>➜ ~ brew link -f node Linking /usr/local/Cellar/node/0.8.10... Warning: Could not link node. Unlinking... Error: Permission denied - /usr/local/lib/dtrace/node.d </code></pre> <p>I'm not familiar with dtrace in any regard and I'm afraid to mess with permissions, so I tried to sudo..</p> <pre><code>➜ ~ git:(master) sudo brew link -f node Password: Error: Cowardly refusing to `sudo brew link' You can use brew with sudo, but only if the brew executable is owned by root. However, this is both not recommended and completely unsupported so do so at your own risk. </code></pre> <p>I've tried uninstalling node via <code>brew uninstall node</code> and retrying the install with no luck.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USchandlervdw
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POError: The 'brew link' step did not complete successfully
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POError: The 'brew link' step did not complete successfully
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POError: The 'brew link' step did not complete successfully
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI can't get automake. mongodb and node to link with homebrew
      singulars
      1. POError: The 'brew link' step did not complete successfully
      1. USpixel 67
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload