6:05 a.m.
Andrew S Howell <andy(a)tibco.com> writes in xemacs-beta(a)xemacs.org:
>> /apps/src/Xemacs/xemacs-21.0.65/src/xemacs -batch -l
>> check-features.el Error: This XEmacs is built with tooltalk
>> support but does not have a tooltalk package installed.
>> Without the tooltalk lisp package, Tooltalk support is broken.
>> make: *** [check-features] Error 1
>> When I put the tooltalk package in place, XEmacs installed
>> fine...
SL> Sounds like it's working fine to me. Do you think the wording
SL> should be improved?
Steve,
No, my wording should be improved. :) What I meant to say was:
Should xemacs compile and install out of the box when tooltalk
is automatically added by configure, without going off and
fetching tooltalk?
That's probably a good idea. When that configure bomb was added,
automated package fetching wasn't implemented at all.
This is very minor point, not worth wasting too much time on...
I don't have access to a system with tooltalk. Out of curiosity, what
happens if you run a tooltalk-enabled XEmacs without the tooltalk Lisp?
If it runs without crashing, we can probably convert the error into
some kind of startup warning and optional package fetch at run-time.
6:57 a.m.
New subject: 21.0.65 build problem on Solaris 2.5.1, gcc 2.7.2.2
>>>> "SL" == SL Baur <steve(a)xemacs.org>
writes:
SL> I don't have access to a system with tooltalk.
I think you do. This configure output was generated on the machine on
your desk:
checking for tt_c.h... no
checking for Tt/tt_c.h... yes
checking for tt_message_create in -ltt... yes
Defining TOOLTALK
Defining TT_C_H_PATH = "Tt/tt_c.h"
Prepending "-ltt " to $libs_x
xemacs will be linked with "tooltalk.o"
checking for Dt/Dt.h... yes
checking for DtDndDragStart in -lDtSvc... yes
7:47 a.m.
New subject: 21.0.65 build problem on Solaris 2.5.1, gcc 2.7.2.2
>>>> "SL" == SL Baur <steve(a)xemacs.org>
writes:
SL> Andrew S Howell <andy(a)tibco.com> writes in
SL> Sounds like it's working fine to me. Do you think the wording
SL> should be improved?
> Steve,
> No, my wording should be improved. :) What I meant to say was:
> Should xemacs compile and install out of the box when tooltalk
> is automatically added by configure, without going off and
> fetching tooltalk?
SL> That's probably a good idea. When that configure bomb was
SL> added, automated package fetching wasn't implemented at all.
> This is very minor point, not worth wasting too much time on...
SL> I don't have access to a system with tooltalk. Out of
SL> curiosity, what happens if you run a tooltalk-enabled XEmacs
SL> without the tooltalk Lisp? If it runs without crashing, we
SL> can probably convert the error into some kind of startup
SL> warning and optional package fetch at run-time.
I just moved lisp/tooltalk to lisp/tooltalk.not and restarted. There
were not any errors. I didn't do anything but make sure XEmacs came up
and I could edit a file.
Regards,
Andy
8:17 a.m.
New subject: 21.0.65 build problem on Solaris 2.5.1, gcc 2.7.2.2
Hi, Andy!
>>>> "ash" == Andrew S Howell
<andy(a)tibco.com> writes:
ash> I just moved lisp/tooltalk to lisp/tooltalk.not and
ash> restarted. There were not any errors. I didn't do anything
ash> but make sure XEmacs came up and I could edit a file.
Anything in the standard paths is supposed to get found and autoloaded
at startup (there is no list of all packages in XEmacs, this is
determined dynamically). Test with
M-: (apply 'concat (mapcar (lambda (x) (if (string-match "tooltalk" x) x))
load-path))
(typed all in one line). I'm pretty sure you'll get the response
".../lisp/tooltalk.not".
You either need to move lisp/tooltalk to ../../ or so, or move all the
lisp files to .el.not and .elc.not.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
__________________________________________________________________________
__________________________________________________________________________
What are those two straight lines for? "Free software rules."
9:47 a.m.
New subject: 21.0.65 build problem on Solaris 2.5.1, gcc 2.7.2.2
>>>> "Stephen" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp> writes:
Stephen> Hi, Andy!
>>>> "ash" == Andrew S Howell
<andy(a)tibco.com> writes:
ash> I just moved lisp/tooltalk to lisp/tooltalk.not and
ash> restarted. There were not any errors. I didn't do anything
ash> but make sure XEmacs came up and I could edit a file.
Stephen> Anything in the standard paths is supposed to get found
Stephen> and autoloaded at startup (there is no list of all
Stephen> packages in XEmacs, this is determined dynamically).
Stephen> Test with
Stephen> M-: (apply 'concat (mapcar (lambda (x) (if (string-match
Stephen> "tooltalk" x) x)) load-path))
Steve,
I could not get the above to work, it complained about "wrong type
argument: stringp, nil"
Your are right though, I did describe-variable load-path, and sure enough, it
found tooltalk.not. The other thing I noticed was that my load-path
starts with nil.
(nil "/h/andy/lisp"
"/apps/xemacs/21.0.0.b65/sun4-55/lib/xemacs/mule-packages/lisp/"....
The culprit was in my .emacs:
(setq load-path
(append (list nil (expand-file-name "~/lisp"))
load-path))
Removing the "nil", and your code worked as advertised. Although it
was a bit more to type, your way was much sexier than
describe-variable :)
Regards,
Andy
9391
days inactive
9391
days old
4 comments
4 participants
participants (4)
-
Andrew S. Howell -
Martin Buchholz -
SL Baur -
Stephen J. Turnbull