Fix #8200 (and reopen #8156)

[kmsquire]

As suggested my @nolta. This seems to fix the build problems in #8200 for me.

Cc: @JeffBezanson

[JeffBezanson]

Why? This is an unstable development version. We should fix it, not just revert things.

[StefanKarpinski]

I think it was causing a lot of trouble. We've also tended not to keep master in a state where it segfaults half of the time.

[kmsquire]

Those two points of view were why I didn't merge right away. :-)

It's been rather difficult to see anything pass on Travis recently, so this
was meant as a stopgap. The best thing is just to fix it, of course, but
that would take me a lot longer than you, Jeff.

Cheers!

On Wednesday, September 3, 2014, Stefan Karpinski notifications@github.com
wrote:

I think it was causing a lot of trouble. We've also tended not to keep
master in a state where it segfaults half of the time.

—
Reply to this email directly or view it on GitHub
#8218 (comment).

[ivarne]

The more stable master is, the more users follow on master and the more people have a incentive to contribute patches and give early feedback on features. The earlier we get bug reports (and fix them) the better impression people will have on Julia, and the more developers we will get to help us reach a 1.0 release.

#8200 is much more annoying than #8156, so until we get a proper fix for the segfault, I think that reverting temporary is a good solution.

[ivarne]

See #8110 (comment), for a concrete example where having this bug scares people away from participating.

[JeffBezanson]

Naturally I would not have pushed these if I saw the segfault locally. Fortunately I can reproduce it on my laptop.

[staticfloat]

Great, I'll release the buildbot back to its business then. :P