[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Compile sista with clang (#235)

[Nicolas Cellier]

This builds pharo.sista.spur with clang in order to workaround gcc bugs
This also re-arrange the build matrix order for appveyor and build stages order for travis
This also fix a compiler warning for ALSA sound, necessary for compiling with clang (it's treated as an error in clang, not in gcc)

[ci skip] the build is green in its branch and no concurrent feature happened, so let's not wait another pair of hours.
You can view, comment on, or merge this pull request online at:

  https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/235

-- Commit Summary --

  * Try and compile build.win32x86/pharo.sista.spur with clang to workaround gcc compiler bug
  * Fix compilation error of ALSA sound with clang
  * Compile linux32x86/pharo.sista.spur with clang
  * Retry compilation of  linux32x86 pharo.sista.spur with clang
  * Retry win32 pharo.cog.spur.lowcode with clang too
  * Retry download cygwin setup 4x with curl
  * Fix whitespace typo
  * Add a main build stage for Squeak and Pharo
  * Reorder the appveyor matrix so as to put main Squeak/Pharo build first
  * Try to force CC=clang in the .travis.yml matrix for linux32x86 pharo.sista.spur
  * Yet another incantation for compiling pharo.sista.spur with clang

-- File Changes --

    M .appveyor.yml (36)
    M .travis.yml (32)
    M build.linux32x86/pharo.sista.spur/build/mvm (3)
    M build.win32x86/pharo.cog.spur.lowcode/Makefile (2)
    M build.win32x86/pharo.sista.spur/Makefile (4)
    M platforms/unix/vm-sound-ALSA/sqUnixSoundALSA.c (2)

-- Patch Links --

https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/235.patch
https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/235.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/235
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180402/fe73c51c/attachment-0001.html>