{"thread":{"id":"20360","subject":"msysGit and SCons: broken?","startedAt":"2009-08-03T18:19:47Z","lastAt":"2009-08-15T14:04:28Z","messageCount":6,"participants":["Dirk Süsserott","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"119426","messageId":"4A772A43.8070503@dirk.my1.cc","threadId":"20360","inReplyTo":null,"subject":"msysGit and SCons: broken?","fromName":"Dirk Süsserott","fromEmail":"newsletter@dirk.my1.cc","sentAt":"2009-08-03T18:19:47Z","receivedAt":"2009-08-03T18:19:47Z","isPatch":false,"sender":{"key":"newsletter@dirk.my1.cc","avatar":null},"body":"Hello,\n\nI'm using Git for Windows (1.6.3.2.1299.gee46c) and *used to use* SCons\nas a build tool. Since my last Git-update (from 1.6.1.9.g97c34 to\n1.6.3.2.1299.gee46c) SCons doesn't work an longer. I'm not exactly sure\nthat the Git upgrade made things worse, but I didn't upgrade neither\nSCons (0.98) nor Python (ActivePython 2.4) and now they cease to work.\n\nWhen running in git-bash, SCons tells me \"TypeError: listdir() argument\n1 must be (buffer overflow), not str:\" and some stack trace.\n\nWhen running in native Windows' cmd.exe it works fine.\n\nIs it somehow possible that the Git upgrade broke python scripts? By\nsetting certain ENV vars or something? I don't want to blame someone for\nthis, really, I'm just trying to track down my problem.\n\n\nDirk\n"},{"id":"119437","messageId":"alpine.DEB.1.00.0908040010220.8306@pacific.mpi-cbg.de","threadId":"20360","inReplyTo":"4A772A43.8070503@dirk.my1.cc","subject":"Re: msysGit and SCons: broken?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-08-03T22:13:36Z","receivedAt":"2009-08-03T22:13:36Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 3 Aug 2009, Dirk Süsserott wrote:\n\n> I'm using Git for Windows (1.6.3.2.1299.gee46c)\n\nI suspect the appropriate mailing list would have been the msysGit list, \nthen.\n\n> and *used to use* SCons as a build tool. Since my last Git-update (from \n> 1.6.1.9.g97c34 to 1.6.3.2.1299.gee46c) SCons doesn't work an longer.\n\nWe do not have any SCons (or Python) support in msysGit.  If you want it \nofficially supported, I invite you to provide patches to compile and \ninstall Python (see the recent work on Perl and Subversion).\n\n> I'm not exactly sure that the Git upgrade made things worse, but I \n> didn't upgrade neither SCons (0.98) nor Python (ActivePython 2.4) and \n> now they cease to work.\n> \n> When running in git-bash, SCons tells me \"TypeError: listdir() argument \n> 1 must be (buffer overflow), not str:\" and some stack trace.\n> \n> When running in native Windows' cmd.exe it works fine.\n> \n> Is it somehow possible that the Git upgrade broke python scripts? By \n> setting certain ENV vars or something? I don't want to blame someone for \n> this, really, I'm just trying to track down my problem.\n\nHow does your SCons call relate to Git?  Do you call it from the Git Bash?  \nDo you call it from cmd.exe directly?  Is Git/bash in your PATH?\n\nCiao,\nDscho\n"},{"id":"119823","messageId":"4A7B32EA.2080505@dirk.my1.cc","threadId":"20360","inReplyTo":"alpine.DEB.1.00.0908040010220.8306@pacific.mpi-cbg.de","subject":"Re: msysGit and SCons: broken?","fromName":"Dirk Süsserott","fromEmail":"newsletter@dirk.my1.cc","sentAt":"2009-08-06T19:45:46Z","receivedAt":"2009-08-06T19:45:46Z","isPatch":false,"sender":{"key":"newsletter@dirk.my1.cc","avatar":null},"body":"Am 04.08.2009 00:13 schrieb Johannes Schindelin:\n> On Mon, 3 Aug 2009, Dirk Süsserott wrote:\n> \n> I suspect the appropriate mailing list would have been the msysGit list, \n> then.\n\nSorry, next time I'll have a look there, but I'm more familiar with this \nlist. :-)\n\n> How does your SCons call relate to Git?  Do you call it from the Git Bash?  \n> Do you call it from cmd.exe directly?  Is Git/bash in your PATH?\n\nMy SCons call doesn't actually relate to Git. I just use the Git-bash as \nmy favorite shell under Windows. It's by far better than the regular \ncmd.exe. Despite I'm using Windows, I'm a \"shell person\" and prefer not \nto use only my index finger to direct the computer :-). Git-bash gives \nthat opportunity.\n\nI used to call SCons from Git-bash and it worked. After Git's upgrade \n(or some other unknown change) I did the same and it didn't work from \nGit-bash, but it still worked from cmd.exe. Git-bash ist not in my PATH \nwhen I run cmd.exe.\n\nDon't bother, I just posed the question and hoped someone says \"yeah, I \nfaced the same problem and solved it like this: ...\". I'll use a \nworkaround and post a solution if I find one.\n\n     Dirk\n"},{"id":"120563","messageId":"4A846A5A.4000000@dirk.my1.cc","threadId":"20360","inReplyTo":"4A7B32EA.2080505@dirk.my1.cc","subject":"Re: msysGit and SCons: broken?","fromName":"Dirk Süsserott","fromEmail":"newsletter@dirk.my1.cc","sentAt":"2009-08-13T19:32:42Z","receivedAt":"2009-08-13T19:32:42Z","isPatch":false,"sender":{"key":"newsletter@dirk.my1.cc","avatar":null},"body":"Am 06.08.2009 21:45 schrieb Dirk Süsserott:\n> Am 04.08.2009 00:13 schrieb Johannes Schindelin:\n>> On Mon, 3 Aug 2009, Dirk Süsserott wrote:\n>>\n>> How does your SCons call relate to Git?  Do you call it from the Git \n>> Bash?  Do you call it from cmd.exe directly?  Is Git/bash in your PATH?\n> \n> I used to call SCons from Git-bash and it worked. After Git's upgrade \n> (or some other unknown change) I did the same and it didn't work from \n> Git-bash, but it still worked from cmd.exe. Git-bash ist not in my PATH \n> when I run cmd.exe.\n\nIf someone had the same or a similar problem: I tracked it down and\nfound a solution. The problem was that I tried to run a Windows program\nfrom git-bash. The Windows program then faces the bash's $PATH with a\ndifferent separator (':' vs. ';') and a different root directory ('/c/'\nvs. 'C:/'). Scons tries to split the PATH apart to figure out which\ntools are installed. ActivePython thinks ';' is the right separator and\nthen fails. Thus, I wrote a wrapper to call Scons after manipulating the\n$PATH variable by first exchanging the separator and then exchanging\n'/c/' with 'c:/'.\n\nFunny, though, that my things worked a few weeks ago *without* this\nwrapper. Dunno why. At least it hasn't anything to do with my Git\nupdate. I proved that by installing earlier versions of Git.\n\n\tDirk\n"},{"id":"120590","messageId":"alpine.DEB.1.00.0908132353380.8306@pacific.mpi-cbg.de","threadId":"20360","inReplyTo":"4A846A5A.4000000@dirk.my1.cc","subject":"Re: msysGit and SCons: broken?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-08-13T21:54:20Z","receivedAt":"2009-08-13T21:54:20Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 13 Aug 2009, Dirk Süsserott wrote:\n\n> Am 06.08.2009 21:45 schrieb Dirk Süsserott:\n> > Am 04.08.2009 00:13 schrieb Johannes Schindelin:\n> > > On Mon, 3 Aug 2009, Dirk Süsserott wrote:\n> > >\n> > > How does your SCons call relate to Git?  Do you call it from the Git Bash?\n> > > Do you call it from cmd.exe directly?  Is Git/bash in your PATH?\n> > \n> > I used to call SCons from Git-bash and it worked. After Git's upgrade (or\n> > some other unknown change) I did the same and it didn't work from Git-bash,\n> > but it still worked from cmd.exe. Git-bash ist not in my PATH when I run\n> > cmd.exe.\n> \n> If someone had the same or a similar problem: I tracked it down and \n> found a solution. The problem was that I tried to run a Windows program \n> from git-bash. The Windows program then faces the bash's $PATH with a \n> different separator (':' vs. ';') and a different root directory ('/c/' \n> vs. 'C:/').\n\nI cannot believe that.  I actually run a Windows program very often, from \nGit Bash, and PATH is correctly converted all the time.\n\nCiao,\nDscho"},{"id":"120711","messageId":"4A86C06C.3060409@dirk.my1.cc","threadId":"20360","inReplyTo":"alpine.DEB.1.00.0908132353380.8306@pacific.mpi-cbg.de","subject":"Re: msysGit and SCons: broken?","fromName":"Dirk Süsserott","fromEmail":"newsletter@dirk.my1.cc","sentAt":"2009-08-15T14:04:28Z","receivedAt":"2009-08-15T14:04:28Z","isPatch":false,"sender":{"key":"newsletter@dirk.my1.cc","avatar":null},"body":"Am 13.08.2009 23:54 schrieb Johannes Schindelin:\n> Hi,\n> \n> On Thu, 13 Aug 2009, Dirk Süsserott wrote:\n> \n\n...\n\n>> If someone had the same or a similar problem: I tracked it down and \n>> found a solution. The problem was that I tried to run a Windows program \n>> from git-bash. The Windows program then faces the bash's $PATH with a \n>> different separator (':' vs. ';') and a different root directory ('/c/' \n>> vs. 'C:/').\n> \n> I cannot believe that.  I actually run a Windows program very often, from \n> Git Bash, and PATH is correctly converted all the time.\n> \n> Ciao,\n> Dscho\n\nHmm, I wrote a simple \"hello $PATH\" and it actually DID print the path \nin Windows' flavour when started from Git Bash, like you said. Dunno why \nActivePython ceased to do so as well... Probably I confused my machine \nby extending PATH in Windows and .bashrc with different PATHs in \ndifferent order. Or ActivePython is somehow \"zickig\" (what's that in \nenglish? :-)). However, now it works for me and as SCons is the only \ntool that failed, I see no further need for investigation.\nBtw., I started scons from Git Bash with\n\n   cmd //c C:/Python24/Scripts/scons.bat \"$@\"\n\nMaybe that's a problem, but I don't care any longer.\n\nDirk\n"}]}