Sounds like a load path problem.
In particular, it looks like you've used /Programs/emacs
in some places and /Programs/emacs-20.7 in other places.
If you get them all to point to the right location, it
should work I would suspect
You reported that it is currently setup as:
(add-to-load-path "/Programs/emacs/site/elib-1.0")
(add-to-load-path "/Programs/emacs/site/eieio-0.16")
(add-to-load-path "/Programs/emacs-20.7/site/speedbar-0.13a")
(add-to-load-path "/Programs/emacs/site/semantic-1.4beta10")
(add-to-load-path "/Programs/emacs/site/jde/lisp")
maybe instead it should be:
(add-to-load-path "/Programs/emacs-20.7/site/elib-1.0")
(add-to-load-path "/Programs/emacs-20.7/site/eieio-0.16")
(add-to-load-path "/Programs/emacs-20.7/site/speedbar-0.13a")
(add-to-load-path "/Programs/emacs-20.7/site/semantic-1.4beta10")
(add-to-load-path "/Programs/emacs-20.7/site/jde/lisp")
I think the "make" issues are a red herring. You shouldn't have to
do any command-line make operations to get JDEE up and running.
Once you get your loadpath set up properly, you can use
M-x jde-compile-jde to compile the JDEE's .el files into .elc files.
This just gives you a little performance gain when jde first loads.
It is not required for proper operation.
Per the installation guide, you should just be able to unzip
everything, setup your .emacs file with a properly loadpath
and (require 'jde), and that's it.
And you are on the right track... start with the minimal .emacs
file from the JDEE site, and get that working. Then propagate
the changes into your own mega .emacs file once you know jde.el
is loading properly. Then finally, go back and byte-compile
the .el files into .elc.
Troy
-----Original Message-----
From: Joan M Friedman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 11:56 AM
To: [EMAIL PROTECTED]
Subject: Cannot open load file: jde
--- snip
