Sorry: my error for point C, though there may a lesson in it. Also
my apologies for my loose language in referring to applications as
.exe files - too much switching between Windows, OS-X and Linux.
The source of the problem was that the GTK2 development libraries
were not fully installed. So, the configuration program decided that
gretl should be compiled without GTK2. That works, but only to
generate a command line version of the program - hence gretlcli but
not gretl_x11. This is flagged in the configuration summary, but I
had not understood the significance. The full configuration log
reports the absence of GTK2 libraries, which pointed me to the
mistake. Everything was ok once I re-installed all of the GTK2
development libraries.
A suggestion: would it be possible (desirable) for the configuration
program to end with a warning that only the command line version will
be generated if the "Build with GTK version" flag is "No" - in the
same way that it gives an error message if, say, FFTW3 is missing?
I will test the rpm with the --nodeps option to see what
happens. One of my pet grouses is that every Linux distribution sets
up a different default path. It shouldn't miss lapack when
installing as root, but I have had previous errors generated by the
omission of some usual directories from the default path.
A follow-up question: in scrutinising the configuration log I noted
that MPFR support was absent, so I installed the relevant development
libraries to correct this. I understand that this is ancillary to
GMP but how much difference does it make to the performance of gretl?
Gordon