archlinux/gcc weirdness

[cryptix]

I'm pretty sure I was able to install this some weeks ago but now I get this:

higgsArchOne~/node-sodium(master|✔) % git rev-parse HEAD                                 
ef8000103d5e0645988ad52ac62e8f7373062602
higgsArchOne~/node-sodium(master|✔) % npm install                                        

> sodium@1.0.22 preinstall /home/cryptix/node-sodium
> make

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --force-missing
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /sbin/automake line 3936.
configure.ac:142: installing 'build-aux/compile'
configure.ac:10: installing 'build-aux/missing'
src/libsodium/Makefile.am: installing 'build-aux/depcomp'
autoreconf: Leaving directory `.'
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /sbin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... clang
checking whether the C compiler works... no
configure: error: in `/home/cryptix/node-sodium/deps/libsodium':
configure: error: C compiler cannot create executables
See `config.log' for more details
Makefile:8: recipe for target 'configure' failed
make: *** [configure] Error 77

npm ERR! Linux 4.2.5-1-ARCH
npm ERR! argv "/usr/bin/node" "/sbin/npm" "install"
npm ERR! node v5.0.0
npm ERR! npm  v3.4.0
npm ERR! code ELIFECYCLE
npm ERR! sodium@1.0.22 preinstall: `make`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the sodium@1.0.22 preinstall script 'make'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sodium package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     make
npm ERR! You can get their info via:
npm ERR!     npm owner ls sodium
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/cryptix/node-sodium/npm-debug.log

I'm not sure why configure selects clang (which isn't installed) and not gcc (which is installed, version 5.2.0). Here is the config.log file.

[paixaop]

This is an error from LibSodium. Can you check if you can compile the library by it self first?
You can go to the libsodium directory under deps/libsodium and try to run configure and make from there.

[cryptix]

This was a fault on my part from merging system configuration... Sorry.

edit: For people playing along, I had export CC=clang in my ~/.profile