Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build error in both 4.2.2 and 5.1.0 #4088

Closed
ghost opened this issue Dec 1, 2015 · 9 comments
Closed

build error in both 4.2.2 and 5.1.0 #4088

ghost opened this issue Dec 1, 2015 · 9 comments
Labels
build Issues and PRs related to build files or the CI. question Issues that look for answers.

Comments

@ghost
Copy link

ghost commented Dec 1, 2015

image
I download the source code from official website and want to install it manually onto Debian.
But when I execute 'make' command, there is always error message like the picture above.

@MylesBorins
Copy link
Contributor

have you run ./configure first?

@Martii
Copy link

Martii commented Dec 1, 2015

What is your $ ./configure parameters?

Have you ensured Debian is up to date with:

  • $ sudo apt-get update and
  • $ sudo apt-get dist-upgrade

Do you have all the necessary prerequisites mentioned here? (clang and clang++ is related to Mac usually)

Have you tried a $ git clone https://github.com/nodejs/node.git from GitHub (GH)? ... if so did you $ git checkout tags/v4.2.2 and such... I'm in process of reworking my local copy for replication and I can see if this is doing it in general for other distro's... but from GH.

Hope some of this might help. :)

@ghost
Copy link
Author

ghost commented Dec 1, 2015

I see the problem is: C++ compiler too old, need g++ 4.8 or clang++ 3.4 (CXX=g++)
But how can I install g++ 4.8 on Debian Wheezy? It's g++ 4.7.2 now and already the latest package: https://packages.debian.org/wheezy/g++

@bnoordhuis
Copy link
Member

You can install it from jessie (see this SO answer) but I'd just download and install the binary from nodejs.org if I were you.

/cc @misterdjules - this is one of the 4.7 parser issues we've talked about.

@Martii
Copy link

Martii commented Dec 1, 2015

@dimply
Our VPS is pre-configured with jessie and appears to be doing well directly with that... thousands, if not more, of users can't be wrong. ;) :)

There aren't any pitfalls to adding an extra packaging repo and major benefits to having access to other packages that are not limited by a specific binary from a specific node based project. The choice is up to you.

Additional ref:

@ghost
Copy link
Author

ghost commented Dec 1, 2015

@bnoordhuis I just don't know how to treat with the downloaded binary files. 😹 .
If I execute "make" and "make install", it seems that linux will automatically do the configures for me.

@ChALkeR ChALkeR added build Issues and PRs related to build files or the CI. question Issues that look for answers. labels Dec 1, 2015
@ghost
Copy link
Author

ghost commented Dec 1, 2015

I successfully installed g++ 4.8 on Debian Wheezy using the Jessie package. Then I execute make, but an error shows cc: Command nod found.
I found a solution with executing export CC=gcc && make and this time I succeed.
But when I go on to sudo make install, the error comes out again with the same information cc: Command nod found. Neither export CC=gcc && sudo make install nor cd /usr/bin && sudo ln -s gcc CC will work. How can I solute this?

@bnoordhuis
Copy link
Member

@dimply Try sudo make install CC=gcc. gcc needs to be on root's PATH, of course.

@jasnell
Copy link
Member

jasnell commented Mar 22, 2016

Assuming it's safe to close this one now.

@jasnell jasnell closed this as completed Mar 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. question Issues that look for answers.
Projects
None yet
Development

No branches or pull requests

5 participants