Re: sawfish 1.6.3 can't compile sawfish.wm.util.prompt

[Christopher Roy Bratusek <zanghar freenet de>]

Am Sun, 23 May 2010 09:41:59 -0500
schrieb Jeremy Hankins <nowan nowan org>:

> Harald van Dijk <harald gigawatt nl> writes:
> > [...]
> > (compiling sawfish/wm/util/ping.jl)
> > (compiling sawfish/wm/util/prompt.jl)
> > error--> (void-value prompt-completion-fun)
> > make[1]: *** [lisp] Error 10
> > make[1]: Leaving directory `/home/harald/sawfish/lisp'
> > make: *** [all] Error 1
> >
> > This file is unchanged from 1.6.2, but as of commit
> > 2277ff2ca26ea48fd6ce96f45faa4971a52bc81a
> > <http://git.gnome.org/browse/sawfish/commit/?id=2277ff2ca26ea48fd6ce96f45faa4971a52bc81a>
> > ,sawfish.wm.util.prompt is no longer implicitly included when compiling
> > itself. Note that you will not see this error if you are working from
> > a previous build directory where the .jlc files already exist. I
> > noticed the build completes without errors or warnings if I simply
> > remove the "Compilation hack" block; is it still necessary? If it is
> > necessary, another way to fix the problem is by having
> > sawfish.wm.util.prompt explicitly (open) itself.
> 
> I haven't been able to replicate this, and it doesn't make a whole lot
> of sense to me.  A file shouldn't have to be opened from itself in order
> to compile it, and I can't see where a (setq foo bar) would generate a
> void-value error on foo.
> 

you're right. hmm… 

--