Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Eric M. Ludlam <eric@si...> - 2009-04-03 02:51:53
>>> don.rodgers@... requires approval seems to think that:
>On Windows XP SP3 with current version of cygwin and full emacs 22.3 Window=
>s binaries installed, just installed cedet-1.0pre6. Executed make (cygwin=
>) in windows cmd shell as follows:
>Build was successful but with a sizeable number of warnings. See attached =
The build does have many warnings in it. Using the ebuild option
can cut down on the warnings due to unloaded dependencies.
>Failed. See attached makeutest.out.
>When executing (load-file "c:/progra~1/cedet-1.0pre6/common/cedet.el") from=
> first line of .emacs, get error:
>Symbol's value as variable is void: le
>Debugger entered--Lisp error: (void-variable le)
> (let ((default-directory ...)) (add-to-list (quote load-path) default-dir=
Curious. I ran into something very similar recently. The stack was
very similar ending in a require(inversion), or a require of something
else, and it failed with some goofy variable that didn't exist in my
I tracked it down to something in my .emacs file I had installed many
years ago related to font lock. I think it was ctypes.el. It had
been quietly loading in my .emacs for years even though the feature it
used was obsolete. Then out of the blue I got this error.
I'll guess you may have something similar. Try moving CEDET init up
in your .emacs file.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net