summaryrefslogtreecommitdiff
path: root/configure
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/v0.8'Ben Noordhuis2012-08-171-1/+6
|\ | | | | | | | | | | | | | | Conflicts: ChangeLog src/node_version.h test/message/stdin_messages.out tools/install.py
| * build: Don't set gcc_version for Windowsisaacs2012-08-151-1/+1
| |
| * build: compile with -fno-tree-vrp when gcc >= 4.0Ben Noordhuis2012-08-131-1/+6
| |
* | addon: remove node-waf, superseded by node-gypBen Noordhuis2012-08-141-6/+0
|/
* build: improve armv7 / hard-float detectionAdam Malcontenti-Wilson2012-07-261-6/+62
|
* build: fix mksnapshot crash on sunosBen Noordhuis2012-07-181-0/+2
| | | | | | | | | | | | Unconditionally compile V8 with -fno-strict-aliasing on all platforms. gcc 4.5.2 on sunos generates bad code when -fstrict-aliasing is enabled, which undoubtedly means that there are more buggy versions of gcc out there. -fstrict-aliasing does not give a significant performance boost so let's just disable it. Fixes #3736.
* build: partially fix configure on ARMBen Noordhuis2012-07-121-17/+11
| | | | | | | | | | | V8 on ARM requires that armv7 is set. We don't have a good way to detect the CPU model right now so we pick a default and hope that it works okay for the majority of people. Non-scientific sampling - the ARM hardware I have lying around the house - suggests that ARMv5 and ARMv6 are still most common so armv7=0 it is. This obviously needs to be revisited sometime in the future.
* build: disable unsafe optimizationsBen Noordhuis2012-07-121-1/+0
| | | | | | | | | | | | | | | | Compile at -O2 and disable optimizations that trigger gcc bugs. Some people still reported mksnapshot crashes after commit b40f813 ("build: fix spurious mksnapshot crashes for good" - so much for that). Average performance of the -O2 binary is on par with the -O3 binary. Variance on the http_simple bytes/8 benchmark appears to be slightly greater but small enough that the possibly of it being noise cannot be excluded. The new binary very slightly but consistently outperforms the -O3 binary (by about 0.5%) on the mostly CPU-bound bytes/102400 benchmark. That could be an artifact of the system I benchmarked it on, a Core 2 Duo with a puny 32 kB of L1 instruction cache. The smaller binary seems to play nicer with the cache.
* build: fix spurious mksnapshot crashes for goodBen Noordhuis2012-07-111-10/+2
| | | | | | | | | | | | | | | | | | | | A variety of gcc bugs made mksnapshot crash with either a segmentation fault or a 'pure virtual method callled' run-time error. After much wailing and gnashing of teeth I managed to deduce that the bugs show up when: 1. gcc 4.5.2 for i386-pc-solaris2.11 is used and -fstrict-aliasing is enabled, or 2. gcc version 4.4.6 for x86_64-redhat-linux is used and -ffunction-sections -finline-functions at -O2 or higher is enabled Therefore, disable -ffunction-sections and -fdata-sections unconditionally and disable -fstrict-aliasing only on Solaris. The -ffunction-sections and -fdata-sections switches were nonsense anyway because we don't link with -Wl,--gc-sections.
* Fix the Windows buildBert Belder2012-07-071-1/+5
|
* build: rename strict_aliasing to node_no_strict_aliasingBen Noordhuis2012-07-031-3/+3
| | | | | Make the variable naming consistent with the other strict aliasing var, v8_no_strict_aliasing.
* build: disable -fstrict-aliasing for any gcc < 4.6.0Ben Noordhuis2012-07-031-6/+3
| | | | | | | It has been conclusively demonstrated that the -fstrict-aliasing bugs in gcc's optimizer are not limited to the 4.5.x releases only. Fixes #3601 among others.
* build: detect cc version with -dumpversionBen Noordhuis2012-07-031-11/+3
| | | | | | | | The heuristic introduced in f78ce08 ("build: handle output of localized gcc or clang") does not handle "branded" versions of gcc, i.e. a gcc whose output has been customized by the distro vendor. Fixes #3601.
* build: handle output of localized gcc or clangBen Noordhuis2012-06-301-16/+18
| | | | | | | | | | Before this commit, we used to scan the output of `$CC -v` for strings like "gcc version x.y.z". It was pointed out that this approach fails with localized versions of gcc because those print (for example) "gcc versión x.y.z". Use the output of `$CC --version` instead and only look at the first line.
* build: rename openssl configure switchesBen Noordhuis2012-06-301-21/+42
| | | | | | | | | | | | | | | | | | | | For consistency's sake, rename: --openssl-use-sys --openssl-includes --openssl-libpath To: --shared-openssl --shared-openssl-includes --shared-openssl-libpath And add --shared-openssl-libname while we're at it. The old switches still work but `./configure --help` won't print them. Fixes #3591.
* build: use proper python interpreterBen Noordhuis2012-06-281-3/+4
| | | | | | | | Make configure start gyp with the same python interpreter that is used to run configure itself. Fixes an issue where configure fails with a SyntaxError because the user has multiple python binaries on his $PATH and the default one is too old.
* build: handle CC env var with spacesGabriel2012-06-271-1/+1
| | | | | | For example: CC='ccache gcc' ./configure
* build: fix --shared-v8 optionBen Noordhuis2012-06-271-1/+0
|
* configure: don't fail if compiler_version() doesn't workBert Belder2012-06-261-3/+3
| | | | This fixes the Windows build.
* build: expand ~ in `./configure --prefix=~/a/b/c`Ben Noordhuis2012-06-261-1/+1
|
* build: disable strict aliasing in v8 with gcc 4.5.xBen Noordhuis2012-06-261-5/+11
| | | | | The gcc 4.5.x have various bugs that make V8 crash in various and interesting ways when -fstrict-aliasing is in effect.
* Rename GYP variable node_use_system_openssl to be consistentRyan Dahl2012-06-201-2/+2
|
* Fix #3465 Add ./configure --no-ifaddrs flagisaacs2012-06-181-0/+8
| | | | For Old Solaris.
* Windows: Enable ETW events.Igor Zinkovsky2012-06-131-0/+19
| | | | | | | This commit enables ETW events to be fired on Windows for existing DTrace probes. ETW instrumentation is enabled by default. It is possible to build node.exe without ETW instrumentation by using --without-etw option with configure script.
* build: Set strict_aliasing on SunOS alwaysisaacs2012-05-161-0/+2
| | | | | A build failure was introduced on c9676c9147e088171e60b1977ac239ded4f327df in SmartOS systems. This makes it build properly.
* build: improve c compiler detectionSadique Ali2012-05-151-10/+14
|
* build: print error message if no compiler foundJavier Hernández2012-05-051-4/+14
| | | | | Make the configure script warn the user about the lack of an acceptable C compiler on the system.
* configure: output a newline at the end of config.gypiNathan Rajlich2012-04-111-1/+1
|
* configure: don't use "with" for Python 2.5 and olderNathan Rajlich2012-04-111-2/+2
|
* build: add support for DTrace and postmortemDave Pacheco2012-04-011-2/+16
| | | | | | | | * fixes #2110 * includes V8 postmortem metadata in Solaris builds * adds GYP support for DTrace probes and ustack helper * ustack helper derives constants dynamically from libv8_base.a * build with DTrace support by default on SunOS
* build: make --openssl-use-sys a boolean optionNathan Rajlich2012-03-171-1/+1
| | | | Before you had to enter a truthy value like: --openssl-use-sys=1
* build: fix configure with spaces in CCAlex Xu2012-03-161-1/+1
|
* vcbuild: run the 'configure' script in vcbuild.batNathan Rajlich2012-03-151-3/+30
| | | | | So that a 'config.gypi' file gets generated, which is required for the `process.config` object (see #2928).
* build: disable -fvisibility=hidden if gcc < 4.0.0Ben Noordhuis2012-03-051-3/+3
|
* build: make CC command in -fstrict-aliasing check configurableBen Noordhuis2012-03-051-8/+11
|
* build: make CC command in host check configurableSadique Ali2012-03-051-2/+1
|
* build: fix gcc version checkShigeki Ohtsu2012-03-031-1/+1
|
* build: remove unused import from configure scriptShigeki Ohtsu2012-03-031-1/+0
|
* build: disable -fstrict-aliasing if gcc < 4.6.0Ben Noordhuis2012-03-021-12/+19
| | | | | | | | A compiler bug in older versions of gcc makes it do unsafe optimizations at -O1 and higher. This manifested itself with (at least) gcc 4.5.2 on SmartOS because it made V8 hang in a busy loop. See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45883
* build: remove --shared-cares configure switchBen Noordhuis2012-03-021-26/+0
| | | | | | | c-ares is a) bundled with libuv now, and b) contains out-of-tree patches. It no longer makes sense to link against a shared library. Fixes #2117.
* Fix #2830 for the old gcc bug on SmartOSShigeki Ohtsu2012-02-271-2/+13
|
* build: support shared zlibT.C. Hollingsworth2012-02-271-1/+31
|
* Revert "Revert "build: support shared V8 properly""isaacs2012-02-231-0/+3
| | | | This reverts commit a9130222bd36ac2c5dd7ae560f02bb99569749a7.
* Merge branch 'v0.7.5-release'isaacs2012-02-231-3/+0
|\
| * Revert "build: support shared V8 properly"isaacs2012-02-231-3/+0
| | | | | | | | | | | | | | This reverts commit 3d1b67064085ef486a69c2fc69d195dc35f4f50c. Breaks build on windows. https://gist.github.com/1895279
* | build: make default_configuration consistent with BUILDTYPEShigeki Ohtsu2012-02-231-0/+1
|/
* build: support shared V8 properlyT.C. Hollingsworth2012-02-221-0/+3
| | | | | -don't pull in bundled v8 as a dependency when node_shared_v8==true -use node_shared_v8_includes for v8.h and v8-debug.h
* build: better host_arch() definition in configureNathan Rajlich2012-02-201-17/+31
| | | | | | On one of my OS X Lion machines, it always reports i386, even though 64-bit is supported. This lookup better matches how WAF determines the host arch, which was correctly getting 64-bit even on this screwy machine.
* build: map i686 to ia32Nathan Rajlich2012-02-201-0/+1
|
* build: test `uname -m` first, then `uname -p`Nathan Rajlich2012-02-201-2/+2
| | | | Prevent false i386 on 64-bit OS X.
View Lorry Controller Status