[Vm-dev] Why the hell directives for compiling with clang were not taken into account
Tobias Pape
Das.Linux at gmx.de
Mon Apr 2 17:12:43 UTC 2018
> On 02.04.2018, at 15: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
>
> See:
> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/361174043
>
Have you seen this?
https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/361174043#L448
OTOH, I did it that way:
https://github.com/OpenSmalltalk/opensmalltalk-vm/compare/krono/upgrade-gcc#diff-f36a4fd868404ca84d806453aabb6f3bR65
> 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...
>
More information about the Vm-dev
mailing list