Russ Whitaker wrote:

symptom: GPC would compile unit crtc.c but wouldn't link to ncurses

so used text editor to search the Makefile.in files for == and replace with = when it appeared in an "if" statement then did cnfigure, etc, etc

result: gpc now finds ncurses

(bash defaults to always false when it sees == )

Sorry, I don't think I can follow you...

First of all, I'm not so much of a bash expert. What do you mean by "bash defaults to always false when it sees =="? My man page says `==' may be used in place of `=' in comparisons, and I can't seem to find any difference in bash's behaviour. Does it mean that (some version of ?) bash does not recognize `==' as a comparison operator?

Secondly, I'm a bit surprised about the symptom. The only `==' I could find were one in Make-lang.in in the main GPC source directory, and two in Makefile.in in the rts subdirectory. All of them were of the form "if [ x$(WITH_SHARED) == xyes ] ; then ...", to test whether one wants to build a shared library of the RTS. I can't see any connection to not linking ncurses. -- Well, perhaps, due to the make failing here, it did not get to the point of installing the new units, so GPC used the units of an older version which did not refer to ncurses correctly -- that might be the case...

Anyway, replacing these three `==' by `=' (which I did now) fixes the whole problem, right? (Or just this symptom?)

Frank