[Converge] Build related commits

[jasnell]

There are a number of build related commits that need to reconciled. /cc @nodejs/build @misterdjules

• 59265264d56cfb7ced87f9b3666ec570152c5f47 src: make build pass with GCC < 4.5 - nodejs/node-v0.x-archive@5926526
• 6168fe6720650052728f3e78a495b723f0b41ce3 build: add win32 convenience build rule - nodejs/node-v0.x-archive@6168fe6

[jasnell]

See: nodejs/node#26 ... The Intl work also impacted the Build.

[Fishrock123]

src: make build pass with GCC < 4.5

iirc this isn't possible with the v8 we are using, cc @bnoordhuis

[bnoordhuis]

Correct. 4.8 is the absolute minimum.

[jasnell]

Another: c0766eb1a4dac9d9b555be271ef84ad401ba91b0 build: fix use of strict aliasing - nodejs/node-v0.x-archive@c0766eb

[Fishrock123]

Also looks like it should just be dropped, again < 4.8 isn't going to work anyways.

[jasnell]

@misterdjules @mhdawson ... do you know of anything that breaks without this?

[Fishrock123]

Well, older systems that use GCC < 4.8 will break trying to build without having GCC upgraded.

[bnoordhuis]

And, FWIW, the library that was the source of the -Wstrict-aliasing warnings, src/queue.h, was removed in nodejs/node@7e779b4.

[jbergstroem]

Clang could be a simpler install through package managers on those systems. Avoiding the gcc 4.8 is pretty much impossible if we want to use recent/stable v8's.

[jasnell]

Ok, then I think this one is largely decided then. It would require a revert of the io.js changes in order to land. @misterdjules @cjihrig @trevnorris @orangemocha @mhdawson : if any of you think this is going to be a problem, we'll need to make the case to revert before we can proceed. Given that, I'm going to close this issue. We can reopen if new information is presented.

[Fishrock123]

@jasnell Hmmm, isn't the 2nd commit still valid? The windows 32 one?

[jasnell]

Ah! missed that one. Perhaps, reopening until we can confirm