Oolite Bulletins

Frame, try this rxvt, straight from the MinGW site downloads:
http://sourceforge.net/projects/mingw/f ... t-2.7.2-3/
This is quite new and might do the job for you.

no same deal, however there is a black line at the bottom of the zillion windows it opens...

This may not work at all, but given the situation, you have nothing to lose: What if you take the files in the bin folder of the MSYS version that works for you and copy them over to the bin folder of the MSYS provided with the environment?

Frame wrote:

no same deal, however there is a black line at the bottom of the zillion windows it opens...

I like that approach, when all else fails, use brute force..

and...

Succes... It starts up...

ill inform you about building when im done svn checkout and hopefully building..

Cheers Frame...

It works, i build a debug version straight away, and it works,

its odd though, i kept the original rxvt.exe file, and it is the same version as you supply, however the sizes in kb differs, ofcourse this can come from different settings in regard to speed or size settings when the build is being made.

my Gnustep from which i copied from was allegedly called 0.22 which you refer to as 1.18, which you refers to as outdated, so im fearing that this bug has been reintroduced in Gnustep, since it must have worked at some point.. im just getting confused about the similar version numbers for something so related...

Now back to tracing the Random Hits crash, and does it happen at all now, and where was that gdb trackback thingi... ..

Cheers Frame... thanks for your help another_commander

Good that you got it working Frame. Note though that GNUstep and MSYS are totally unrelated things. Whatever the problem was with rxvt spawning windows, it has nothing to do with the version of GNUstep itself. It may be that GNUstep packages contain MSYS as part of the package, but this was by no means a GNUstep bug.

another_commander wrote:

Good that you got it working Frame. Note though that GNUstep and MSYS are totally unrelated things. Whatever the problem was with rxvt spawning windows, it has nothing to do with the version of GNUstep itself. It may be that GNUstep packages contain MSYS as part of the package, but this was by no means a GNUstep bug.

oh thanks for clearing that up for me... I'm not to well acquainted with GNUstep so i'm not sure what belongs to what.. ..

Need some help here.

My computer crashed during build. I now get multiple error messages of the "NUL character seen" kind, and then the three interrupt massages as seen below when trying to compile trunk. Any easy way to force a complete download of svn to see if that helps.

Gimi wrote:

Need some help here.

My computer crashed during build. I now get multiple error messages of the "NUL character seen" kind, and then the three interrupt massages as seen below when trying to compile trunk.

Code: Select all

obj.spk/oolite.obj/OODebugMonitor.m.d:135: warning: NUL character seen; rest of line ignored
make[2]: *** [internal-objc_program-all_] Interrupt
make[1]: *** [oolite.all.objc-program.variables] Interrupt
make: *** [internal-all] Interrupt

Any easy way to force a complete download of svn to see if that helps.

Try renaming or deleting the folder where trunk currently resides in your disk, then do a fresh SVN checkout as per instructions in the first post. I am not sure what happened there; I have never seen this message before, but I would think a fresh checkout has good chances of fixing it.

another_commander wrote:

Try renaming or deleting the folder where trunk currently resides in your disk, then do a fresh SVN checkout as per instructions in the first post. I am not sure what happened there; I have never seen this message before, but I would think a fresh checkout has good chances of fixing it.

Thank you A_C. That worked a treat. Back on track.

Get the following when I try to update trunk:
Then it just sits there doing nothing.

If I interrupt and do another svn up I get this: Doing an svn cleanup and then a svn up again just reverts to the first message.

Any ideas, has the repository been locked for all except the developers now?

Have you tried repeatedly, or was this all in one sitting? It could well be one of BerliOS’s many and varied glitches.

I am getting a 403:Forbidden response when I try to svn up. Time for a support call to the Berlios admins I think.

Ahruman wrote:

Have you tried repeatedly, or was this all in one sitting? It could well be one of BerliOS’s many and varied glitches.

Tried several times over the last few hours with no joy, rebooting in the process as well.

Looks like HTTP access is down, but SVN protocol access is up. Gimi, try svn checkout svn://svn.berlios.de/oolite-linux/trunk .