On Tue, Feb 24, 2009 at 12:00:44AM +0100, Jan-Jaap van der Geer wrote: > I have spend a lot of time trying to get the GCCSDK stuff working > on cygwin, but in the end I have given up. It just failed seemingly > at random places. Not only at the instructions for building the > GCCSDK but also on different things. I even tried another machine, > but either something is really wrong with cygwin or I must have > done the exact same thing wrong, as I had the exact same problems > there.
That sounds very odd. How did you get hold of autogen for cygwin? (Not that that will solve your problem, but it might help others chase it up). > The autobuilder stars happily compiling and working, but after a > while it seems to get stuck. The last thing on screen says (typing > this over, haven't used time to get filesharing working): > > sh -e ./tinfo/MKfallback.sh /home/jjvdgeer/env/share/terminfo > ../misc/terminfo.src vt102 vt220 xterm-vt220 >fallback.c > creating temporary terminfo directory... > > At this point nothing more seems to happen. I checked with 'top' > which suggest the CPU is using 100% of one of its cores on 'tic' > which seems to have something to do with terminfo, which seems to > correspond with the last command on screen. Even though I have no > idea what it really is. That sounds odd. One thing you can do to debug something like this is to use 'strace'. When doing something like 'strace ls' it tells you all the syscalls that the program makes (lots and lots of output to stderr). It's quite handy for finding that a program is stalling on a particular call, or similar. If you can hack around the Makefile to insert something like: strace -f somecommand someoptions 2> /tmp/strace.log around an existing command "somecommand someoptions" it might give you some more information to track it down further. tic is a bona fide program from ncurses - it comes with Ubuntu. You might want to try reinstalling package ncurses-bin just to see if something went wrong with your installation. (Do aptitude reinstall, don't try to remove it as half the packages on the system depend on ncurses!) You might also want to replace tic temporarily with something that tells you what arguments it's called with so you can run it by hand: $ sudo mv /usr/bin/tic /usr/bin/tic-tmp $ sudo cat > /usr/bin/tic #!/bin/sh echo $* > /tmp/tic.log /usr/bin/tic-tmp $* [Ctrl-D] $ sudo chmod +x /usr/bin/tic Don't forget to switch this back afterwards! Theo _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
