Community
Participate
Working Groups
For some reason, $PWD (and CWD) is defined automatically for new build configurations. This confuses the hell out of configure which declares the build environment insane. By undefining PWD in the settings, things are fine. There is probably a way to undefine this env var in your config. I'll also pursue turning off these by default in the cdt-dev list. I can't remember why they are there to begin with other than some old version of make that needed them, or something.
From other bug: (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 think it is pretty important to get this fix into Indigo. Configure is run when you create the project and it spits out an error. Not a good experience. Thanks, Jeff!
Created attachment 196697 [details] Proposed fix. I have attached a proposed fix for this problem. Please try it out ASAP and let me know. Please try using some of the autotools commands from the Project menu to ensure they aren't busted by the change. If all works, I'll check it in right away.
Looks good. And works! Thanks, Jeff.
Closing.
