[Vm-dev] Why the hell directives for compiling with clang were not taken into account

Ben Coman btc at openinworld.com
Mon Apr 2 14:15:58 UTC 2018


On 2 April 2018 at 21:51, Nicolas Cellier <
nicolas.cellier.aka.nice at gmail.com> wrote:

>
> Gah!
>
> despite my stuttutututter command:
>     CC=clang ./configure CC=clang
> the travis build is completely ignoring the directives and keep using gcc
>

Maybe... "You can test projects against either GCC or Clang, or both.
To do so, specify the compiler to use using the 'compiler:' key in
.travis.yml."
https://docs.travis-ci.com/user/languages/c/#Choosing-compilers-to-test-against

cheers -ben


>
> See:
> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/361174043
>
> I suspect that it's lack of clean build, but not sure...
>
> Building OpenSmalltalk VM in /home/travis/build/OpenSmalltalk/opensmalltalk-vm/build.linux32x86/pharo.sista.spur/build.itimerheartbeat...
> Re-exec as x86
> clean? ok but this isn't safe!!
>
> Or would the clang compiler be absent?
> Or what?
>
> It ain't fun...
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180402/18578457/attachment.html>


More information about the Vm-dev mailing list