12:06 a.m.
I have tried to build the ben-mule branch today and encountered a
problem in the build process. This is Debian Linux 3.0:
Suggestions?
Bootstrapping from temacs...*** Error in XEmacs initialization
(wrong-type-argument listp "tr")
*** Backtrace
really-early-error-handler((wrong-type-argument listp "tr"))
car("tr")
(setq loc (car --dolist-temp--38119))
(while --dolist-temp--38119 (setq loc (car --dolist-temp--38119)) (if (cond ... ...)
(return-from langenv lang)) (setq --dolist-temp--38119 (cdr --dolist-temp--38119)))
# bind (loc --dolist-temp--38119)
(let ((--dolist-temp--38119 locs) loc) (while --dolist-temp--38119 (setq loc ...) (if
... ...) (setq --dolist-temp--38119 ...)) nil)
# (catch --cl-block-nil-- ...)
(catch (quote --cl-block-nil--) (let (... loc) (while --dolist-temp--38119 ... ... ...)
nil))
(cl-block-wrapper (catch (quote --cl-block-nil--) (let ... ... nil)))
(block nil (let (... loc) (while --dolist-temp--38119 ... ... ...) nil))
(dolist (loc locs) (if (cond ... ...) (return-from langenv lang)))
# bind (case-fold-search locs lang)
(let* ((lang ...) (locs ...) (case-fold-search t)) (dolist (loc locs) (if ... ...)))
(while --dolist-temp--38111 (setq langcons (car --dolist-temp--38111)) (let* (... ...
...) (dolist ... ...)) (setq --dolist-temp--38111 (cdr --dolist-temp--38111)))
# bind (langcons --dolist-temp--38111)
(let ((--dolist-temp--38111 language-info-alist) langcons) (while --dolist-temp--38111
(setq langcons ...) (let* ... ...) (setq --dolist-temp--38111 ...)) nil)
# (catch --cl-block-nil-- ...)
(catch (quote --cl-block-nil--) (let (... langcons) (while --dolist-temp--38111 ... ...
...) nil))
(cl-block-wrapper (catch (quote --cl-block-nil--) (let ... ... nil)))
(block nil (let (... langcons) (while --dolist-temp--38111 ... ... ...) nil))
(dolist (langcons language-info-alist) (let* (... ... ...) (dolist ... ...)))
# (catch --cl-block-langenv-- ...)
(catch (quote --cl-block-langenv--) (dolist (langcons language-info-alist) (let* ...
...)))
(cl-block-wrapper (catch (quote --cl-block-langenv--) (dolist ... ...)))
(block langenv (dolist (langcons language-info-alist) (let* ... ...)))
# bind (locale)
get-language-environment-from-locale("C")
(and locstring (get-language-environment-from-locale locstring))
(setq langenv (and locstring (get-language-environment-from-locale locstring)))
# bind (locstring)
(let ((locstring ...)) (setq langenv (and locstring ...)))
(if (memq system-type (quote ...)) (let (... ...) (setq langenv ...) (puthash ... sysdef
mswindows-langenv-to-locale-table) (puthash langenv userdef
mswindows-langenv-to-locale-table) (and langenv ...) (mswindows-set-current-locale
userdef)) (let (...) (setq langenv ...)))
# bind (langenv)
(let (langenv) (if (memq system-type ...) (let ... ... ... ... ... ...) (let ... ...))
(unless langenv (setq langenv "English")) (setq current-language-environment
langenv) (let (...) (reset-language-environment) (set-language-environment-coding-systems
langenv default-eol-type)))
init-locale-at-early-startup()
*** Killing XEmacs
--
How old would you be if you didn't know how old you are?
-- Satchell Page
4:29 a.m.
>>>> "Daniel" == Daniel Pittman
<daniel(a)rimspace.net> writes:
Daniel> I have tried to build the ben-mule branch today and
Daniel> encountered a problem in the build process. This is Debian
Daniel> Linux 3.0:
CC reports of bugs in that branch to ben(a)xemacs.org. Ben typically
lags by a week or more in reading xemacs-beta.
Ben's the only one who has a good idea of what's going on in that
branch right now.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
5:28 a.m.
Stephen J. Turnbull writes:
>>>>> "Daniel" == Daniel Pittman
<daniel(a)rimspace.net> writes:
Daniel> I have tried to build the ben-mule branch today and
Daniel> encountered a problem in the build process. This is Debian
Daniel> Linux 3.0:
CC reports of bugs in that branch to ben(a)xemacs.org. Ben typically
lags by a week or more in reading xemacs-beta.
Ben's the only one who has a good idea of what's going on in that
branch right now.
is ben subscribed to the build reports list as well ??
i have been having trouble getting his branch to compile on FreeBSD
i sent a build report with "[Failure ben-mule]" in the subject
it seemed like the best subject to use
hey i just had a thought
would it be useful to have the branch added to the SUCCESS|FAILURE
header for the subject ? and maybe the major options like GTK and MULE ?
it would make sorting build reports a bit easier
what do people think about this ?
if anyone is interested i could have a go at a patch for build-report.el
--
XEmacs Advocate | Do not try the patience of Wizards,
FreeBSD Devote | for they are subtle and quick to anger.
Perl Hacker | - Elric (Technomage) , Babylon 5.
Apache God | <mailto:rendhalverï¼ xemacs.org>
5:49 a.m.
>>>> "rendhalver" == rendhalver <(Peter
Brown)" <rendhalver(a)xemacs.org>> writes:
rendhalver> is ben subscribed to the build reports list as well ??
No. Ben has a problem that is not RSI, but has similar effects on his
productivity. See his .sig for an URL describing the situation. I
monitor build-reports and if there's something that needs Ben's
immediate attention, I pass it on. I've told him that people have had
problems building on Unix recently, but the branch is in flux (he
plans to merge back to mainline early next week), so he just wants to
get that done early (spring break so he has time to respond to bug
reports).
rendhalver> i have been having trouble getting his branch to
rendhalver> compile on FreeBSD
I believe Ben basically tests on native Windows and Cygwin with all
the trimmings. So there are probably issues with "real" Unices that
he doesn't catch, but they should be straightforward to fix.
rendhalver> would it be useful to have the branch added to the
rendhalver> SUCCESS|FAILURE header for the subject ? and maybe the
rendhalver> major options like GTK and MULE ?
Not really, for my use. I have a (now bitrotted) script to collect
option statistics from the header and body. For the headers, success
or failure is critical, followed by version then platform. Sticky
tag, if any, would be nice. I guess you could grep ./CVS/Entries for
version.sh. That gives a sense of the state of the branch.
Options and other details are mostly useful if you're trying to find
something "close" to a problem build.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
6:19 a.m.
Stephen J. Turnbull writes:
>>>>> "rendhalver" == rendhalver <(Peter
Brown)" <rendhalver(a)xemacs.org>> writes:
rendhalver> is ben subscribed to the build reports list as well ??
No. Ben has a problem that is not RSI, but has similar effects on his
productivity. See his .sig for an URL describing the situation. I
ok will have a look at that
another talent of mine is healing people so i will email him and see
if some of my technique's will help him with that :)
monitor build-reports and if there's something that needs
Ben's
immediate attention, I pass it on. I've told him that people have had
problems building on Unix recently, but the branch is in flux (he
plans to merge back to mainline early next week), so he just wants to
get that done early (spring break so he has time to respond to bug
reports).
cool
rendhalver> i have been having trouble getting his branch to
rendhalver> compile on FreeBSD
I believe Ben basically tests on native Windows and Cygwin with all
the trimmings. So there are probably issues with "real" Unices that
he doesn't catch, but they should be straightforward to fix.
i tried a compile of 21.5 with mule here and it built without a hitch
didnt send a build report tho maybe i should
rendhalver> would it be useful to have the branch added to
the
rendhalver> SUCCESS|FAILURE header for the subject ? and maybe the
rendhalver> major options like GTK and MULE ?
Not really, for my use. I have a (now bitrotted) script to collect
option statistics from the header and body. For the headers, success
or failure is critical, followed by version then platform. Sticky
tag, if any, would be nice. I guess you could grep ./CVS/Entries for
version.sh. That gives a sense of the state of the branch.
Options and other details are mostly useful if you're trying to find
something "close" to a problem build.
ok cool
just another one of the radical/strange/interesting ideas that i get
a lot of them work, some of them are to radical/strange/interesting,
and others are just plain silly :)
but i think the world need more radical/strange/interesting ideas so i
will continue to have them, and some people will have use of them
--
XEmacs Advocate | Do not try the patience of Wizards,
FreeBSD Devote | for they are subtle and quick to anger.
Perl Hacker | - Elric (Technomage) , Babylon 5.
Apache God | <mailto:rendhalverï¼ xemacs.org>
8107
days inactive
8107
days old
4 comments
3 participants
participants (3)
-
Daniel Pittman -
Rendhalver [Peter Brown] -
Stephen J. Turnbull