On Fri, 26 Aug 2011, Hélio Guilherme wrote:
I solved the problem of gretl looking for the old library by
deleting .gretl directory.
Deleting your ~/.gretl directory will not do any harm, but neither
will it help if gretl's configuration is confused, since it contains
no configuration information.
The file to delete if you're worried about a possibly confused
configuration is ~/.gretl2rc (a plain text file, not a directory).
I've said this before, but if you're a long-term gretl CVS user it
is important that the command you use for doing your CVS updates is
cvs update -d -P
The "-d" says to add any new directories that have been created in
the repository. These are not added by default with a plain "cvs
update", but the gretl build will surely be broken if you do not add
new directories as they appear.
The "-P" says to prune (delete) files that are in your local copy
but have been removed from the repository. Again, this does not
happen by default, but the presence of stale files in your CVS tree
may well break the gretl build.
In addition, it's important to pay attention to any messages you get
from cvs when updating. From time to time cvs may report an
inconsistency between what's in your local copy and what's on the
server. For example, if you have modified a file relative to what is
on the server but have not committed your modification. Such
inconsistencies are, once again, likely to break the build.
If inconsistencies accumulate, the best approach is to delete your
whole CVS tree and start again.
Allin Cottrell