Clang Support on FreeBSD

[NuLL3rr0r]

Hello,
Unfortunately on FreeBSD systems whenever I do a npm install for most modules node-gyp assumes the compiler is g++. FreeBSD uses clang as it's default compiler and there is no g++.

This is an example issue that I had: kelektiv/node.bcrypt.js#270 (comment)

This solved the issue:
export CXX=clang++
npm install --clang=1

But on FreeBSD/Mac OS X systems it should switches to clang insted of gcc.

[saper]

Hi, I am using

env CC=clang CXX=clang++ LINKXX=clang++ LINK=clang ....

before using node-gyp or npm install

[AnthIste]

@saper thanks a lot, that worked for me when installing leveldown on FreeBSD 9.3

[Globik]

And for windows?

[saper]

@Globik Are you using clang on Windows?

[Globik]

@saper yes, for tests, at a very beginning right now.

[saper]

There is probably much more work to do for such a setup:

1. Check if gyp supports such a setup.
2. Unless clang uses Visual Studio v120 C++ ABI (which I doubt highly), you would need to build your own node with clang
3. One needs to convince a lot of code that win32 is not only Visual Studio. Some libraries in the non-node world support mingw32 for example.

This bug is about detecting and using clang in an environment where it is a known working compiler, in sod cases the only one installed.

[arrowd]

Building https://github.com/kelektiv/node.bcrypt.js with npm on FreeBSD works ATM. Either this is fixed or other reproducing testcase is needed.