Re: [MACTCL] Bug with tcl configure command - wrong compiler used

[G 3 <pro...@gm...>]

On Jan 18, 2017, at 1:26 PM, Scott Redman wrote:

> This sounds like an issue with configure and/or the makefile.
>
> I haven't built on MacOS yet, but looking at the configure scripts  
> and makefiles for 8.6.6, it seems there is an extra call to  
> configure that happens when you run "make" in the macosx directory  
> to re-run configure in the unix directory, which is then used to  
> build.  Not clear that this step is passing the CC variable down  
> into the unix directory's configure when it does that.

It does not sent all the variables to the unix/configure command.  
Using preprocessor macros I was able to verify this.

>
> Try doing:
>      CC=gcc-5 make
>

Thanks for the suggestion. It unfortunately didn't work.


> -- Scott
>
>
>
> --------------------------------------------
> On Wed, 1/18/17, G 3 <pro...@gm...> wrote:
>
>  Subject: Re: [MACTCL] Bug with tcl configure command - wrong  
> compiler used
>  To: kw...@co...
>  Cc: tc...@li...
>  Date: Wednesday, January 18, 2017, 10:04 AM
>
>
>  On Jan
>  18, 2017, at 6:21 AM, Kevin Walzer wrote:
>
>> On 1/18/17 12:58 AM, G 3
>  wrote:
>>> When I specified gcc-5 to
>  compile Tcl, the Apple supplied gcc is used
>>> instead.
>>>
>>> How to reproduce this problem:
>>>
>>> cd to the
>  Tcl8.6.6 folder
>>> ./configure
>  --enable-framework=on CC=gcc-5
>>>
>  make
>>>
>>> What
>  I noticed:
>>>
>>>
>  When I ran the 'make' command, I saw this line in
>  another configure
>>> output that
>  ran:
>>> "checking for gcc...
>  gcc"
>>>
>>>
>  It said this for the above configure command:
>>>
>>> checking for
>  gcc... gcc-5
>>>
>>> It looks like during the
>  'make' phase, the right gcc version to use
>>> is forgotten.
>>>
>>> Note: running
>  "CC=gcc-5 ./configure --enable-framework=on" does
>  not
>>> help.
>>>
>> You mentioned
>  earlier you are using a package manager. Which one? This
>> seems like a path conflict, i.e. the wrong
>  compiler is being found.
>
>  I
>  was using TigerBrew. This problem was discovered when I was
>  not
>  using the package manager. I was
>  building using the "configure ;
>  make
>  ; make install" way.
>
>
>   
> ---------------------------------------------------------------------- 
> --------
>  Check out the vibrant tech community on one of
>  the world's most
>  engaging tech sites,
>  SlashDot.org! http://sdm.link/slashdot
>  _______________________________________________
>  Tcl-mac mailing list
>  tc...@li...
>  https://lists.sourceforge.net/lists/listinfo/tcl-mac
>