Change:
I have a fresh installation of Ubuntu 14.04 and installed compiled version of 10.38. failed on step with error 'make: g++: Command not found'. solves the problem. It make sense put g++ dependency into Prerequisites section.
That's kind of annoying but yea, we might need to do something like that. Compilers are a dependency for any binary npm module (which one of our dependencies depends on). Even contextify itself doesn't call out the need for g**. When you install node / npm via does it not install as well? It seems like it should since that's a requirement for many modules.
I used the recommended approach for . is not a part of installation. But I see your point, contextify setup on Windows even more .
The installation of build-essential is not 'optional'. It is a prerequisite for otherwise node-gyp will fail. The instructions for the Debian-based installation should reflect that build-essential is a prerequisite.
for installing g++ in fedora and other linux os use sudo yum install /usr/bin/g++ or sudo dnf install gcc-c++
fixed it for me (Ubuntu)
works for CentOS7, too. :)
What about Mac?

Discussion:
`React` is the entry point to the React framework. If you're using one of the prebuilt packages it's available as a global; if you're using CommonJS modules you can `require()` it. <del> ### DOM </del> <ins> #### React.DOM </ins> `React.DOM` provides all of the standard HTML tags needed to build a React app. You generally don't use it directly; instead, just include it as part of the `/** @jsx React.DOM */` docblock. <del> ### initializeTouchEvents(boolean shouldUseTouch) </del> <ins> #### React.initializeTouchEvents ```javascript initializeTouchEvents(boolean shouldUseTouch) ``` </ins> Configure React's event system to handle touch events on mobile devices. <del> ### function autoBind(function method) </del> <ins> #### React.autoBind ```javascript function autoBind(function method) ``` </ins> Marks the provided function to be automatically bound to each React component instance created. This allows React components to define automatically bound methods and ensure that when called they will always reference their current instance.

}); ``` <del> ### function createClass(object specification) </del> <ins> #### React.createClass ```javascript function createClass(object specification) ``` </ins> Creates a component given a specification. A component implements a `render` method which returns a single child. That child may have an arbitrarily deep child structure. One thing that makes components different than a standard prototypal classes is that you don't need to call new on them. They are convenience wrappers that construct backing instances (via new) for you. <del> ### ReactComponent renderComponent(ReactComponent container, DOMElement mountPoint) </del> <ins> #### React.renderComponent ```javascript ReactComponent renderComponent(ReactComponent container, DOMElement mountPoint) ``` </ins> Renders a React component into the DOM in the supplied `container`.

Component classses created by `createClass()` return instances of `ReactComponent` when called. Most of the time when you're using React you're either creating or consuming `ReactComponent`s. <del> ### DOMElement getDOMNode() </del> <ins> #### getDOMNode ```javascript DOMElement getDOMNode() ``` </ins> If this component has been mounted into the DOM, this returns the corresponding native browser DOM element. This method is useful for reading values out of the DOM, such as form field values and performing DOM measurements. <del> ### setProps(object nextProps) </del> <ins> #### setProps ```javascript setProps(object nextProps) ``` </ins> When you're integrating with an external JavaScript application you may want to signal a change to a React component rendered with `renderComponent()`. Simply call `setProps()` to change its properties and trigger a re-render. **Note:** This method can only be called on a root-level component. That is, it's only available on the component passed directly to `renderComponent()` and none of its children. If you're inclined to use `setProps()` on a child component, instead take advantage of reactive updates and pass the new prop to the child component when it's created in `render()`. <del> ### replaceProps(object nextProps) </del> <ins> #### replaceProps ```javascript replaceProps(object nextProps) ``` </ins> Like `setProps()` but deletes any pre-existing props that are not in nextProps. <del> ### ReactComponent transferPropsTo(ReactComponent targetComponent) </del> <ins> #### transferPropsTo ```javascript ReactComponent transferPropsTo(ReactComponent targetComponent) ``` </ins> Transfer properties from this component to a target component that have not already been set on the target component. This is usually used to pass down properties to the returned root component. `targetComponent`, now updated with some new props is returned as a convenience. <del> ### setState(object nextState) </del> <ins> #### setState ```javascript setState(object nextState) ``` </ins> Merges nextState with the current state. This is the primary method you use to trigger UI updates from event handlers and server request callbacks.

**Note:** `setState()` does not immediately mutate `this.state` but creates a pending state transition. Accessing `this.state` after calling this method can potentially return the existing value. <del> ### replaceState(object nextState) </del> <ins> #### replaceState ```javascript replaceState(object nextState) ``` </ins> Like `setState()` but deletes any pre-existing state keys that are not in nextState. <del> ### forceUpdate() </del> <ins> #### forceUpdate() ```javascript forceUpdate() ``` </ins> If your `render()` method reads from something other than `this.props` or `this.state` you'll need to tell React when it needs to re-run `render()`. Use `forceUpdate()` to cause React to automatically re-render. This will cause `render()` to be called on the component and all of its children but React will only update the DOM if the markup changes. Normally you should try to avoid all uses of `forceUpdate()` and only read from `this.props` and `this.state` in `render()`. This makes your application much simpler and more efficient. <del> ### object getInitialState() ### componentWillMount() ### componentDidMount(DOMElement domNode) ### componentWillReceiveProps(object nextProps) ### boolean shouldComponentUpdate(object nextProps, object nextState) ### componentWillUpdate(object nextProps, object nextState) ### ReactComponent render() ### componentDidUpdate(object prevProps, object prevState, DOMElement domNode) ### componentWillUnmount() These are overridable lifecycle methods; see the [lifecycle methods](lifecycle.html) documentation for more information. </del> <ins> ```javascript object getInitialState() componentWillMount() componentDidMount(DOMElement domNode) componentWillReceiveProps(object nextProps) boolean shouldComponentUpdate(object nextProps, object nextState) componentWillUpdate(object nextProps, object nextState) ReactComponent render() componentDidUpdate(object prevProps, object prevState, DOMElement domNode) componentWillUnmount() ``` See the [advanced components](advanced-components.html) documentation for more details on these lifecycle methods. </ins>