October 2005 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [A21.5R21.4] [C] xemacs-21.5-clean: finder-find-library to return filename actually searched for 20 years

Adrian Aichner

I have fixed the accidental unix2dos conversion of my original commit. Unfortunately I don't know the exact cause of it yet. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

XEmacs Packages have been pre-released (2005-10-09-13) 20 years

Norbert Koch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there everyone. I have just added the following packages to the 'Pre-Releases' directory: New Packages in Pre-Release: =========================== tramp-1.27-pkg.tar.gz upstream version: 2.0.51 Previously Announced Packages Still in Pre-Release: ================================================== bbdb-1.28-pkg.tar.gz upstream version: 2.34 c-support-1.22-pkg.tar.gz upstream version: none ecrypto-0.20-pkg.tar.gz upstream version: 2.0 ediff-1.56-pkg.tar.gz upstream version: 2.75 edit-utils-2.25-pkg.tar.gz upstream version: none mail-lib-1.74-pkg.tar.gz upstream version: none net-utils-1.47-pkg.tar.gz upstream version: N/A pgg-1.06-pkg.tar.gz upstream version: 0.1 re-builder-1.05-pkg.tar.gz upstream version: 1.20 riece-1.20-pkg.tar.gz upstream version: 2.0.0 sasl-1.16-pkg.tar.gz upstream version: 1.14.4 sieve-1.18-pkg.tar.gz upstream version: none sml-mode-0.12-pkg.tar.gz upstream version: 3.9.5 speedbar-1.28-pkg.tar.gz upstream version: 0.14beta4 texinfo-1.30-pkg.tar.gz upstream version: none text-modes-1.89-pkg.tar.gz upstream version: none viper-1.44-pkg.tar.gz upstream version: 3.09 xemacs-base-1.98-pkg.tar.gz upstream version: none xemacs-devel-1.71-pkg.tar.gz upstream version: none xslt-process-1.12-pkg.tar.gz upstream version: 1.2.1 Detailed Changes: ================ - ------- ChangeLog Entries from xemacs-packages/tramp/ChangeLog ------- 2005-10-09 Norbert Koch <viteno(a)xemacs.org> * Makefile (VERSION): XEmacs package 1.27 released. 2005-10-08 Michael Albinus <michael.albinus(a)gmx.de> * Makefile (AUTHOR_VERSION): Bump to 2.0.51. Installing These: ================ Manually: - -------- 1) Download the packages that you want to install from: /ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/ 2) Unpack them to: [1] /usr/local/lib/xemacs/xemacs-packages/ 3) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.[245].x): - ---------------------------------------------- 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) Select the packages you wish to install (there are brief instructions at the bottom of the packages buffer). 4) Packages -> Install/Remove Selected 5) Re-start XEmacs. Using XEmacs Package Tools (XEmacs 21.1.14): - ------------------------------------------- 1) Options -> Manage Packages -> Add Download Site -> Pre-Releases 2) Options -> Manage Packages -> List and Install 3 - 5) As per XEmacs 21.[245].x. norbert - XEmacs Package Release Manager. Footnotes: [1] Note: Mule packages should be installed into: /usr/local/lib/xemacs/mule-packages/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (FreeBSD) iD8DBQFDSQbggu3ywdHdhM0RAnvZAKCm0NKFiNuL7O0OkMqgNTsr1xbQKgCbB5bp hPXQSbCXR1LBHTeJBpoTaYg= =xfPE -----END PGP SIGNATURE-----

1 participants
0 comments

Re: [Failed] XEmacs 21.5-b22 "cucumber" (+CVS-20051006) i586-pc-win32 20 years

Stephen J. Turnbull

>>>>> "Guido" == Guido Van Hoecke <Guido(a)vanhoecke.org> writes: Guido> d:\src\XEmacs\xemacs-21-5-22-cucumber\src\config.h(835) : Guido> fatal error C1083: Cannot open include file: 'malloc.h': No Guido> such file or directory First guess is that something is unusual about your system. malloc.h is required by several standards, I don't see how you can build any sizable program if it's not found. You have a current CVS checkout, so I'd have to guess the change is due to some of the fiddling that Ben did clarify the Makefile for native Windows builds. But I can't guess how that could hurt; malloc.h should be on your standard include path that the compiler provides. There don't seem to be any options in the command line the would remove the standard include paths. It would help us if you could find malloc.h on your system and tell us where it is so we can make sure that the build is set up to find it. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

4 participants
7 comments

Re: [PATCH] Aliasing --enable to --with. 20 years

Ben Wing

Malcolm Purvis wrote: >This patch makes the following changes to configure.ac: > >1. Aliases all --enable- options to --with (see the macro > XE_ARG_ENABLE_OR_WITH below). >2. Requires that only autoconf 2.59 be used to generate the configure script >3. Replaces numerous blank lines with the proper m4 'blank line' macro. This > prevents stray blan lines appearing at the wrong places in the configure > script. > >The aliasing means that any option that was previously available only as >--enable now can be set with --with as well (and --without instead of >--disable). In addition the option appears in the help output in both forms. > >Existing --with options are not aliased to --enable. > > Thank you thank you thank you !!! much appreciated. ben

1 participants
0 comments

[Success] XEmacs 21.5-b22 "cucumber" (+CVS-20051007) i586-pc-win32 20 years

Adrian Aichner

> XEmacs Build Report generated by emacs-version > 21.5 (beta22) "cucumber" (+CVS-20050925) XEmacs Lucid > with system-configuration > i586-pc-win32 > follows: > Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\Installation: > (Output from most recent run of ./configure) OS version: Microsoft Windows XP [Version 5.1.2600] OS: Windows_NT XEmacs 21.5-b22 "cucumber" (+CVS-20051007) configured for `i586-pc-win32'. Building XEmacs using "NMAKE". Building XEmacs using make flags " ". Building XEmacs in source tree "c:\\Hacking\\cvs.xemacs.org\\XEmacs\\xemacs-21.5-clean". For src, using compiler "cl -nologo -W3 -DSTRICT -Zi -O2 -G5 -Ob2 -MDd -c -TP -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\inc -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -I"c:\Hacking\libs4xemacs\xpm-3.4k" -I"c:\Hacking\libs4xemacs\xpm-3.4k\lib" -I"c:\Hacking\libs4xemacs\libpng-1.0.2" -I"c:\Hacking\libs4xemacs\zlib" -I"c:\Hacking\libs4xemacs\tiff-v3.4\libtiff" -I"c:\Hacking\libs4xemacs\jpeg-6b" -I"c:\Hacking\libs4xemacs\compface" -I"c:\Hacking\libs4xemacs\zlib" -DHAVE_MS_WINDOWS -DHAVE_MENUBARS -DHAVE_SCROLLBARS -DHAVE_TOOLBARS -DHAVE_WIDGETS -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE_GIF -DHAVE_PNG -DHAVE_TIFF -DHAVE_JPEG -DHAVE_XFACE -DHAVE_ZLIB -DHAVE_NATIVE_SOUND -DMULE -DERROR_CHECK_ALL -DPDUMP -DUSE_KKCC -DMC_ALLOC -DSYSTEM_MALLOC -DDEBUG_XEMACS -D_DEBUG -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs -DHAVE_CONFIG_H -DPATH_VERSION=\"21.5-b22\" -DPATH_PROGNAME=\"xemacs\" -DEMACS_VERSION=\"21.5-b22\" -DEMACS_PROGNAME=\"xemacs\" -DST! ACK_TRACE_EYE_CATCHER=xemacs_21_5_b22_i586_pc_win32 -DPATH_PREFIX=\"..\" -DEMACS_MAJOR_VERSION=21 -DEMACS_MINOR_VERSION=5 -DEMACS_BETA_VERSION=22 -DXEMACS_CODENAME=\""cucumber"\" -DXEMACS_EXTRA_NAME=\"(+CVS-20051007)\" -DEMACS_CONFIGURATION=\"i586-pc-win32\" -DPATH_PACKAGEPATH=\""~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages"\"". For lib-src, using compiler "cl -nologo -W3 -DSTRICT -Zi -O2 -G5 -Ob2 -MDd -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lib-src -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -DHAVE_CONFIG_H -DWIN32_NATIVE". Compiling as C++. Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b22". Package path is "~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages". Compiling in support for Microsoft Windows native GUI. Compiling in international (MULE) support. Compiling in support for XPM images. Compiling in support for GIF images. Compiling in support for PNG images. Compiling in support for TIFF images. Compiling in support for JPEG images. Compiling in support for X-Face message headers. Compiling in support for GZIP compression/decompression. Compiling in support for toolbars. Compiling in support for dialogs. Compiling in support for widgets. Compiling in support for native sounds. Using portable dumper. Using system malloc. Using DLL version of C runtime library. Compiling in extra internal error-checking. NOTE: --------------------------------------------------------- NOTE: Compiling in support for runtime error-checking. NOTE: XEmacs will run noticeably more slowly as a result. NOTE: Error-checking is on by default for XEmacs beta releases. NOTE: --------------------------------------------------------- Compiling in debugging support (no slowdown). Compiling with optimization. Using new experimental GC algorithms. Using new experimental allocator. > Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\xemacs-21.5-clean-cvs-update.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* " > and then deleting lines matching > "confl.*with.*auto-inlining\|^Formatting:" cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\ Compilation started at Sat Oct 08 11:01:01 2005 +0200 (W. Europe Daylight Time) ? gunzip-error.txt ? man/lispref/errors.texi.new ? nt/xemacs-21.5-clean-make-all-texinfo-error.err P CHANGES-beta P ChangeLog P Makefile.in.in P configure P configure.ac P version.sh P lisp/ChangeLog P lisp/build-report.el M lisp/cmdloop.el P lisp/dumped-lisp.el P lisp/simple.el P lisp/mule/canna-leim.el P lisp/mule/mule-cmds.el P man/ChangeLog P man/emodules.texi P modules/ChangeLog U modules/canna/Makefile.in.in U modules/canna/canna-api.c U modules/canna/configure.ac U modules/canna/install-sh rcsmerge: warning: conflicts during merge C src/ChangeLog P src/Makefile.in.in P src/alloc.c P src/depend P src/emacs.c M src/frame-msw.c P src/symsinit.h cvs server: Updating tests cvs server: Updating tests/DLL M tests/automated/region-tests.el U CHANGES-beta U ChangeLog U Makefile.in.in U configure U configure.ac U lisp/ChangeLog U lisp/build-report.el U lisp/dumped-lisp.el U lisp/simple.el U lisp/mule/canna-leim.el U lisp/mule/mule-cmds.el U modules/ChangeLog U src/depend U src/emacs.c U src/symsinit.h Compilation finished at Sat Oct 08 11:02:54 > Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-all.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* " > and then deleting lines matching > "confl.*with.*auto-inlining\|^Formatting:" cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\ nmake /f xemacs.mak all Compilation started at Sat Oct 08 11:03:38 2005 +0200 (W. Europe Daylight Time) Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b22". Compiling in extra internal error-checking. NOTE: Compiling in support for runtime error-checking. 1 file(s) copied. 1 File(s) copied 1 File(s) copied Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\) Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules) While compiling describe-register-1 in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\register.el: ** reference to free variable yank-excluded-properties While compiling the end of the data: ** the function remove-list-of-text-properties is not known to be defined. While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\diagnose.el: ** the function sort-numeric-fields is not known to be defined. While compiling get-selection in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\select.el: ** variable err bound but not referenced While compiling forward-paragraph in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\paragraphs.el: ** variable multiple-lines bound but not referenced While compiling the end of the data: ** the function constrain-to-field is not known to be defined. Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\) Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules) While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-init.el: ** the function x-keysym-hash-table is not known to be defined. While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\gtk.el: ** the function gtk-import-function is not known to be defined. While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\gtk-iso8859-1.el: ** assignment to free variable character-set-property While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\thai-util.el: ** define-category called with 3 arguments, but accepts only 2 ** define-category called with 3 arguments, but accepts only 2 ** define-category called with 3 arguments, but accepts only 2 While compiling the end of the data: ** the function make-category-table is not known to be defined. While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\lao-util.el: ** define-category called with 3 arguments, but accepts only 2 ** define-category called with 3 arguments, but accepts only 2 ** define-category called with 3 arguments, but accepts only 2 ** define-category called with 3 arguments, but accepts only 2 While compiling the end of the data: ** the function make-category-table is not known to be defined. While compiling ethio-modify-vowel in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\ethio-util.el: ** decompose-composite-char is an obsolete function; use char-to-string instead. Reading included file: c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\man\lispref\errors.texi Compilation finished at Sat Oct 08 11:09:24 > Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check-temacs.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* " > and then deleting lines matching > "confl.*with.*auto-inlining\|^Formatting:" cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\ nmake /f xemacs.mak check-temacs Compilation started at Sat Oct 08 11:10:38 2005 +0200 (W. Europe Daylight Time) Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\) Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules) base64-tests.el: 1234 of 1234 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures byte-compiler-tests.el: 66 of 66 tests successful (100%). 38 tests skipped because can't defadvice. 0 errors that should have been generated, but weren't 0 wrong-error failures c-tests.el: 4 of 4 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures case-tests.el: 1148 of 1148 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures ccl-tests.el: 4570 of 4570 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures database-tests.el: No tests run. 0 errors that should have been generated, but weren't 0 wrong-error failures extent-tests.el: 194 of 194 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures hash-table-tests.el: 9866 of 9866 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures lisp-tests.el: 3672 of 3672 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures md5-tests.el: 56 of 56 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures mule-tests.el: 232 of 236 tests successful ( 98%). 0 errors that should have been generated, but weren't 0 wrong-error failures Unexpected error (void-function executable-find) while executing interpreted code. Unexpected error (void-function executable-find) while executing byte-compiled code. os-tests.el: No tests run. Unexpected error (void-function executable-find) while executing interpreted code Unexpected error (void-function executable-find) while executing byte-compiled code 0 errors that should have been generated, but weren't 0 wrong-error failures regexp-tests.el: 350 of 350 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures region-tests-1-1.el: 28 of 28 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures region-tests.el: 38 of 38 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures symbol-tests.el: 246 of 246 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures syntax-tests.el: 56 of 56 tests successful (100%). 2 tests skipped because c-mode unavailable. 0 errors that should have been generated, but weren't 0 wrong-error failures tag-tests.el: 6 of 6 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures weak-tests.el: 140 of 140 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures base64-tests.el: 1234 of 1234 tests successful (100%). byte-compiler-tests.el: 66 of 66 tests successful (100%). c-tests.el: 4 of 4 tests successful (100%). case-tests.el: 1148 of 1148 tests successful (100%). ccl-tests.el: 4570 of 4570 tests successful (100%). database-tests.el: No tests run. extent-tests.el: 194 of 194 tests successful (100%). hash-table-tests.el: 9866 of 9866 tests successful (100%). lisp-tests.el: 3672 of 3672 tests successful (100%). md5-tests.el: 56 of 56 tests successful (100%). mule-tests.el: 232 of 236 tests successful ( 98%). os-tests.el: No tests run. regexp-tests.el: 350 of 350 tests successful (100%). region-tests-1-1.el: 28 of 28 tests successful (100%). region-tests.el: 38 of 38 tests successful (100%). symbol-tests.el: 246 of 246 tests successful (100%). syntax-tests.el: 56 of 56 tests successful (100%). tag-tests.el: 6 of 6 tests successful (100%). weak-tests.el: 140 of 140 tests successful (100%). Compilation finished at Sat Oct 08 11:11:23 > Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* " > and then deleting lines matching > "confl.*with.*auto-inlining\|^Formatting:" cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\ nmake /f xemacs.mak check Compilation started at Sat Oct 08 11:14:00 2005 +0200 (W. Europe Daylight Time) base64-tests.el: 1234 of 1234 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures byte-compiler-tests.el: 104 of 104 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures c-tests.el: 4 of 4 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures case-tests.el: 1148 of 1148 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures ccl-tests.el: 4570 of 4570 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures database-tests.el: No tests run. 0 errors that should have been generated, but weren't 0 wrong-error failures extent-tests.el: 194 of 194 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures hash-table-tests.el: 9866 of 9866 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures lisp-tests.el: 3672 of 3672 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures md5-tests.el: 56 of 56 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures mule-tests.el: 232 of 236 tests successful ( 98%). 0 errors that should have been generated, but weren't 0 wrong-error failures os-tests.el: 20 of 20 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures regexp-tests.el: 350 of 350 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures region-tests-1-1.el: 28 of 28 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures region-tests.el: 38 of 38 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures symbol-tests.el: 246 of 246 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures syntax-tests.el: 60 of 60 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures tag-tests.el: 6 of 6 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures weak-tests.el: 140 of 140 tests successful (100%). 0 errors that should have been generated, but weren't 0 wrong-error failures base64-tests.el: 1234 of 1234 tests successful (100%). byte-compiler-tests.el: 104 of 104 tests successful (100%). c-tests.el: 4 of 4 tests successful (100%). case-tests.el: 1148 of 1148 tests successful (100%). ccl-tests.el: 4570 of 4570 tests successful (100%). database-tests.el: No tests run. extent-tests.el: 194 of 194 tests successful (100%). hash-table-tests.el: 9866 of 9866 tests successful (100%). lisp-tests.el: 3672 of 3672 tests successful (100%). md5-tests.el: 56 of 56 tests successful (100%). mule-tests.el: 232 of 236 tests successful ( 98%). os-tests.el: 20 of 20 tests successful (100%). regexp-tests.el: 350 of 350 tests successful (100%). region-tests-1-1.el: 28 of 28 tests successful (100%). region-tests.el: 38 of 38 tests successful (100%). symbol-tests.el: 246 of 246 tests successful (100%). syntax-tests.el: 60 of 60 tests successful (100%). tag-tests.el: 6 of 6 tests successful (100%). weak-tests.el: 140 of 140 tests successful (100%). Compilation finished at Sat Oct 08 11:14:53 -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

canna build failure caused by module name 20 years

Marcus Crestani

Stephen, building the canna module of current CVS results in ../../lib-src/ellcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g --mode=compile --mod-output=canna-api_i.o -I../../src -I/home/crestani/src/xemacs/xemacs-21.5/modules/canna/../../src -c canna-api_i.c canna-api_i.c:10: error: syntax error before '-' token canna-api_i.c:20: error: syntax error before '-' token and many other connected errors. Your recent renaming of the canna module causes the error: one use of MODNAME (defined in Makefile.in.in) is to generate C function identifiers, therefore it must itself be a valid C identifier. My patch renames it from canna-api to canna_api, this fixes the build. Index: modules/canna/Makefile.in.in =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/modules/canna/Makefile.in.in,v retrieving revision 1.2 diff -u -r1.2 Makefile.in.in --- modules/canna/Makefile.in.in 4 Oct 2005 17:51:32 -0000 1.2 +++ modules/canna/Makefile.in.in 7 Oct 2005 12:35:58 -0000 ＠＠ -26,7 +26,7 ＠＠ ## source tree. ### Specialize this part for your module -MODNAME=canna-api +MODNAME=canna_api MODVER=0.5.0 MODTITLE="Module wrapping Canna libraries for XEmacs" CFLAGS=＠CFLAGS＠ The change in the module name has also to be reflected in canna-leim.el. I also think that the path "canna/" has to be removed from the require statement: Index: lisp/mule/canna-leim.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/mule/canna-leim.el,v retrieving revision 1.8 diff -u -r1.8 canna-leim.el --- lisp/mule/canna-leim.el 4 Oct 2005 17:51:29 -0000 1.8 +++ lisp/mule/canna-leim.el 7 Oct 2005 14:38:06 -0000 ＠＠ -45,7 +45,7 ＠＠ (defun canna-activate (&optional name) ;; XEmacs 21.5.10 and later have 3-argument require. - (unless (require 'CANNA "canna/canna-api" 'no-error) + (unless (require 'CANNA "canna_api" 'no-error) (error 'file-error "No Canna API support!? See M-x describe-installation & C-h v module-load-path.")) (unless (require 'canna nil 'no-error) Because canna_api.ell gets copied (with `make install') to /usr/local/lib/xemacs-21.5-b22/i686-pc-linux/modules/canna_api.ell, with no additional subdirectory. Is this only a problem on my local installation? My module-load-path contains: ("/usr/local/lib/xemacs/site-modules/" "/usr/local/lib/xemacs-21.5-b22/i686-pc-linux/modules/"). The above patches fix canna for me, but there are several ways to approach the problems, and I really don't know what would be the best way. Thus, I didn't send this to -patches. So, please consider this mail more as a bugreport than as a fix. Let me know, if you want me to send my changes to -patches, though, I'd be happy to do this then. -- Marcus

2 participants
1 comments

unicode internal 20 years

Ben Wing

sorry if i've missed some of the discussions on switching to unicode internally. i've been thinking of what needs to be done to implement this. besides simply changing the internal representation, we need: -- [1] at some point, use extent properties to track the language of a text. this is well-recognized. -- [2] charsets should be generalized so that they encompass an arbitrary set of unicode chars. -- [3] we should add unicode-compatible charsets. the names should be such that they programmatically map onto perl-compatible (used with regexp \p, see below) charset names. -- [4] the perl regexp \p syntax should be adopted for referencing charsets. (char categories just suck.) for that matter, we should move in the direction of being as perl-compatible as possible with our regexps, since that is where the world is going. (cf java, python, ruby, c#, ...) the big problem here is \( and (, which are backwards. the only reasonable solutions i can see are [a] a global variable to control which kinds of regexps are used; [b] a double set of all functions that take regexps. comments? -- [5] char tables need to be changed. their current implementation is heavily tied to the current mule character structure. we will also need to change `map-char-table'. unfortunately, this will be incompatible with its current workings. fortunately, only three packages use map-char-table, and from looking at these three, it's not clear anything will break. also, the new map-char-table will work like GNU Emacs. -- [6] at some point, font objects should be changed to include a char table so that different charsets can have different fonts. it is easy to maintain backward compatibility here -- the "old" way of doing things just maps all chars to the same font. and let's please use font vectors, not XLFD-style crap. as for [5], map-char-table needs to return either a single char or a range; *not* any of the other crap it currently returns. also, in [5] we have an implementation choice. either we use sorted ranges or we use page-table-style lookups, indexed successively on each byte of the char value. both are already implemented in XEmacs ("range tables" and "unicode translation tables"). this is a standard speed-vs-space issue. the former are O(log n) but compact; the latter are O(constant) but potentially large. (although it depends on how full the tables are. a sparse table referencing a few chars all over the unicode space could get very large with the page-table style; but a dense table with high locality might actually be smaller.) should we allow the user to control this, with range tables the default?

6 participants
14 comments

Re: bug report: UTF-8 encoding support 20 years

Stephen J. Turnbull

>>>>> "Eduards" == Eduards Mihelovics <emikhelo(a)gmail.com> writes: Eduards> It evaluates to: Eduards> (utf-8 iso-8-1 utf-16-little-endian-bom utf-16-bom Eduards> utf-8-bom iso-7 no-conversion iso-8-2 iso-8-designate Eduards> iso-lock-shift shift-jis big5 utf-16-little-endian utf-16 Eduards> ucs-4) OK, things are working right to that extent. And I _knew_ there was an interactive interface, I just forgot what it was! M-x prefer-coding-system should do what you need, sorry for taking so long to come to my senses. If it does work, then (prefer-coding-system 'utf-8) in your init file should make life good. Here's the docstring: Add CODING-SYSTEM at the front of the priority list for automatic detection. This also sets the coding system of newly created buffers (the default value of `buffer-file-coding-system') and the default coding system for output to a subprocess (the CDR of `default-process-coding-system'). If CODING-SYSTEM specifies a certain type of EOL conversion, the coding systems set by this function will use that type of EOL conversion. This does not change [various subtle things that shouldn't be changed, if you run into trouble with *file names* or *subprocesses* look at the full docstring or ask on xemacs-beta]. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

3 participants
4 comments

mode for wikipedia? 20 years

Uwe Brauer

Hello Does anybody know about a mode for wikipedia? I know about emacs-wiki which is however specifically for emacs wiki, and I know about wikipedia-mode.el (by Chong Yidong). However the latter just allow basic navigation, does not allow to insert links and formating stuff. Does anything more advanced exist? Thanks Uwe Brauer

1 participants
0 comments

Re: bug report: UTF-8 encoding support 20 years

Stephen J. Turnbull

>>>>> "Eduards" == Eduards Mihelovics <emikhelo(a)gmail.com> writes: Eduards> I don't know. Evaluating (set-coding-category-system Eduards> 'utf-8 utf-8) produces: Symbol's value as variable is Eduards> void: utf-8 *argh* again. I need to quit my day job, so I'll have time to think and say it right the first time. That should read (set-coding-category-system 'utf-8 'utf-8) (both utf-8's should be quoted). -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

2 participants
1 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta October 2005