October 2001 - XEmacs-Beta - XEmacs Mailing List Archives

[comp.emacs.xemacs] Xemacs, cygwin and "setup.exe" 23 years, 1 month

Adrian Aichner

Andy, do you know what's wrong? -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

5 participants
5 comments

Windows branch of 21.4 and binaries available 23 years, 1 month

Andy Piper

So I have finally finalized my windows changes and produced binaries and a new netinstaller for them. If you want to build XEmacs yourself then you will need to sync to the windows-21-4 tag. If no problems are found with the installer versions then I will tag the branch and make an announcement. The pre-built installer versions can be found in the usual place: http://ftp.xemacs.org/windows/setup.exe I'll get adrian to update the webpage when we know its all sane. I have fixed most of the problems people have reported with the installer - so it should work ok on Windows 98. I have not been able to find the problem with the connection usage. I have compared our sources with the cygwin installer sources and can find no changes that would affect this. If anyone wants to investigate this further I would be very grateful. Thanks andy CHANGES-msw This file briefly describes all mswindows-specific changes to XEmacs in the OXYMORON series of releases. The mswindows release branch contains additional changes on top of the "official" XEmacs release. These changes are deemed necessary for XEmacs to be fully functional under mswindows. It is not intended that these changes cause problems on UNIX systems, but they have not been tested on UNIX platforms. Caveat Emptor. See the file 'CHANGES-release' for a full list of official changes. to XEmacs 21.4.5 "Civil Service" - Fixed a scrollbar problem when selecting the frame with focus. - Fixed `mswindows-shell-execute' under cygwin. - Added a new function `mswindows-cygwin-to-win32-path' for JDE. - Added support for dialog-based directory selection. - The installer version uses the 21.5 netinstaller. The 21.5 installer now does proper dde file association and adds uninstall capability.

3 participants
3 comments

Can't compile 21.4.5 23 years, 1 month

Norbert Koch

Hi! After applying xemacs-21.4.4-21.4.5.patch to my existing source tree, I can't successfully compile, because of gcc -c -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -W\ shadow -Wpointer-arith -Demacs -I. -DHAVE_CONFIG_H -I/client/include -I/usr/X1\ 1R6/include window.c window.c: In function `window_loop': window.c:2692: invalid operands to binary && gmake[1]: *** [window.o] Error 1 The source reads struct window *p = ...; case UNDEDICATE_BUFFER: { if ((XBUFFER (p->buffer) == XBUFFER (obj)) && (p->dedicated)) p->dedicated = Qnil; break; } Now, the structure doesn't have a member dedicated. Hints? Vitals: FreeBSD 4.3-RELEASE i386 gcc version 2.95.3 [FreeBSD] 20010315 (release) norbert.

4 participants
7 comments

XEmacs using MingW32 23 years, 1 month

Dhruva Krishnamurthy

Hi, I did some hack work in the configure script and found that it assumes the build platform to be UNIX type. This can be found in various places for example: The executable extension variable "ac_exeext" is not set for MingW32 on NT. The path seperator is ";" and not ":" as in UNIX. These were the two major problems I faced. I modified the configure script and the generated config.status to fix the above stated problem. I was able to get Makefile and GNUMakefile for all folders with out any errors or warning. When I do a "make" or a "gmake", it fails in "lib-src" folder stating the following error: cd ./lib-src && gmake all GNUmakefile:130: *** multiple target patterns. Stop. gmake[1]: Entering directory `F:/tmp/XEmacs-Build/xemacs-21.5.3/lib-src' gmake[1]: Leaving directory `F:/tmp/XEmacs-Build/xemacs-21.5.3/lib-src' gmake: *** [lib-src] Error 2 And line 130 has the build target for getopt.o and it is specified only once. I thought that "^M" must be the culprit. It was not. If any one is interested in porting XEmacs to build using MinGW32, please let me know. -- +-----------------------------------------------------------+ | Remaining time multiplied by distress is CONSTANT | +-----------------------------------------------------------+

3 participants
2 comments

RE: How do you modify PATH on Windows XEmacs 21.4.3 23 years, 1 month

Jerker Haglund

> Unfortunately, setenv only affects subprocesses, not the XEmacs process > itself. And since XEmacs is the process loading my DLL, Windows looks at > its PATH, not PATHs for subprocesses. What a hoax! > We could modify setenv to take an optional boolean arg that would > indicate whether this change affects the Xemacs process, or just > subprocesses. Default would be false, and just affect the subprocesses > (the current behavior). True would cause a change to the XEmacs process > as well as causing XEmacs to reload that environment variable into the > lisp variable for the environment. > > Thoughts? Sounds alright to me. > One of the things I've been considering for a while is writing lisp > primitives that allow you to manipulate the windows registry. This would > then allow you to muck with AppPaths under windows which I think would > achieve what you want. Windows-specific though... ... in Win9x you need to edit autoexec.bat and reboot (that's a bit like Unix). But if you change the default environment in .emacs you need to restart xemacs for changes to take effect. That's an installer type thing. Perhaps the dll's should have been installed in the first place? /J. Haglund

2 participants
1 comments

WTF is CBufbyte? (xemacs-21.4.5) 23 years, 1 month

Dmitry Yaitskov

Hi, Subj? It is referenced in fileio.c & callproc.c, but neither the compiler nor I could find it declared anywhere. Any ideas? Thanks. (i686-pc-cygwin) -- Cheers, -Dima.

2 participants
2 comments

Crash Report 23 years, 1 month

Andrew C. Feren

Don't know how useful the following will be, but Xemacs crashed when I ran eudc-expand-inline. I haven't been able to reproduce the crash. Details below. -Andrew uname -a: SunOS cola 5.8 Generic_108528-09 sun4u sparc SUNW,Sun-Blade-100 ./configure '--with-tty=yes' '--with-workshop' '--with-netinstall' '--site-prefixes=/opt/gnome-1.4:/usr/local' '--site-runtime-libraries' '/lib:/usr/lib:/opt/gnome-1.4/lib:/usr/local:/usr/openwin/lib' XEmacs 21.4.4 "Artificial Intelligence" configured for `sparc-sun-solaris2.8'. Compilation / Installation: Source code location: /user/humpback/aferen/src/new/xemacs-21.4.4 Installation prefix: /usr/local Additional prefixes: /opt/gnome-1.4 /usr/local Runtime library search path: /lib:/usr/lib:/opt/gnome-1.4/lib:/usr/local:/usr/openwin/lib Operating system description file: `s/sol2.h' Machine description file: `m/sparc.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wshadow -Wsign-compare -Wpointer-arith Relocating allocator for buffers: yes GNU version of malloc: yes Window System: Compiling in support for the X window system: - X Windows headers location: /usr/dt/include /usr/openwin/include - X Windows libraries location: /usr/dt/lib /usr/openwin/lib - Handling WM_COMMAND properly. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Using Motif native widgets. TTY: Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for TIFF images. Sound: Compiling in support for sound (native). Databases: Compiling in support for Berkeley database. Compiling in support for GNU DBM. Compiling in support for LDAP. Internationalization: Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for ToolTalk. Compiling in support for Sun WorkShop. Compiling in support for dynamic shared object modules. ========================================= (gdb) where #0 0x11b134 in print_internal (obj=0, printcharfun=2315444, escapeflag=1) at print.c:1224 #1 0x11c9a4 in Fprin1 (object=0, stream=2315444) at print.c:637 #2 0x819d4 in Fbacktrace (stream=2315444, detailed=2164764) at eval.c:5192 #3 0x7703c in fatal_error_signal (sig=11) at emacs.c:518 #4 <signal handler called> #5 0x7fab4 in Ffuncall (nargs=27, args=0xffbec638) at eval.c:3508 #6 0x54a0c in execute_optimized_program (program=0xdbf11f "\004", stack_depth=27, constants_data=0xdbfd10) at bytecode.c:746 #7 0x54664 in funcall_compiled_function (fun=18057104, nargs=3, args=0xffbec7c8) at bytecode.c:515 #8 0x7f6f8 in Feval (form=17406544) at eval.c:3388 #9 0x10cb48 in readevalloop (readcharfun=14413952, sourcename=17170676, evalfun=0x7ef80 <Feval>, printflag=0) at lread.c:1449 #10 0x10ba18 in Fload_internal (file=17170676, noerror=2164740, nomessage=2164764, nosuffix=2164764, codesys=0, used_codesys=50) at lread.c:737 #11 0x7fc0c in Ffuncall (nargs=6, args=0xffbecc84) at eval.c:3528 #12 0x54a0c in execute_optimized_program (program=0x254299 "\207<À", stack_depth=6, constants_data=0x360a90) at bytecode.c:746 #13 0x54664 in funcall_compiled_function (fun=3528648, nargs=4, args=0xffbece60) at bytecode.c:515 #14 0x7fd60 in Ffuncall (nargs=4, args=0xffbece5c) at eval.c:3563 ---Type <return> to continue, or q <return> to quit--- #15 0x54a0c in execute_optimized_program ( program=0x5e839e "®\004Ï\211\024)\t¬\006ØÛ\r\"\210\f«\aÜÝ\fA\"\210*)\207efs-ftp-path", stack_depth=4, constants_data=0x5e8e10) at bytecode.c:746 #16 0x54664 in funcall_compiled_function (fun=6566844, nargs=1, args=0xffbed048) at bytecode.c:515 #17 0x7fd60 in Ffuncall (nargs=1, args=0xffbed044) at eval.c:3563 #18 0x54a0c in execute_optimized_program ( program=0xffbed0e5 "\210ÅÇ!¬\004È \210Â\207", stack_depth=1, constants_data=0x1056210) at bytecode.c:746 #19 0x57848 in Fbyte_code (instructions=-4271920, constants=17129984, stack_depth=5) at bytecode.c:2403 #20 0x7f4d4 in Feval (form=17407564) at eval.c:3331 #21 0x10cb48 in readevalloop (readcharfun=11754368, sourcename=9878484, evalfun=0x7ef80 <Feval>, printflag=0) at lread.c:1449 #22 0x10ba18 in Fload_internal (file=9878484, noerror=2164740, nomessage=2164764, nosuffix=2164764, codesys=0, used_codesys=30) at lread.c:737 #23 0x7fc0c in Ffuncall (nargs=6, args=0xffbed65c) at eval.c:3528 #24 0x54a0c in execute_optimized_program (program=0x254299 "\207<À", stack_depth=6, constants_data=0x360a90) at bytecode.c:746 #25 0x54664 in funcall_compiled_function (fun=3528648, nargs=4, args=0xffbed838) at bytecode.c:515 #26 0x7fd60 in Ffuncall (nargs=4, args=0xffbed834) at eval.c:3563 ---Type <return> to continue, or q <return> to quit--- #27 0x54a0c in execute_optimized_program ( program=0x5e839e "®\004Ï\211\024)\t¬\006ØÛ\r\"\210\f«\aÜÝ\fA\"\210*)\207efs-ftp-path", stack_depth=4, constants_data=0x5e8e10) at bytecode.c:746 #28 0x54664 in funcall_compiled_function (fun=6566844, nargs=4, args=0xffbeda1c) at bytecode.c:515 #29 0x7fd60 in Ffuncall (nargs=4, args=0xffbeda18) at eval.c:3563 #30 0x802ac in Fapply (nargs=2, args=0xffbedb68) at eval.c:3804 #31 0x7fd10 in Ffuncall (nargs=2, args=0xffbedb64) at eval.c:3549 #32 0x54a0c in execute_optimized_program ( program=0xdf55df "*È\rÉN\034\030\f«\005\f\t!\210*\207", stack_depth=2, constants_data=0xd6f3d0) at bytecode.c:746 #33 0x54664 in funcall_compiled_function (fun=13263664, nargs=5, args=0xffbedd34) at bytecode.c:515 #34 0x7fd60 in Ffuncall (nargs=5, args=0xffbedd30) at eval.c:3563 #35 0x83494 in call5 (fn=6439972, arg0=2310988, arg1=11028948, arg2=2164740, arg3=2164764, arg4=2164764) at eval.c:4255 #36 0x10b524 in Fload_internal (file=11028948, noerror=2164740, nomessage=2164764, nosuffix=2164764, codesys=0, used_codesys=14) at lread.c:571 #37 0x7fc0c in Ffuncall (nargs=6, args=0xffbee084) at eval.c:3528 #38 0x54a0c in execute_optimized_program (program=0x254299 "\207<À", stack_depth=6, constants_data=0x360a90) at bytecode.c:746 #39 0x54664 in funcall_compiled_function (fun=3528648, nargs=4, ---Type <return> to continue, or q <return> to quit--- args=0xffbee260) at bytecode.c:515 #40 0x7fd60 in Ffuncall (nargs=4, args=0xffbee25c) at eval.c:3563 #41 0x54a0c in execute_optimized_program ( program=0x5e839e "®\004Ï\211\024)\t¬\006ØÛ\r\"\210\f«\aÜÝ\fA\"\210*)\207efs-ftp-path", stack_depth=4, constants_data=0x5e8e10) at bytecode.c:746 #42 0x54664 in funcall_compiled_function (fun=6566844, nargs=4, args=0xffbee444) at bytecode.c:515 #43 0x7fd60 in Ffuncall (nargs=4, args=0xffbee440) at eval.c:3563 #44 0x83448 in call4 (fn=2310988, arg0=4664164, arg1=2164740, arg2=2164740, arg3=2164740) at eval.c:4235 #45 0x7ee6c in do_autoload (fundef=4663004, funname=4806828) at eval.c:3146 #46 0x7ea70 in Fcommand_execute (cmd=4806828, record_flag=2164740, keys=2164740) at eval.c:2955 #47 0xad20c in execute_command_event (command_builder=0x4abc40, event=10896292) at event-stream.c:3915 #48 0xad850 in Fdispatch_event (event=10896292) at event-stream.c:4199 #49 0x5e584 in Fcommand_loop_1 () at cmdloop.c:583 #50 0x5e7ec in command_loop_1 (dummy=2164740) at cmdloop.c:494 #51 0x7bd94 in condition_case_1 (handlers=2164836, bfun=0x5e7d0 <command_loop_1>, barg=2164740, hfun=0x5e84c <cmd_error>, harg=2164740) at eval.c:1651 #52 0x5e95c in command_loop_2 (dummy=2164740) at cmdloop.c:256 #53 0x83bb4 in internal_catch (tag=2244780, func=0x5e910 <command_loop_2>, ---Type <return> to continue, or q <return> to quit--- arg=2164740, threw=0x0) at eval.c:1317 #54 0x5e130 in initial_command_loop (load_me=2164740) at cmdloop.c:305 #55 0x789e8 in sort_args (argc=1977344, argv=0xffbeebe4) at emacs.c:2344 (gdb) -- -Andrew Feren Cetacean Networks, Inc. Portsmouth, NH

1 participants
0 comments

XEmacs 21.4.5 does not compile under Win32, because CBufbyte is not declared 23 years, 1 month

"Peter Arius"

Dear Bug Team! I just downloaded xemacs-21.4.5.tar.gz and tried to compile on Windows NT/ VC++ 6.0, but src/fileio.c failed in line 955 because CBufbyte was not declared. I think the following patch does the right thing: *** src/fileio.c.orig Wed Oct 24 18:46:30 2001 --- src/fileio.c Wed Oct 24 18:48:02 2001 *************** *** 952,958 **** if (IS_DIRECTORY_SEP (nm[1])) { if (strcmp ((char *) nm, (char *) XSTRING_DATA (name)) != 0) ! name = build_string ((CBufbyte *) nm); } /* drive must be set, so this is okay */ else if (strcmp ((char *) nm - 2, --- 952,958 ---- if (IS_DIRECTORY_SEP (nm[1])) { if (strcmp ((char *) nm, (char *) XSTRING_DATA (name)) != 0) ! name = build_string ((char *) nm); } /* drive must be set, so this is okay */ else if (strcmp ((char *) nm - 2, Kind regards, Peter ================================================================ System Info to help track down your bug: --------------------------------------- OS version: Windows NT Version 4.0 OS: Windows_NT XEmacs 21.4.5 \"Civil Service\" configured for `i586-pc-win32'. Building XEmacs in \"E:\\public\\XEmacs\\xemacs-21.4.5\\nt\". Using compiler \"cl -nologo -W3 -O2 -G5 -ML\". Installing XEmacs in \"c:\\Program Files\\XEmacs\". Package path is \"~\\.xemacs;;c:\\Program Files\\XEmacs\\lib\\xemacs\\site-packages;c:\\Program Files\\XEmacs\\lib\\xemacs\\xemacs-packages\". Compiling in support for Microsoft Windows native GUI. 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 toolbars. Compiling in support for dialogs. Compiling in support for widgets. Compiling in support for native sounds. Compiling in fast dired implementation. -- Peter Arius, Software Process Improvement method park Software AG Wetterkreuz 19a, 91058 Erlangen, Germany Tel. +49-9131-97206-301 mailto:Peter.Arius＠methodpark.de Fax +49-9131-97206-222 http://www.methodpark.de -- At Siemens Med: -- Tel. +49-9131-84-8269 mailto:Peter.Arius＠erln.gepas.de

1 participants
0 comments

["Andrea Francesco Merello" <AMERELL1@irf.com>] xemacs installation 23 years, 1 month

Adrian Aichner

Hello Andrea! Please ask for for help on comp.emacs.xemacs for stable XEmacs releases (like 21.1.13) or xemacs-beta(a)xemacs.org for beta (currently 21.5-b3) and gamma (currently 21.4.5) versions. Your diagnostic information below doesn't seem to give enough details to pinpoint the problem. Best regards, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

MinGW compilation on Windows 23 years, 1 month

Andrew Begel

I have a bunch of patches that I'd like to submit to enable XEmacs to be compiled by a native MinGW gcc (rather than Cygwin's cross-compiler gcc -mno-cygwin). A MinGW installation gcc (www.mingw.org) requires different include paths than gcc -mno-cygwin. There are also some #defines in the wrong places and some typedefs that need to be altered. Comparing the preprocessor directives defined by MinGW's Windows native gcc, and the ones defined by Cygwin's gcc -mno-cygwin, the only difference is that __MINGW__ is merely defined -D__MINGW__ by cygwin, whereas in mingw gcc, it's defined -D__MINGW__=1.0. Would it be a bad thing to add in a new #define to XEmacs that would discriminate between these two compilers, and then modify the places in the code (and configure script) that care about the difference to get the differences right? It would enable me to get rid of a whole load of patches I apply to each new XEmacs release to make it compile correctly under MinGW. What do you think? Andrew ----------- Andrew Begel Computer Science Division UC Berkeley

2 participants
1 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 October 2001