Topic: Build svn-4238 broken?

1 — 7 of 7 Posts

Magor Topic Opener Joined: 2009-03-30, 07:38 UTC+2.0 Posts: 36 Pry about Widelands Location: Königswinter, Germany	Posted at: 2009-06-11, 17:34 UTC+2.0 Hi! I just wanted to update, build and play but thus said svn-4238 on OpenSuSE 11.1: scons AttributeError: FS instance has no attribute '_cwd': File "/usr/lib64/python2.6/site-packages/SCons/Script/Main.py", line 1261: _exec_main(parser, values) File "/usr/lib64/python2.6/site-packages/SCons/Script/Main.py", line 1226: _main(parser) File "/usr/lib64/python2.6/site-packages/SCons/Script/Main.py", line 800: fs = SCons.Node.FS.get_default_fs() File "/usr/lib64/python2.6/site-packages/SCons/Node/FS.py", line 2891: default_fs = FS() File "/usr/lib64/python2.6/site-packages/SCons/Node/FS.py", line 1051: self.Top = self.Dir(self.pathTop) File "/usr/lib64/python2.6/site-packages/SCons/Node/FS.py", line 1214: return self._lookup(name, directory, Dir, create) File "/usr/lib64/python2.6/site-packages/SCons/Node/FS.py", line 1163: directory = self._cwd make: *** [warning] Fehler 2 Looks like this scons thingy has a bad day... Never trusted that bugger Yours, Magor Top Quote

Nasenbaer Joined: 2009-02-21, 18:17 UTC+1.0 Posts: 826 One Elder of Players Location: Germany	Posted at: 2009-06-12, 09:43 UTC+2.0 can not confirm - using Mandriva Linux 2009.1 - seems to be a scons problem so good you did not trust it Which scons version do you use? does 1) deleting the "build" dir in widelands svn directory + 2) running svn up for getting a clean "build" again resolve the problem? Cheers Nasenbaer Top Quote

Dwarik Joined: 2009-05-11, 17:50 UTC+2.0 Posts: 42 Pry about Widelands	Posted at: 2009-06-12, 13:02 UTC+2.0 also another question, did you try building widelands before (and succeeded with another version?) Top Quote

Magor Topic Opener Joined: 2009-03-30, 07:38 UTC+2.0 Posts: 36 Pry about Widelands Location: Königswinter, Germany	Posted at: 2009-06-15, 12:12 UTC+2.0 Nasenbaer wrote: can not confirm - using Mandriva Linux 2009.1 - seems to be a scons problem so good you did not trust it Which scons version do you use? `script: v1.1.0.d20081125.r3795, 2008/11/25 22:04:43, by scons on scons-dev engine: v1.1.0.d20081125.r3795, 2008/11/25 22:04:43, by scons on scons-dev` does 1) deleting the "build" dir in widelands svn directory + 2) running svn up for getting a clean "build" again resolve the problem? Don't know, but I doubt it, as I did not change any params manually, and scons died before it even started to get all the build environment information. SVN-4244 or earlier fixed that problem. Edited: 2009-06-15, 12:12 UTC+2.0 Top Quote

Magor Topic Opener Joined: 2009-03-30, 07:38 UTC+2.0 Posts: 36 Pry about Widelands Location: Königswinter, Germany	Posted at: 2009-06-15, 12:14 UTC+2.0 Dwarik wrote: also another question, did you try building widelands before (and succeeded with another version?) I build widelands regularly from svn, about once or twice a week, usually successful Yours, Magor Top Quote

Dwarik Joined: 2009-05-11, 17:50 UTC+2.0 Posts: 42 Pry about Widelands	Posted at: 2009-06-15, 12:29 UTC+2.0 If nasenbears sugestion doesn't work what is the exact command you are using when invoking scons run 'scons -c' run 'svn update' can you provide a dump of the output you get if you add '--debug=stree' to scons. did you recently update scons? maybe try updating to scons v 1.2 if you have an package of that available Top Quote

Dwarik Joined: 2009-05-11, 17:50 UTC+2.0 Posts: 42 Pry about Widelands	Posted at: 2009-06-15, 12:29 UTC+2.0 looking at your other post i guess you got it working Top Quote

1 — 7 of 7 Posts