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

K K Subbu kksubbu.ml at gmail.com
Mon Apr 2 16:29:53 UTC 2018


The extract was from win32 build only but on the Cog branch. My bad :-(.

ifeq can be tricky. Try replacing the ifeq in Makefile.tools with:

COMPILER_TO_USE ?= gcc

and then try

$ make COMPILER_TO_USE=clang

You could also add this target at the end of Makefile.

echo.% :
	@echo $($(*))

and then run

$ make COMPILER_TO_USE=clang echo.COMPILER_TO_USE

to debug your rules.

HTH .. Subbu

On Monday 02 April 2018 09:15 PM, Nicolas Cellier wrote:
> Hi Subbu, thanks,
> this apply to windows build only, not linux build
> it means that if the variable is not set, then use gcc as default.
> But what I did in windows build is to explicitely set 
> COMPILER_TO_USE:=clang in the pharo.sista.spur/Makefile
> See
> https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/37d4a3d39933227e305bf2610a0ec685e6f101d2
> 
> 2018-04-02 17:40 GMT+02:00 K K Subbu <kksubbu.ml at gmail.com 
> <mailto:kksubbu.ml at gmail.com>>:
> 
> 
>     On Monday 02 April 2018 07:21 PM, Nicolas Cellier wrote:
> 
> 
>         Gah!
> 
>         despite my stuttutututter command:
>               CC=clang ./configure CC=clang
>         the travis build is completely ignoring the directives and keep
>         using gcc
> 
> 
>     I found the following clue in build.win32x86/common/Makefile.tools
>     -----
>       10 ifeq ($(COMPILER_TO_USE),)
>       11 COMPILER_TO_USE:=gcc
>       12 endif
>     --------------------------
> 
>     HTH .. Subbu
> 
> 



More information about the Vm-dev mailing list