Menu
▾
▴
tcl-mac — Q&A for Tcl on the Macintosh platform
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(20) |
Mar
(29) |
Apr
(10) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(59) |
Sep
(19) |
Oct
(55) |
Nov
(22) |
Dec
(40) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(56) |
Feb
(71) |
Mar
(179) |
Apr
(41) |
May
(26) |
Jun
(52) |
Jul
(62) |
Aug
(19) |
Sep
(87) |
Oct
(188) |
Nov
(95) |
Dec
(30) |
| 2003 |
Jan
(83) |
Feb
(119) |
Mar
(174) |
Apr
(77) |
May
(85) |
Jun
(52) |
Jul
(67) |
Aug
(121) |
Sep
(147) |
Oct
(96) |
Nov
(89) |
Dec
(144) |
| 2004 |
Jan
(92) |
Feb
(172) |
Mar
(205) |
Apr
(201) |
May
(105) |
Jun
(42) |
Jul
(94) |
Aug
(109) |
Sep
(81) |
Oct
(59) |
Nov
(84) |
Dec
(68) |
| 2005 |
Jan
(56) |
Feb
(57) |
Mar
(183) |
Apr
(139) |
May
(131) |
Jun
(178) |
Jul
(62) |
Aug
(42) |
Sep
(95) |
Oct
(47) |
Nov
(73) |
Dec
(47) |
| 2006 |
Jan
(66) |
Feb
(31) |
Mar
(51) |
Apr
(20) |
May
(49) |
Jun
(26) |
Jul
(23) |
Aug
(65) |
Sep
(67) |
Oct
(26) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(18) |
Feb
(43) |
Mar
(43) |
Apr
(16) |
May
(33) |
Jun
(48) |
Jul
(34) |
Aug
(7) |
Sep
(9) |
Oct
(55) |
Nov
(44) |
Dec
(73) |
| 2008 |
Jan
(37) |
Feb
(97) |
Mar
(44) |
Apr
(33) |
May
(79) |
Jun
(11) |
Jul
(66) |
Aug
(9) |
Sep
(12) |
Oct
(6) |
Nov
(12) |
Dec
(19) |
| 2009 |
Jan
(12) |
Feb
(13) |
Mar
(19) |
Apr
(30) |
May
(59) |
Jun
(22) |
Jul
(11) |
Aug
(59) |
Sep
(82) |
Oct
(25) |
Nov
(51) |
Dec
(27) |
| 2010 |
Jan
(27) |
Feb
(8) |
Mar
(29) |
Apr
(9) |
May
(39) |
Jun
(6) |
Jul
(8) |
Aug
(22) |
Sep
(33) |
Oct
(8) |
Nov
(35) |
Dec
(9) |
| 2011 |
Jan
(62) |
Feb
(19) |
Mar
(31) |
Apr
(19) |
May
(1) |
Jun
(1) |
Jul
(17) |
Aug
(10) |
Sep
(14) |
Oct
(11) |
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
(11) |
Mar
|
Apr
(1) |
May
(5) |
Jun
(7) |
Jul
(22) |
Aug
(22) |
Sep
(30) |
Oct
(23) |
Nov
(19) |
Dec
|
| 2013 |
Jan
(6) |
Feb
(1) |
Mar
(10) |
Apr
(7) |
May
(3) |
Jun
(3) |
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(14) |
Nov
(9) |
Dec
(5) |
| 2014 |
Jan
(13) |
Feb
(1) |
Mar
(6) |
Apr
(3) |
May
(5) |
Jun
(2) |
Jul
(20) |
Aug
(6) |
Sep
(26) |
Oct
(25) |
Nov
(20) |
Dec
(41) |
| 2015 |
Jan
(9) |
Feb
(35) |
Mar
(9) |
Apr
(28) |
May
(20) |
Jun
(3) |
Jul
(5) |
Aug
|
Sep
(2) |
Oct
(4) |
Nov
|
Dec
(3) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
(12) |
Jun
(35) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(7) |
| 2017 |
Jan
(28) |
Feb
(14) |
Mar
(4) |
Apr
(5) |
May
(4) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
(8) |
| 2018 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(7) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(3) |
Nov
(7) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(10) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(4) |
Apr
(21) |
May
(8) |
Jun
(3) |
Jul
|
Aug
|
Sep
(1) |
Oct
(10) |
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: G 3 <pro...@gm...> - 2017-01-23 14:21:58
|
On Jan 23, 2017, at 8:16 AM, Kevan Hashemi wrote: >> Thank you so much! I successfully built TclTk 8.5.8. I was even >> able to update Python to use this new version. :) > > Splendid. What system did you compile on? Did you compile for both > Intel and PPC at the same time? Yours, Kevan I compiled on an iMac G5 running Mac OS 10.4. I didn't compile for both Intel and PowerPC, but a future build will be built that way. Thanks again. |
|
From: Kevan H. <ha...@br...> - 2017-01-23 13:41:10
|
> Thank you so much! I successfully built TclTk 8.5.8. I was even able to > update Python to use this new version. :) Splendid. What system did you compile on? Did you compile for both Intel and PPC at the same time? Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/ |
|
From: G 3 <pro...@gm...> - 2017-01-21 16:57:15
|
On Jan 20, 2017, at 10:13 AM, Kevan Hashemi wrote: >> I didn't know TclTk 8.5.8 was compatible with Mac OS 10.4. Did you >> build it on Mac OS 10.4? > > Yes. Actually, it looks like I built both the Intel and PPC > versions on a PPC 10.4 machine, because that was the safest way to > do it. Scroll down from this link for note on the build. > > http://alignment.hep.brandeis.edu/Electronics/LWDAQ/Manual.html#MacOS > > Yours, Kevan Thank you so much! I successfully built TclTk 8.5.8. I was even able to update Python to use this new version. :) |
|
From: Kevan H. <ha...@br...> - 2017-01-20 15:13:54
|
> I didn't know TclTk 8.5.8 was compatible with Mac OS 10.4. Did you build > it on Mac OS 10.4? Yes. Actually, it looks like I built both the Intel and PPC versions on a PPC 10.4 machine, because that was the safest way to do it. Scroll down from this link for note on the build. http://alignment.hep.brandeis.edu/Electronics/LWDAQ/Manual.html#MacOS Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/ |
|
From: G 3 <pro...@gm...> - 2017-01-20 14:53:44
|
On Jan 20, 2017, at 9:49 AM, Kevan Hashemi wrote: > Deasr G3, > > I mis-typed. My application runs in TclTK 8.5.8. I have TclTk 8.5.8 > binaries for MacOS 10.4 (PPC), MacOS 10.4+ (Intel), Windows, and > Linux. I didn't know TclTk 8.5.8 was compatible with Mac OS 10.4. Did you build it on Mac OS 10.4? Thanks. > > I did use TclTk 8.4.x before I moved to TclTk 8.5.8. I'm not sure > if I ever used 8.5.20. But you don't have to go back that far if > you want to run on MacOS 10.4. > > Yours, Kevan > > G 3 wrote: >> On Jan 20, 2017, at 8:08 AM, Kevan Hashemi wrote: >>>> If you want to run 10.4, use an older version of Tk, such as >>>> 8.4.20. >>> >>> Indeed. My application runs in 10.5.8, and works fine on 10.4 and >>> up. The TclTk binaries are bundled with the application, and >>> there are PPC and Intel versions for MacOS, as well as version >>> for Windows and Linux. >> Do you use version 8.4.20? How is it? >> I don't want the Apple version (8.4.7) anymore. It's a little too >> buggy. > > -- > Kevan Hashemi, Electrical Engineer > Physics Department, Brandeis University > http://alignment.hep.brandeis.edu/ |
|
From: Kevan H. <ha...@br...> - 2017-01-20 14:49:40
|
Deasr G3, I mis-typed. My application runs in TclTK 8.5.8. I have TclTk 8.5.8 binaries for MacOS 10.4 (PPC), MacOS 10.4+ (Intel), Windows, and Linux. I did use TclTk 8.4.x before I moved to TclTk 8.5.8. I'm not sure if I ever used 8.5.20. But you don't have to go back that far if you want to run on MacOS 10.4. Yours, Kevan G 3 wrote: > > On Jan 20, 2017, at 8:08 AM, Kevan Hashemi wrote: > >>> If you want to run 10.4, use an older version of Tk, such as 8.4.20. >> >> Indeed. My application runs in 10.5.8, and works fine on 10.4 and up. >> The TclTk binaries are bundled with the application, and there are PPC >> and Intel versions for MacOS, as well as version for Windows and Linux. > > Do you use version 8.4.20? How is it? > > I don't want the Apple version (8.4.7) anymore. It's a little too buggy. > > -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/ |
|
From: G 3 <pro...@gm...> - 2017-01-20 14:41:08
|
On Jan 20, 2017, at 8:08 AM, Kevan Hashemi wrote: >> If you want to run 10.4, use an older version of Tk, such as 8.4.20. > > Indeed. My application runs in 10.5.8, and works fine on 10.4 and > up. The TclTk binaries are bundled with the application, and there > are PPC and Intel versions for MacOS, as well as version for > Windows and Linux. Do you use version 8.4.20? How is it? I don't want the Apple version (8.4.7) anymore. It's a little too buggy. |
|
From: Kevan H. <ha...@br...> - 2017-01-20 13:34:16
|
> If you want to run 10.4, use an older version of Tk, such as 8.4.20. Indeed. My application runs in 10.5.8, and works fine on 10.4 and up. The TclTk binaries are bundled with the application, and there are PPC and Intel versions for MacOS, as well as version for Windows and Linux. -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/ |
|
From: Kevin W. <kw...@co...> - 2017-01-20 04:09:25
|
On 1/19/17 9:06 PM, G 3 wrote: > What if someone made a patch that changed a few lines in the Cocoa > code of Tk and made them compatible with Mac OS 10.4 and higher. This > patch would contain no Carbon calls, only Cocoa calls. Would that > patch be accepted? It's going to be far more than "a few lines of code." Tk-Cocoa relies on the Objective-C 2.0 runtime, which wasn't released until 10.5. Given that this is the foundation of the Cocoa version of Tk, I'm not inclined to commit anything that rips it out, nor am I inclined to include a massive set of ifdef bits to get it to build on an operating system that Apple stopped supporting years ago. That's simply needless complexity. May I ask why you are staying with such an old verison of macOS? -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: G 3 <pro...@gm...> - 2017-01-20 02:06:48
|
On Jan 19, 2017, at 8:57 PM, Kevin Walzer wrote: > On 1/19/17 8:53 PM, G 3 wrote: >> >> On Jan 19, 2017, at 7:41 PM, Kevin Walzer wrote: > >> If someone were to make a patch that allowed for using both the >> new and old API's together, would it be accepted? >> >> > No, it's not that simple. Versions of Tk that run natively on 10.4 > are based on the Carbon API, which was deprecated by Apple and > stopped being supported in Tk in 8.5 around 8.5.15 or so. 8.5.16 > onward and 8.6 support the Cocoa API, which is a complete rewrite. > The Cocoa version nominally requires 10.5 to run, but practically > speaking it won't build on anything older than 10.6. > > If you want to run 10.4, use an older version of Tk, such as 8.4.20. The Cocoa framework was available on Mac OS X since 10.0. Actually before that, but that would be going into the public beta / NeXTSTEP OS territory. What if someone made a patch that changed a few lines in the Cocoa code of Tk and made them compatible with Mac OS 10.4 and higher. This patch would contain no Carbon calls, only Cocoa calls. Would that patch be accepted? |
|
From: Kevin W. <kw...@co...> - 2017-01-20 01:57:15
|
On 1/19/17 8:53 PM, G 3 wrote: > > On Jan 19, 2017, at 7:41 PM, Kevin Walzer wrote: > If someone were to make a patch that allowed for using both the new > and old API's together, would it be accepted? > > No, it's not that simple. Versions of Tk that run natively on 10.4 are based on the Carbon API, which was deprecated by Apple and stopped being supported in Tk in 8.5 around 8.5.15 or so. 8.5.16 onward and 8.6 support the Cocoa API, which is a complete rewrite. The Cocoa version nominally requires 10.5 to run, but practically speaking it won't build on anything older than 10.6. If you want to run 10.4, use an older version of Tk, such as 8.4.20. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: G 3 <pro...@gm...> - 2017-01-20 01:53:46
|
On Jan 19, 2017, at 7:41 PM, Kevin Walzer wrote: > On 1/19/17 12:22 PM, G 3 wrote: >> So the question is where in the makefile is the unix configure >> command called? > > The canonical way to build Tcl/Tk natively on the Mac is to go into > the top level of the source tree and run the following commands: > > make -C tcl$version/macosx > make -C tk$version/macosx > > and then repeat: > > make -C tcl$version/macosx install > make -C tk$version/macosx install > > But 8.6 won't work on 10.4--it calls into API's that don't exist on > that platform. If someone were to make a patch that allowed for using both the new and old API's together, would it be accepted? |
|
From: Kevin W. <kw...@co...> - 2017-01-20 00:41:16
|
On 1/19/17 12:22 PM, G 3 wrote: > So the question is where in the makefile is the unix configure command > called? The canonical way to build Tcl/Tk natively on the Mac is to go into the top level of the source tree and run the following commands: make -C tcl$version/macosx make -C tk$version/macosx and then repeat: make -C tcl$version/macosx install make -C tk$version/macosx install But 8.6 won't work on 10.4--it calls into API's that don't exist on that platform. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: G 3 <pro...@gm...> - 2017-01-19 17:59:34
|
On Jan 19, 2017, at 12:49 PM, Scott Redman wrote: > There's a file in the macosx directory called GNUmakefile, and in > there is a target to call configure in $UNIX_DIR, roughly line 130 > (tcl8.6.6). Thank you. > Is it possible to use the unix target instead? Yes. That is what the TigerBrew package manager uses. I just made a patch that fixes an issue with the sqlite to make it compile on Mac OS 10.4. The patch is at the end of this file: http:// www.mediafire.com/file/g6phuehuq3kjx5w/replacement_tcl-tk.txt. > In fact, is that why it was working in Tkinter? Currently the answer is yes. I do hope to make the aqua version of Tk work soon. > > -- Scott > > > -------------------------------------------- > On Thu, 1/19/17, G 3 <pro...@gm...> wrote: > > Subject: Re: [MACTCL] Bug with tcl configure command - wrong > compiler used > To: kw...@co... > Cc: tc...@li..., "Scott Redman" > <sc...@re...> > Date: Thursday, January 19, 2017, 9:22 AM > > > On Jan > 19, 2017, at 8:39 AM, Kevin Walzer wrote: > >> What version of macOS are > you building on? Current versions of Tcl/ >> Tk won't build on anything older than > 10.6, at least not the native >> > version. X11 might still work. > > I am using Mac OS 10.4. Tcl/Tk can be build on > older versions of Mac > OS X. I was able to > use Tk 8.6 with Tkinter (python Tk interface) on > X11. Regardless of my version of Mac OS X, > there are issues with the > build process. > When the user specifies a compiler, it is expected > that all source code built is built using that > compiler. My theory is > to pass all the > environmental variables that the tk/macosx/makefile > knows to any configure command it calls. > > So the question is where in > the makefile is the unix configure > command called? > > > > > ---------------------------------------------------------------------- > -------- > 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 > |
|
From: G 3 <pro...@gm...> - 2017-01-19 17:22:43
|
On Jan 19, 2017, at 8:39 AM, Kevin Walzer wrote: > What version of macOS are you building on? Current versions of Tcl/ > Tk won't build on anything older than 10.6, at least not the native > version. X11 might still work. I am using Mac OS 10.4. Tcl/Tk can be build on older versions of Mac OS X. I was able to use Tk 8.6 with Tkinter (python Tk interface) on X11. Regardless of my version of Mac OS X, there are issues with the build process. When the user specifies a compiler, it is expected that all source code built is built using that compiler. My theory is to pass all the environmental variables that the tk/macosx/makefile knows to any configure command it calls. So the question is where in the makefile is the unix configure command called? |
|
From: Kevin W. <kw...@co...> - 2017-01-19 13:39:43
|
What version of macOS are you building on? Current versions of Tcl/Tk won't build on anything older than 10.6, at least not the native version. X11 might still work. -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: G 3 <pro...@gm...> - 2017-01-19 05:43:12
|
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 > |
|
From: Scott R. <sco...@sb...> - 2017-01-18 18:40:13
|
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.
Try doing:
CC=gcc-5 make
-- 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
|
|
From: G 3 <pro...@gm...> - 2017-01-18 18:04:09
|
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. |
|
From: Kevin W. <kw...@co...> - 2017-01-18 11:21:37
|
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. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Kevin W. <kw...@co...> - 2017-01-18 11:20:28
|
On 1/17/17 10:25 PM, G 3 wrote: > http://wiki.tcl.tk/12945 > > This page titled "Building Stand-Alone Tcl/Tk Applications under Mac > OS X", has a few issues with it that I thought I should report. > > The links that are labeled [1], [3], [4], and [5] are dead. > > In the line of text that says "including an applicaton-specific > icon", it should replace applicaton with application. > > Hope this is the right place to report such an issue. Thank you for > any help that can be provided. > As it is a wiki, you are welcome to edit the page, clean up dead links, etc. That would be much appreciated, in fact. -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: G 3 <pro...@gm...> - 2017-01-18 05:58:56
|
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. |
|
From: G 3 <pro...@gm...> - 2017-01-18 03:25:23
|
http://wiki.tcl.tk/12945 This page titled "Building Stand-Alone Tcl/Tk Applications under Mac OS X", has a few issues with it that I thought I should report. The links that are labeled [1], [3], [4], and [5] are dead. In the line of text that says "including an applicaton-specific icon", it should replace applicaton with application. Hope this is the right place to report such an issue. Thank you for any help that can be provided. |
|
From: G 3 <pro...@gm...> - 2017-01-18 03:21:19
|
On Jan 16, 2017, at 5:13 PM, G 3 wrote: > > On Jan 16, 2017, at 3:44 PM, Kevin Walzer wrote: > >> On 1/16/17 2:39 PM, G 3 wrote: >>> After installing TCL-TK 8.6.6, I saw this error message when I tried >>> to use the Tk framework in Python: >>> _tkinter.TclError: no display name and no $DISPLAY environment >>> variable >>> >>> Anyone know of a fix for this issue? >>> >>> -------------------------------------------------------------------- >>> ---------- >>> 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 >>> >> Sounds like Python is looking for an X11 version of Tk, not the >> native one. > > That does make sense. Just to note that after opening Python in X11, I was able to use this version of the Tk framework. The problem with the missing $DISPLAY variable is because the package manager I use has the unix target built on Mac OS X instead of the macosx target. The downside of this is all the widgets has that motif look. The 3D aqua look is not available. |
|
From: G 3 <pro...@gm...> - 2017-01-16 22:14:02
|
On Jan 16, 2017, at 3:44 PM, Kevin Walzer wrote: > On 1/16/17 2:39 PM, G 3 wrote: >> After installing TCL-TK 8.6.6, I saw this error message when I tried >> to use the Tk framework in Python: >> _tkinter.TclError: no display name and no $DISPLAY environment >> variable >> >> Anyone know of a fix for this issue? >> >> --------------------------------------------------------------------- >> --------- >> 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 >> > Sounds like Python is looking for an X11 version of Tk, not the > native one. That does make sense. |
9 messages has been excluded from this view by a project administrator.
