May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[Success] 21.0 "Russian White" XEmacs Lucid (beta39) on i386-pc-c ygwin32 26 years, 6 months

Michael Hill

Built smoothly from tarballs. Toolbar still causes problems with file operations and Info. I also get the size problem with the second frame, but the third one looks okay. I'm reporting to the beta list mainly to point out that 'build-report' still sends to the beta list. :-) Mike > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b39/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include' XEmacs 21.0-b39 "Russian White" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b39 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /binary/xemacs-21.0-b39/beta.err does not exist!

1 participants
0 comments

[PATCH] fix for the CDE DnD Problem in b39 26 years, 6 months

Oliver Graf

Hi there! A quick fix for the parse error in line 1110. Regards, Oliver. --- frame-x.c~ Mon May 11 14:04:43 1998 +++ frame-x.c Mon May 11 14:12:08 1998 ＠＠ -1106,10 +1106,10 ＠＠ - the data must be converted to the new format (URL/MIME) */ return; - + /* DtDndTransferCallbackStruct *transferInfo = (DtDndTransferCallbackStruct *) callData; - + */ if (transferInfo == NULL) return;

2 participants
1 comments

Gnuserv and W32 26 years, 6 months

Jan Vroonhof

As I understand it the NTEmacs folk have their own version of gnuclient. Am I correct in assuming that ours currently isn't supported on xemacs-nt? (At the very least gnuserv.el needs to handle type 'msw devices) Jan

2 participants
1 comments

[SUCCESS] 21.0 "Russian White" XEmacs Lucid (beta39) on i386-pc-cygwin32 26 years, 6 months

Andy Piper

Built jsut fine. andy > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /development/build/xemacs-20/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT ARMAGEDON 4.0 19.1 i586 unknown ./configure '--site-includes=/usr/local/include' '--package-path=/usr/gnu/lib/xemacs/packages' '--prefix=/usr/gnu' XEmacs 21.0-b39 "Russian White" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /development/build/xemacs-20 What installation prefix should install use? /usr/gnu What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /development/build/xemacs-20/beta.err does not exist!

1 participants
0 comments

Re: dragndrop & frame-x.c problems, Russian White 26 years, 6 months

Oliver Graf

Jason R Mastaler <jason(a)mastaler.com> writes: > With my default set of configure options (illustrated by the > Installation file attached below), I was unable to compile beta-39 due > to the following problems with frame-x.c. > > However, after re-configuring with '--with-dragndrop=no' added, > Russian White compiled without problems. A SUCCESS build report on > this one will be sent to the xemacs-build-reports list shortly. I'm the guilty one. CDE is broken. '--without-cde' should make it compile with OffiX DnD. Regards, Oliver.

1 participants
0 comments

Re: [Failure] XEmacs 21.0-b39 "Russian White", sparc-sun-solaris2.5.1 26 years, 6 months

Oliver Graf

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > My first attempt failed DnD-related, I believe. > > Have I missed anything obvious? > > That's where the trouble starts: > > "frame-x.c", line 1110: syntax error before or at: * This is from CDE. Try to configure '--without-cde', cause it's broken (and it seems that I did'nt close a comment right ;-) I will take a look at the CDE stuff today and tomorrow. But there is stuff in the CDE code I don't know (some speccount in x_cde_transfer_callback, frame-x.c around line 1150 -- it gets set at the start of a block and at the end it is unbinded to nil?). Regards, Oliver.

1 participants
0 comments

trouble with DnD changes under HPUX 10.20 26 years, 6 months

Peter Windle

refuses to compile frames-x.c: cc -c -O +Onolimit -Ae +Z -z -Demacs -I. -DHAVE_CONFIG_H -I/opt/audio/include -I/usr/dt/include -I/usr/local/include -Ae -Wp,-H100000 +Olibcalls -I/usr/dt/include -I/usr/include/X11R6 -I/usr/include/Motif1.2_R6 -I/usr/contrib/X11R6/include -I/usr/contrib/X11R6/include frame-x.c cc: "frame-x.c", line 1110: error 1000: Unexpected symbol: "DtDndTransferCallbackStruct". cc: "frame-x.c", line 1110: error 1588: "transferInfo" undefined. cc: "frame-x.c", line 1113: error 1563: Expression in if must be scalar. cc: "frame-x.c", line 1119: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1119: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1119: error 1563: Expression in if must be scalar. cc: "frame-x.c", line 1123: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1123: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1123: error 1566: Test expression in for must be scalar. cc: "frame-x.c", line 1125: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1125: error 1532: Reference through a non-pointer. cc: "frame-x.c", line 1125: error 1529: Cannot select field of non-structure. ..and so forth problem appears to be caused by: + /* + this needs to be changed to the new protocol: + - we need the button, modifier and pointer states to create a + correct misc_user_event + - the data must be converted to the new format (URL/MIME) + */ + return; + DtDndTransferCallbackStruct *transferInfo = (DtDndTransferCallbackStruct *) callData; the HP C compiler complains about things after a return? or something... #if 0ing everything everything after the return seems to get me a compile out, anyway. uname -a: HP-UX sdlhpp63 B.10.20 A 9000/778 2006473329 two-user license ./configure '--site-includes=/opt/audio/include -I/usr/dt/include -I/usr/local/include' '--site-libraries=/opt/audio/lib -L/usr/dt/lib -L/usr/local/lib' '--x-includes=/usr/include/X11R6 -I/usr/include/Motif1.2_R6 -I/usr/contrib/X11R6/include' '--x-libraries=/usr/lib/X11R6 -L/usr/lib -L/usr/contrib/X11R6/lib' '--with-scrollbars=lucid' '--with-menubars=lucid' '--with-gnu-make' '--package-path=/local/packages' '--gung-ho' XEmacs 21.0-b39 "Russian White" configured for `hppa1.1-hp-hpux10.20'. Where should the build process find the source code? /local/xemacs-beta What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/hpux10.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -O +Onolimit -Ae +Z -z Should XEmacs use the GNU version of malloc? yes 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/dt/include /usr/include/X11R6 -I/usr/include/Motif1.2_R6 -I/usr/contrib/X11R6/include /usr/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/X11R6 -L/usr/lib -L/usr/contrib/X11R6/lib Additional header files: /opt/audio/include -I/usr/dt/include -I/usr/local/include Additional libraries: /opt/audio/lib -L/usr/dt/lib -L/usr/local/lib Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

2 participants
1 comments

package problems 26 years, 6 months

Jeff Miller

os-utils & edit-utils are still listed as single packages. They should be regular. What happened to overlay? I've been playing with flyspell-mode which requires it. Jeff

2 participants
1 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> >> > Michael, what was your opinion about the optimization we discussed, >> > which would forbid directories ending with `.el' or `.elc'? I think >> > it would be worth implementing it, especially for non-Unix systems, >> > where a stat is extremely costly. >> >> I thought this was taken care of by limiting the recursion depth? Hrvoje> So did I, but this appears not to be the case. Ermh, out here XEmacs started up *vastly* faster after limiting recursion depth. If it's still not fast enough, it's a different issue. If limiting `packages-hierarchy-depth' didn't improve things, the problem will not be taken care of by forbidding *.el and *.elc anyway, because recursion simply doesn't progress to that level. I'll look into it. Note that---because of the smarter startup code and the package searching---there *must* be more stats than in 20.4. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Proposal: XEmacs startup, Microsoft, and kernels 26 years, 6 months

Didier Verna

"Lonhyn T. Jasinskyj" <lonhyn(a)nas.nasa.gov> writes: > I recently read that Microsoft has recently improved the startup speed > of Internet Explorer to be much faster than Netscape. They accomplished > this by putting large chunks of what is done in IE startup into the > "operating system". 'course. The idea is that if you try to uninstall IE from w98, your system will not work properly anymore. > I was hoping that we could accomplish the same with XEmacs by dropping > as much of it as possible into device drivers. I can imagine Bill Gates shiping XEmacs with w98 ... and if you try to uninstall it, you crash your system :-) OK guys, I candidate for collecting the donations in order to buy a NT source code license ...

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 May 1998