@juanito: I did use the compiletc meta package, still it shows the error. l've looked at the configure script output, and there's 2 things:
- uname -p returns 'unknown', don't know what it should return, maybe it doesn't recognize the VIA CPU.
- At the point where the ./configure script fails, it tries to compile libfind1.c , and when I manually do that, it cannot find include files like stdio.h, which are obviously present ("find" finds them).
Looks like I at last have to study how ./configure works :-(
@tinypoodle: I applied the fix to which the link pointed in /opt/bootlocal.sh . Don't know if it made a difference, but I have discovered at least why some of the searches don't return results. In the search.sh and provides.sh scrips I saw wget. Sure enough, the lights on my router blinked when I did a search, e.g. for "nasm". But, if I then selected 'provides' and hit enter, nothing happened. If the word to search for doesn't change, it lookes like the script simply isn't called. If I place a space behind "nasm" it works again and finds the proper files. Is this intended behaviour? Sounds unlogical to me.
Do you know where the address in the upper window line is cofigured? Normally ibiblio, but on one of the systems it is something local, and I cannot change if from within the program.
And indeed, I don't have 12M RAM, that was 128M, a typo. Meantime it's 256M even.
Thanks for all the assistance for far, and it is really refreshing to see small programs again, like "editor" in < 11k. Although I would accept an extra few hundred bytes for line numbers being visible. :-)
Mat