July 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Lars Magne Ingebrigtsen

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta34) "Molpe" [Lucid] (powerpc-unknown-linux, Mule) of Mon Jul 10 2000 on blue configured using `configure --with-mule' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: Make a symlink with a non-ASCII character in it. Then say something like: (file-symlink-p "/music/new/Caliméro") where "/music/new/Caliméro" is the symlink you made. You will then get: Fatal error: assertion failed, file mule-charset.h, line 602, 0 <= fb && fb < 0xA0 Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/src/xemacs-21.2/src/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: file-symlink-p("/music/new/Caliméro") eval((file-symlink-p "/music/new/Caliméro")) # bind (expr) eval-interactive((file-symlink-p "/music/new/Caliméro")) # bind (standard-output opoint ignore-quotes eval-last-sexp-arg-internal) eval-last-sexp(nil) # bind (command-debug-status) call-interactively(eval-last-sexp) # (condition-case ... . error) # (catch top-level ...)

2 participants
1 comments

Package tm unconditionally uses message-included-forward-headers 23 years, 9 months

Adrian Aichner

I installed tm 1.22 Emacs MIME support. today. (load-library "mime-setup") causes following *Backtrace*. I use (gnus-version) "Gnus v5.8.7" which doesn't have this variable. I can send a patch testing for (boundp 'message-included-forward-headers) but maybe someone here knows more about this. Please advise, Adrian Signaling: (void-variable message-included-forward-headers) byte-code("..." [require tm-edit mime-make-tag "message" "rfc822" "\n" message-forward-start-separator "" message-forward-end-separator string-match message-included-forward-headers "Mime-Version:" "\\|^Mime-Version:" "Content-Type:" "\\|^Content-Type:" "Content-Transfer-Encoding:" "\\|^Content-Transfer-Encoding:"] 3) load-internal("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\message-mime.elc" nil t t binary) efs-real-load("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\message-mime.elc" nil t t) load("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\message-mime.elc" nil t nil) efs-real-require(message-mime "c:\\XEmacs\\xemacs-packages\\lisp\\tm\\message-mime.elc") require(message-mime) #<compiled-function nil "...(4)" [require message-mime] 2>() call-after-loaded(message #<compiled-function nil "...(4)" [require message-mime] 2>) byte-code("..." [boundp epoch::version add-hook message-setup-hook mime/editor-mode message-maybe-setup-default-charset message-send-hook mime-editor/maybe-translate message-header-hook mime/encode-message-header call-after-loaded message #<compiled-function nil "...(4)" [require message-mime] 2> provide mime-setup run-hooks mime-setup-load-hook] 3) load-internal("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t binary) efs-real-load("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t) load("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t) apply(load ("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t)) dired-handler-fn(load "c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t) efs-real-load("c:\\XEmacs\\xemacs-packages\\lisp\\tm\\mime-setup.elc" nil t t) load("mime-setup") #<compiled-function (library) "...(4)" [load library] 2 288519 (list (read-library "Load Library: " load-path nil nil nil ...))>("mime-setup") call-interactively(load-library) command-execute(load-library t) execute-extended-command(nil) call-interactively(execute-extended-command) -- Adrian Aichner <adrian(a)xemacs.org>

3 participants
2 comments

Re: No GNU malloc in glibc 2.2 ??? 23 years, 9 months

SL Baur

Martin Buchholz <martin(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >>>>>> "sb" == SL Baur <steve(a)turbolinux.co.jp> writes: sb> What's up with the attached malloc report? Why doesn't the GNU libc sb> malloc work in Alpha Linux? > Perhaps because of this in m/alpha.h: > #ifdef LINUX > # define SYSTEM_MALLOC > #endif > which is derived perhaps from this: > 1998-02-18 SL Baur <steve(a)altair.xemacs.org> > * m/alpha.h: > * unexelf.c: Synched with Emacs 20.2. > From Aki Vehtari <Aki.Vehtari(a)hut.fi> > s&m is evil. Ugh. However, on Linux SYSTEM_MALLOC _is_ GNU malloc so there's more to it than just s&m.

2 participants
1 comments

Re: [PATCH] Enhanced clipboard support. 23 years, 9 months

Adrian Aichner

>>>>> "AH" == Alastair J Houghton <ajhoughton(a)lineone.net> writes: AH> Here's a patch that modifies the clipboard support in AH> XEmacs. It provides for an mswindows-style multi-format AH> selections (e.g. you could keep an integer and its string AH> representation in a selection and pull out whichever was AH> most appropriate). It also adds the ability to register AH> new data types with the host window system (only implemented AH> for mswindows at the moment), as well as the ability to AH> look up the names of external formats and the ability AH> to get a conservative list of available selection formats AH> for a given selection. Oh, and the append code has been AH> changed from the *horrible* kludge that was used before. This sounds exciting! So I tried applying your patch. Please produce unified diffs if your diff programs supports this format (usually via the -u switch). This makes patches smaller and much easier to read. Here is what I get when applying your patch against latest CVS sources: cd d:\tmp\21.2\xemacs\ patch --strip=2 < d:\tmp\selection.diff Compilation started at Mon Jul 10 01:33:22 2000 +0200 (W. Europe Daylight Time) patching file `src/console.h' Hunk #1 FAILED at 91. 1 out of 1 hunk FAILED -- saving rejects to src/console.h.rej patching file `src/select-msw.c' patching file `src/select-x.c' patching file `src/select.c' patching file `src/select.h' patching file `lisp/select.el' Compilation exited abnormally with code 1 at Mon Jul 10 01:33:27 So, there's a conflict with src/console.h. Fortunately this was a simple matter. I patched manually. The src/console.h you based your changes on is from before 2000-07-05 Kirill 'Big K' Katsnelson <kkm(a)dtmx.com> * console-msw.h (struct mswindows_device): Removed unnecessary cached device geometry values. Added update_tick and an accessor macro. (Lisp_Devmode): Added lrecord declaration. (struct msprinter_device): Contain devmode as a Lisp object. Added mswindows_get_selected_frame_hwnd(); * console.h (struct console_methods): Indentation nitpicking. Correct? I'm building right now. AH> Additionally, the mswindows code for selection handling has AH> been rewritten - it is now much cleaner, and uses the new AH> functionality. AH> I've tested it quite a bit on mswindows, but there might AH> be some obscure problem that I haven't noticed yet (or AH> even something obvious I've missed). However, as I'm now AH> using a version containing this patch, I'm bound to AH> notice anything wrong with it sooner or later... I'm testing a native NT build. XEmacs from latest CVS sources does not build after applying your patch! Can you please refresh your source-base and see what's wrong? Here's what I get: link.exe ＠C:\TEMP\nmb00348. specifier.obj : error LNK2005: _Qappend already defined in select.obj ..\src\temacs.exe : fatal error LNK1169: one or more multiply defined symbols found NMAKE : fatal error U1077: 'link.exe' : return code '0x491' Stop. Is there a patch to specifier.c which you forgot to include? Best regards, Adrian -- Adrian Aichner <adrian(a)xemacs.org>

1 participants
0 comments

Re: fix completer.el for ms windows 23 years, 9 months

Adrian Aichner

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Ben Wing <ben(a)666.com> writes: >> +(defvar completer-path-separator-string >> + (if (eq system-type 'windows-nt) "\\" "/")) >> + >> +(defvar completer-path-separator-regexp >> + (if (eq system-type 'windows-nt) "[/\\]" "/")) >> + >> +(defvar completer-path-delimiter-list >> + (if (eq system-type 'windows-nt) '(?\\ ?/) '(?/))) >> + >> +(defvar completer-path-separator-regexp-inside-brackets >> + (if (eq system-type 'windows-nt) "/\\" "/")) >> + >> +(defvar completer-dot-dot-list >> + (if (eq system-type 'windows-nt) '("../" "..\\") '("../"))) >> + Jan> Shouldn't those be dependent on the vale of Jan> directory-sep-char instead of system type? Oops, I miss that. I agree with you since XEmacs native NT supports directory-sep-char and works with both kinds of leaning toothpicks[1]. Jan> Jan Footnotes: [1] See perldoc perlop to learn about LTS[2]. [2] APA LeaningToothpickSyndorome. -- Adrian Aichner <adrian(a)xemacs.org>

1 participants
0 comments

about that overfontifying in compile output buffers 23 years, 9 months

Ben Wing

was it charles waldman who complained about this? i see what's going on, in that it's trying to highlight lines showing program execution but not highlight error messages, entering/leaving messages, and the like. the latter two messages have colons in them, and program execution lines have -'s in them because of options beginning with -. So you could at least eliminate some problems by looking only for places with a - beginning a word [i.e. preceded by spaces]. -- Ben In order to save my hands, I am cutting back on my mail. I also write as succinctly as possible -- please don't be offended. If you send me mail, you _will_ get a response, but please be patient, especially for XEmacs-related mail. If you need an immediate response and it is not apparent in your message, please say so. Thanks for your understanding. See also http://www.666.com/ben/chronic-pain/

2 participants
1 comments

Re: xemacs 21.1.10 and 21.2.34 crash 23 years, 9 months

Simon Josefsson

It's the last call to abort() below. static XtActionProc wm_delete_window (Widget shell, XtPointer closure, XtPointer call_data) { ... if (!kids || !*kids) abort (); widget = kids [0]; if (! XtIsSubclass (widget, dialogWidgetClass)) abort (); Ben Wing <ben(a)666.com> writes: > i meant in lwlib-Xaw.c, line 503 > > Ben Wing wrote: > > > what's the code at this line? > > > > Simon Josefsson wrote: > > > > > start xemacs -no-init-file > > > C-x C-f /etc/resolv.conf (or just some existing file) > > > type "ioasdoiasdiojasd" in the buffer > > > select "delete buffer" from the menu > > > close the popup window using your window manager (I'm using twm). > > > > > > uname -a: Linux localhost.localdomain 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000 i686 unknown > > > > > > ../configure > > > > > > XEmacs 21.1.10 "Capitol Reef" configured for `i686-pc-linux'. > > > > > > Where should the build process find the source code? /home/jas/src/xemacs-21.1 > > > What installation prefix should install use? /usr/local > > > What operating system and machine description files should XEmacs use? > > > `s/linux.h' and `m/intel386.h' > > > What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch > > > Should XEmacs use the GNU version of malloc? yes > > > (Using Doug Lea's new malloc from the GNU C Library.) > > > Should XEmacs use the relocating allocator for buffers? yes > > > What window system should XEmacs use? x11 > > > Where do we find X Windows header files? /usr/X11R6/include > > > Where do we find X Windows libraries? /usr/X11R6/lib > > > Compiling in support for XAUTH. > > > Compiling in support for XPM images. > > > Compiling in support for PNG image handling. > > > Compiling in support for (builtin) GIF image handling. > > > Compiling in support for JPEG image handling. > > > Compiling in support for TIFF image handling. > > > Compiling in native sound support. > > > Compiling in support for Berkeley DB. > > > Compiling in support for LDAP. > > > Compiling in support for ncurses. > > > Compiling in support for GPM (General Purpose Mouse). > > > Compiling in support for proper session-management. > > > Using Lucid menubars. > > > Using Lucid scrollbars. > > > Using Athena dialog boxes. > > > Compiling in DLL support. > > > movemail will use "dot-locking" for locking mail spool files. > > > Using Lisp_Objects with minimal tagbits. > > > > > > [jas＠barbar jas]$ xemacs-21.1.10 -no-init-file > > > > > > Fatal error (6). > > > Your files have been auto-saved. > > > Use `M-x recover-session' to recover them. > > > > > > If you have access to the PROBLEMS file that came with your > > > version of XEmacs, please check to see if your crash is described > > > there, as there may be a workaround available. > > > Otherwise, please report this bug by running the send-pr > > > script included with XEmacs, or selecting `Send Bug Report' > > > from the help menu. > > > As a last resort send ordinary email to `crashes(a)xemacs.org'. > > > *MAKE SURE* to include the information in the command > > > M-x describe-installation. > > > > > > If at all possible, *please* try to obtain a C stack backtrace; > > > it will help us immensely in determining what went wrong. > > > To do this, locate the core file that was produced as a result > > > of this crash (it's usually called `core' and is located in the > > > directory in which you started the editor, or maybe in your home > > > directory), and type > > > > > > gdb /usr/local/bin/xemacs-21.1.10 core > > > > > > then type `where' when the debugger prompt comes up. > > > (If you don't have GDB on your system, you might have DBX, > > > or XDB, or SDB. A similar procedure should work for all of > > > these. Ask your system administrator if you need more help.) > > > > > > Lisp backtrace follows: > > > > > > next-command-event(nil) > > > byte-code("..." [next-command-event event misc-user-event-p event-object yes throw ynp-done t no nil abort menu-no-selection-hook signal quit button-release-e > > > vent-p beep message "please answer the dialog box"] 3) > > > # (catch ynp-done ...) > > > # bind (echo-keystrokes event) > > > # (unwind-protect ...) > > > # bind (ssf79598 prompt) > > > yes-or-no-p-dialog-box("Buffer .emacs modified; kill anyway? ") > > > # bind (prompt) > > > yes-or-no-p("Buffer .emacs modified; kill anyway? ") > > > kill-buffer(#<buffer ".emacs">) > > > #<compiled-function nil "...(4)" [kill-buffer] 2 902850 nil>() > > > call-interactively(kill-this-buffer) > > > # (condition-case ... . error) > > > # (catch top-level ...) > > > Aborted (core dumped) > > > [jas＠barbar jas]$ gdb /usr/local/bin/xemacs-21.1.10 core > > > GNU gdb 19991004 > > > Copyright 1998 Free Software Foundation, Inc. > > > GDB is free software, covered by the GNU General Public License, and you are > > > welcome to change it and/or distribute copies of it under certain conditions. > > > Type "show copying" to see the conditions. > > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > > This GDB was configured as "i386-redhat-linux"... > > > Core was generated by `xemacs-21.1.10 -no-init-file'. > > > Program terminated with signal 6, Aborted. > > > Reading symbols from /usr/X11R6/lib/libXaw.so.6...done. > > > Reading symbols from /usr/lib/libtiff.so.3...done. > > > Reading symbols from /usr/lib/libpng.so.2...done. > > > Reading symbols from /usr/lib/libjpeg.so.62...done. > > > Reading symbols from /usr/lib/libz.so.1...done. > > > Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. > > > Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. > > > Reading symbols from /usr/X11R6/lib/libXt.so.6...done. > > > Reading symbols from /usr/X11R6/lib/libXext.so.6...done. > > > Reading symbols from /usr/X11R6/lib/libX11.so.6...done. > > > Reading symbols from /usr/X11R6/lib/libSM.so.6...done. > > > Reading symbols from /usr/X11R6/lib/libICE.so.6...done. > > > Reading symbols from /lib/libdl.so.2...done. > > > Reading symbols from /lib/libdb.so.3...done. > > > ---Type <return> to continue, or q <return> to quit--- > > > Reading symbols from /usr/lib/libgpm.so.1...done. > > > Reading symbols from /usr/lib/libncurses.so.4...done. > > > Reading symbols from /usr/lib/libldap.so.1...done. > > > Reading symbols from /usr/lib/liblber.so.1...done. > > > Reading symbols from /lib/libm.so.6...done. > > > Reading symbols from /lib/libc.so.6...done. > > > Reading symbols from /lib/ld-linux.so.2...done. > > > Reading symbols from /lib/libnss_files.so.2...done. > > > #0 0x4030ad41 in __kill () from /lib/libc.so.6 > > > (gdb) bt > > > #0 0x4030ad41 in __kill () from /lib/libc.so.6 > > > #1 0x809e2d1 in fatal_error_signal (sig=6) at emacs.c:263 > > > #2 0x4030ac68 in __restore () > > > at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127 > > > #3 0x4030c0d8 in abort () at ../sysdeps/generic/abort.c:88 > > > #4 0x8157bb8 in wm_delete_window (shell=0x845b010, closure=0xbfffeb7c, > > > call_data=0x0) at lwlib-Xaw.c:503 > > > #5 0x4014ddd4 in HandleActions () from /usr/X11R6/lib/libXt.so.6 > > > #6 0x4014e2b6 in HandleSimpleState () from /usr/X11R6/lib/libXt.so.6 > > > #7 0x4014e7f1 in _XtTranslateEvent () from /usr/X11R6/lib/libXt.so.6 > > > #8 0x4012b1ac in XtDispatchEventToWidget () from /usr/X11R6/lib/libXt.so.6 > > > #9 0x4012b9d5 in _XtDefaultDispatcher () from /usr/X11R6/lib/libXt.so.6 > > > #10 0x4012bd2d in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6 > > > #11 0x40136517 in XtAppProcessEvent () from /usr/X11R6/lib/libXt.so.6 > > > #12 0x813a3b9 in emacs_Xt_next_event (emacs_event=0x84c4b00) at event-Xt.c:2381 > > > #13 0x80bee01 in event_stream_next_event (event=0x84c4b00) > > > at event-stream.c:568 > > > #14 0x80bfd79 in next_event_internal (target_event=139217664, allow_queued=1) > > > at event-stream.c:2022 > > > #15 0x80c00d6 in Fnext_event (event=139217664, prompt=136851700) > > > at event-stream.c:2239 > > > #16 0x80c05bb in Fnext_command_event (event=139217664, prompt=136851700) > > > at event-stream.c:2395 > > > ---Type <return> to continue, or q <return> to quit--- > > > #17 0x80a15e8 in funcall_recording_as (recorded_as=136936128, nargs=1, > > > args=0xbfffef88) at eval.c:3193 > > > #18 0x80a55dd in Ffuncall (nargs=2, args=0xbfffef88) at eval.c:3238 > > > #19 0x80852f6 in Fbyte_code (bytestr=136479216, vector=136479328, maxdepth=7) > > > at bytecode.c:416 > > > #20 0x80a10bd in Feval (form=136479192) at eval.c:3063 > > > #21 0x80a519f in internal_catch (tag=137647084, func=0x80a08a8 <Feval>, > > > arg=136479192, threw=0x0) at eval.c:1328 > > > #22 0x8085756 in Fbyte_code (bytestr=136478856, vector=136478896, maxdepth=7) > > > at bytecode.c:566 > > > #23 0x80a2331 in funcall_lambda (fun=136479476, nargs=1, arg_vector=0xbffff3b8) > > > at eval.c:3597 > > > #24 0x80a181e in funcall_recording_as (recorded_as=137647000, nargs=1, > > > args=0xbffff3b4) at eval.c:3214 > > > #25 0x80a55dd in Ffuncall (nargs=2, args=0xbffff3b4) at eval.c:3238 > > > #26 0x80852f6 in Fbyte_code (bytestr=136479564, vector=136479596, maxdepth=5) > > > at bytecode.c:416 > > > #27 0x80a2331 in funcall_lambda (fun=136479628, nargs=1, arg_vector=0xbffff4e4) > > > at eval.c:3597 > > > #28 0x80a181e in funcall_recording_as (recorded_as=136944004, nargs=1, > > > args=0xbffff4e0) at eval.c:3214 > > > #29 0x80a47cb in call1 (fn=136944004, arg0=139111252) at eval.c:3238 > > > #30 0x80824cb in Fkill_buffer (bufname=139103120) at buffer.c:1218 > > > ---Type <return> to continue, or q <return> to quit--- > > > #31 0x80a16c5 in funcall_recording_as (recorded_as=136924128, nargs=1, > > > args=0xbffff5f0) at eval.c:3197 > > > #32 0x80a55dd in Ffuncall (nargs=2, args=0xbffff5f0) at eval.c:3238 > > > #33 0x80852f6 in Fbyte_code (bytestr=136470680, vector=136470704, maxdepth=5) > > > at bytecode.c:416 > > > #34 0x80a2331 in funcall_lambda (fun=136470724, nargs=0, arg_vector=0xbffff73c) > > > at eval.c:3597 > > > #35 0x80a181e in funcall_recording_as (recorded_as=136470724, nargs=0, > > > args=0xbffff738) at eval.c:3214 > > > #36 0x80a473c in apply1 (fn=136470724, arg=136851700) at eval.c:3238 > > > #37 0x80867f2 in Fcall_interactively (function=137645824, > > > record_flag=136851700, keys=136851700) at callint.c:397 > > > #38 0x80a15fb in funcall_recording_as (recorded_as=136924436, nargs=1, > > > args=0xbffff914) at eval.c:3193 > > > #39 0x80a47cb in call1 (fn=136924436, arg0=137645824) at eval.c:3238 > > > #40 0x80c2c39 in execute_command_event (command_builder=0x83f46f0, > > > event=138963492) at event-stream.c:4341 > > > #41 0x80c3315 in Fdispatch_event (event=138963492) at event-stream.c:4685 > > > #42 0x808b30a in Fcommand_loop_1 () at cmdloop.c:579 > > > #43 0x808b4ca in command_loop_1 (dummy=136851700) at cmdloop.c:494 > > > #44 0x80a52bb in condition_case_1 (handlers=136851812, > > > bfun=0x808b4b4 <command_loop_1>, barg=136851700, > > > hfun=0x808ae10 <cmd_error>, harg=136851700) at eval.c:1653 > > > ---Type <return> to continue, or q <return> to quit--- > > > #45 0x808b59e in command_loop_2 (dummy=136851700) at cmdloop.c:256 > > > #46 0x80a519f in internal_catch (tag=136926072, > > > func=0x808b56c <command_loop_2>, arg=136851700, threw=0x0) at eval.c:1328 > > > #47 0x808b04c in initial_command_loop (load_me=136851700) at cmdloop.c:305 > > > #48 0x809d112 in xemacs_21_1_10_i686_pc_linux () at emacs.c:1720 > > > #49 0x809e5cd in main (argc=2, argv=0xbffffc84, envp=0xbffffc90) > > > at emacs.c:2137 > > > (gdb) > > > > -- > > Ben > > > > In order to save my hands, I am cutting back on my mail. I also write > > as succinctly as possible -- please don't be offended. If you send me > > mail, you _will_ get a response, but please be patient, especially for > > XEmacs-related mail. If you need an immediate response and it is not > > apparent in your message, please say so. Thanks for your understanding. > > > > See also http://www.666.com/ben/chronic-pain/ > > -- > Ben > > In order to save my hands, I am cutting back on my mail. I also write > as succinctly as possible -- please don't be offended. If you send me > mail, you _will_ get a response, but please be patient, especially for > XEmacs-related mail. If you need an immediate response and it is not > apparent in your message, please say so. Thanks for your understanding. > > See also http://www.666.com/ben/chronic-pain/

2 participants
1 comments

Re: xemacs-packages/XEmacs.rules, package-info.el? 23 years, 9 months

Adrian Aichner

>>>>> "Norbert" == Norbert Koch <nk(a)LF.net> writes: Norbert> Hi! Norbert> Maybe, my setup is hosed, but I always get errors about Norbert> package-info.el, which can't be found during make. I've Norbert> changed it to package-info and everything looks okay Norbert> (well, for me). This doesn't sound right. Don't you have <xemacs>/lisp/package-info.el? I get this: (locate-library "package-info.el") "c:\\XEmacs\\XEmacs-21.1.10\\lisp\\package-info.el" I can build all packages just fine, even on Windows NT with a native NT XEmacs. Adrian Norbert> 2000-07-08 Norbert Koch <nk(a)LF.net> Norbert> * XEmacs.rules: Change load-directive for package-info. Norbert> Index: XEmacs.rules Norbert> =================================================================== Norbert> RCS file: /usr/CVSroot/XEmacs/xemacs-packages/XEmacs.rules,v Norbert> retrieving revision 1.19 Norbert> diff -u -r1.19 XEmacs.rules Norbert> --- XEmacs.rules 2000/06/23 10:31:08 1.19 Norbert> +++ XEmacs.rules 2000/07/08 16:14:00 Norbert> ＠＠ -135,7 +135,7 ＠＠ Norbert> package-info : package-info.in Makefile $(AUTOLOAD_PATH)/_pkg.el \ Norbert> $(pkg_tar).gz $(pkg_tar).bz2 Norbert> $(XEMACS) $(VANILLA) -batch \ Norbert> - -l package-info.el -f batch-update-package-info \ Norbert> + -l package-info -f batch-update-package-info \ Norbert> '$(VERSION)' $(PKG_TAR_GZ) \ Norbert> '$(REQUIRES)' \ Norbert> '$(AUTHOR_VERSION)' '$(MAINTAINER)' '$(CATEGORY)' Norbert> norbert Norbert> -- Norbert> Wait.. is this a FUN THING or the END of LIFE in Petticoat Junction??

1 participants
0 comments

21.2.34/sparc-sun-solaris2.6 configure buglet 23 years, 9 months

Will Partain

I had 'configure' keel over with: ... checking for AIX... no checking for a working inclusion macro... configure: error: Cannot define a proper SMART_INCLUDE macro. Please report. The config.log (below) suggests that the problem is because I happen to have 'sparc' (a CPP symbol) as part of the pathname of my build dir. Thanks, Will ================= This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:833: checking whether ln -s works configure:1098: checking host system type configure:1593: checking for gcc configure:1697: checking whether the C compiler (/ark/bin/gcc -I/ark/include -O2 -fstrict-aliasing -L/ark/lib) works configure:1715: /ark/bin/gcc -o conftest -I/ark/include -O2 -fstrict-aliasing -I/ark/include -L/ark/lib conftest.c 1>&5 configure:1743: checking whether the C compiler (/ark/bin/gcc -I/ark/include -O2 -fstrict-aliasing -L/ark/lib) is a cross-compiler configure:1748: checking whether we are using GNU C configure:1755: /ark/bin/gcc -E conftest.c configure:1773: checking whether /ark/bin/gcc accepts -g configure:2236: checking how to run the C preprocessor configure:2255: /ark/bin/gcc -E -I/ark/include conftest.c >/dev/null 2>conftest.out configure:2315: checking for AIX configure:2346: checking for a working inclusion macro configure:2360: /ark/bin/gcc -c -I/ark/include -O2 -fstrict-aliasing -I/ark/include conftest.c 1>&5 configure:2355: /item/ark-builds/xemacs--21.2.34/1-solaris2.6/conffoo.h: No such file or directory configure: failed program was: #line 2348 "configure" #include "confdefs.h" int main() { #define SMART_INCLUDE(path,file) <path/file> #define CONFFOO_H_PATH /item/ark-builds/xemacs--21.2.34/sparc-solaris2.6 #define CONFFOO_INCLUDE(file) SMART_INCLUDE (CONFFOO_H_PATH,file) #include CONFFOO_INCLUDE(conffoo.h) ; return 0; } configure:2388: /ark/bin/gcc -c -I/ark/include -O2 -fstrict-aliasing -I/ark/include conftest.c 1>&5 configure:2383: /item/ark-builds/xemacs--21.2.34/1-solaris2.6/conffoo.h: No such file or directory configure: failed program was: #line 2375 "configure" #include "confdefs.h" int main() { #define GLUE_INCLUDE(path,file) <##path##/##file##> #define SMART_INCLUDE(path,file) GLUE_INCLUDE(path,file) #define CONFFOO_H_PATH /item/ark-builds/xemacs--21.2.34/sparc-solaris2.6 #define CONFFOO_INCLUDE(file) SMART_INCLUDE(CONFFOO_H_PATH,file) #include CONFFOO_INCLUDE(conffoo.h) ; return 0; } configure:2417: /ark/bin/gcc -c -I/ark/include -O2 -fstrict-aliasing -I/ark/include conftest.c 1>&5 configure:2412: /item/ark-builds/xemacs--21.2.34/1-solaris2.6/conffoo.h: No such file or directory configure: failed program was: #line 2403 "configure" #include "confdefs.h" int main() { #define GLUE_INCLUDE_2(path,file) <##path##/##file##> #define GLUE_INCLUDE_1(path,file) GLUE_INCLUDE_2(path,file) #define SMART_INCLUDE(path,file) GLUE_INCLUDE_1(path,file) #define CONFFOO_H_PATH /item/ark-builds/xemacs--21.2.34/sparc-solaris2.6 #define CONFFOO_INCLUDE(file) SMART_INCLUDE (CONFFOO_H_PATH,file) #include CONFFOO_INCLUDE(conffoo.h) ; return 0; }

2 participants
1 comments

Commited fix for broken add-log.el in latest xemacs-base, please release 23 years, 9 months

Adrian Aichner

Hello Andreas, when you get a chance, please release a new xemacs-base with my fix to add-log.el. I have become a fan of `patch-to-change-log' already and would miss it! Best regards, Adrian -- Adrian Aichner <adrian(a)xemacs.org>

1 participants
0 comments

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 July 2000