Community
Participate
Working Groups
Just tested autotools on Windows and I see that autoreconf is called using runCommand. It needs to be called with runShell so that it runs correctly on Windows.
The code is indeed calling runScript as part of the build. Are you by any chance using the latest Indigo RC1? The fix for runScript and autoreconf is not in this build. It will be in RC2.
I actually checked out the code from git running the master branch. I tried to create a patch but egit is broken right now for that (separate bug has been raised). Once I got passed the runScript issue, I ran into two other issues. For some reason MSYS wasn't happy with 'sh reconfig -i', and I had to change it to 'sh -c "reconfig -i"'. Then once I got past that, I found the PWD environment variable that CDT automatically sets to screw up configure. I just filtered it out before passing it to the launcher. I haven't checked but that may fix up the -c issue.
Created attachment 196477 [details] current java file I have attached the current AutotoolsNewMakeGenerator.java. Perhaps I am missing something, but autoreconf is using runScript which has your patch for adding sh -c to it for Windows. Could you do a diff between your file and this one to make a patch? If there is another file in question, let me know and I'll attach it here so you can do a diff and make a local patch.
Ah, there we go. I did a pull and have the updated source. The only thing left is to filter out the PWD environment variable when calling the script. configure still fails because of that.
(In reply to comment #4) > Ah, there we go. I did a pull and have the updated source. > > The only thing left is to filter out the PWD environment variable when calling > the script. configure still fails because of that. Do you have a patch for this? Is it simply to filter out PWD in the environment list loop when the tests that you added for using the runScript are true? It's cutting it close for Indigo as RC2 is already out. You have https://bugs.eclipse.org/bugs/show_bug.cgi?id=343879 open for the PWD issue
(In reply to comment #5) > (In reply to comment #4) > > Ah, there we go. I did a pull and have the updated source. > > > > The only thing left is to filter out the PWD environment variable when calling > > the script. configure still fails because of that. > > Do you have a patch for this? Is it simply to filter out PWD in the > environment list loop when the tests that you added for using the runScript are > true? It's cutting it close for Indigo as RC2 is already out. You have > https://bugs.eclipse.org/bugs/show_bug.cgi?id=343879 open for the PWD issue Ah, too many things going on at once :). Yes it is as simple as filtering out in the loop. And we'll look to post Indigo to turn it off for everyone. I'll copy this comment into 343879 and we can use that for this fix.
