October 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Patches Applied for 21.1.8 25 years, 1 month

Gunnar Evermann

Vin Shelton <acs(a)xemacs.org> writes: > Thanks for your suggestions. I have applied the 2nd set of patches for > 21.1.8. I have got another one: http://www.xemacs.org/list-archives/xemacs-patches/9901/msg00039.html this is REALLY old but was never applied to 21.0 or 21.1 for some reason. The patch is against something like 21.2.8 but it should be easy enough to adapt. I only realised we missed this when working on a new 21.1.7 bug report on c.e.x. > I'm still hoping for more mule feedback. Does mule work in this > release? I'll wait a bit for Adrian's patch and for more testing; I'd > like to release sometime next week, though. I tried typing Russian, Japanese and Chinese and it looked OK to me, but I can only read one of these languages. Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Gunnar Evermann

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Robert Pluim <rpluim(a)bigfoot.com> writes: > > > For more information and suggestions for which packages to install see > > the file README.packages. Go read it before you do anything else. I > > mean it. If you haven't read it, don't complain about various > > functions being missing from your installation. > > > > --end-- > > > > (or is that too rude/strong/arrogant/elitist/whatever ?) > > It is a bit on the rude side even for a dutch guy like me. I don't find it too rude --- actually I love it. We should add a similar comment referring to the PROBLEMS file. :-) For example I consider it extremely rude of our users to send us those stupid bug reports concerning Fskip_syntax_backward crashes despite the unambiguous note in PROBLEMS and the fact that it has been discussed to death in c.e.x. FYI I just answered the 80th report sent to our bug tracking system concerning this crash. I am really grateful for the fact that the lack of xemacs-base does not cause xemacs to print out the crash-reporting email address... Gunnar

1 participants
0 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Jan Vroonhof

Mauro Condarelli <mcondarelli(a)soft-in.com> writes: > The file README.packages contain information vital to have a fully > working XEmacs. This information was not included in this file only > because it is too large for this terse INSTALL. Seems fine. Vin, could you make this change or do you need a patch? Jan

1 participants
0 comments

configure bug 25 years, 1 month

Georg Nikodym

The cvs tree (as of now) has syntax errors in configure. Patch follows: (undefined) 167$ cvs diff configure configure.in Index: configure =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/configure,v retrieving revision 1.110.2.42 diff -c -r1.110.2.42 configure *** configure 1999/10/21 14:00:28 1.110.2.42 --- configure 1999/10/22 00:28:58 *************** *** 7714,7720 **** if test "$have_xaw3d"; then libs_x="-lXaw3d $libs_x" && if test "$extra_verbose" = "yes"; then echo " Prepending \"-lXaw3d\" to \$libs_x"; fi else ! libs_x="-lXaw $libs_x" && if test "$extra_verbose" = "yes"; then echo " Prepending \"-lXaw\" to \$libs_x"; fi ;; *athena* ) { test "$extra_verbose" = "yes" && cat << \EOF Defining LWLIB_USES_ATHENA --- 7714,7720 ---- if test "$have_xaw3d"; then libs_x="-lXaw3d $libs_x" && if test "$extra_verbose" = "yes"; then echo " Prepending \"-lXaw3d\" to \$libs_x"; fi else ! libs_x="-lXaw $libs_x" && if test "$extra_verbose" = "yes"; then echo " Prepending \"-lXaw\" to \$libs_x"; fi ; fi ;; *athena* ) { test "$extra_verbose" = "yes" && cat << \EOF Defining LWLIB_USES_ATHENA Index: configure.in =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/configure.in,v retrieving revision 1.111.2.46 diff -c -r1.111.2.46 configure.in *** configure.in 1999/10/21 14:00:27 1.111.2.46 --- configure.in 1999/10/22 00:29:01 *************** *** 2922,2928 **** if test "$have_xaw3d"; then XE_PREPEND(-lXaw3d, libs_x) else ! XE_PREPEND(-lXaw, libs_x) ;; *athena* ) AC_DEFINE(LWLIB_USES_ATHENA) AC_DEFINE(NEED_ATHENA) --- 2922,2928 ---- if test "$have_xaw3d"; then XE_PREPEND(-lXaw3d, libs_x) else ! XE_PREPEND(-lXaw, libs_x) ; fi ;; *athena* ) AC_DEFINE(LWLIB_USES_ATHENA) AC_DEFINE(NEED_ATHENA)

3 participants
2 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Reid Rivenburgh

>> Jan Vroonhof writes: > Terje Bless <link(a)tss.no> writes: >> >Is it my (attempt at) English that is confusing you or is this a >> >question about why they are not in the core? >> >> The latter. > The answer is: To allow them be released in a different cycle than > the main XEmacs releases. > The jury is still out on whether that is actually beneficial. I understand that position, and it makes sense. I think that if an add on is essential, though, it should be included with what you download to get the application running. Is there any reason xemacs-base (and efs?) can't be bundled with the XEmacs tarball and installed wherever packages get installed when xemacs is installed? Then it would still be a package and could be upgraded independently of XEmacs itself. I suppose the install process would have to ensure that a newer version of xemacs-base wasn't already installed, but that doesn't sound impossible. I apologize in advance if I'm making wrong assumptions; I've only read vague rumblings about this issue. I installed 21.1 awhile ago and don't remember what difficulties I may have faced. Reid

2 participants
1 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Jan Vroonhof

Robert Pluim <rpluim(a)bigfoot.com> writes: > For more information and suggestions for which packages to install see > the file README.packages. Go read it before you do anything else. I > mean it. If you haven't read it, don't complain about various > functions being missing from your installation. > > --end-- > > (or is that too rude/strong/arrogant/elitist/whatever ?) It is a bit on the rude side even for a dutch guy like me. Without that last sentence it is OK. Maybe we should add some warning to INSTALL that not reading README.packages has been shown to cause cancer in laboratory animals. Jan

4 participants
3 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Jan Vroonhof

"Robin S. Socha" <robin(a)socha.net> writes: > echo "NOTE: If this script fails, read the INSTALL file and" > echo "install by hand." I hate interactive install scripts. A much better solution would be a warning in startup.el that screams loudly when XEmacs doesn't find any packages. If XEmacs could actually bootstrap I would be extremely in favor of a make get-packages and a make site-custimize Jan

1 participants
0 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 25 years, 1 month

Mark Thomas

Jan Vroonhof writes: >> >Is it my (attempt at) English that is confusing you or is this a >> >question about why they are not in the core? >> >> The latter. > The answer is: To allow them be released in a different cycle than the > main XEmacs releases. One objection I have to the package system is the idea that the "main XEmacs releases" (which I will call "XEmacs distributions") are the core and only the core. Instead of trying to figure out what should be in the core and what shouldn't (and failing terribly in the case of xpm-button-create), a better solution would be to make an XEmacs distribution the core and some set of bundled packages. The set of bundled packages should at least be enough to bootstrap XEmacs to use the PUI to download the remainder of the packages from the web/ftp sites. Right now, this means xemacs-base and efs; whenever the http-based package system that I've heard mention gets written, it can replace efs. At the other extreme, the bundled packages could be contents of the sumo tarball. In practice, you'd probably go for the something in the middle, say the most "popular" packages. This still gives you the flexibility of releasing packages on a different cycle than the core, but gives you more than a barely functioning XEmacs. -Mark

3 participants
2 comments

Re: Patches Applied for 21.1.8 25 years, 1 month

Andreas Jaeger

>>>>> Vin Shelton writes: Vin> I'm still hoping for more mule feedback. Does mule work in this I haven't checked that 21.1.8 works - first have to remove my local patches and need to find some time. The problems were cyrillic, japanese, and chinese support. A simple test would be to run "Mule->Set language environment" to each language. If anything fails, you've got trouble. Vin> release? I'll wait a bit for Adrian's patch and for more testing; I'd Vin> like to release sometime next week, though. Andreas -- Andreas Jaeger SuSE Linux Labs aj(a)suse.de private aj(a)arthur.rhein-neckar.de

1 participants
0 comments

Re: *** PANIC *** The C compiler can no longer build working executables. 25 years, 1 month

Justin Vallon

Vin Shelton <acs(a)xemacs.org> writes: > I'm configuring with the following option: --with-widgets=athena3d > > In order to make this work, I had to make this link: > > lrwxrwxrwx 1 root root 15 Oct 1 21:09 /usr/X11R6/lib/libXaw3d.so -> libXaw3d.so.6.1 Maybe you installed the "runtime" libXaw3d, but not the "development" package/etc? Typically, only the dev package has the .so symlinks. The linker resolves the libXaw3d.so to libXaw3d.so.6.1 at link time, and at runtime, the .so link is not needed. This allows a non-dev system to have libXaw3d.so.6.1 and libXaw3d.so.6.2 installed on the same system, without libXaw3d.so being in conflict (between 6.1 and 6.2). -- -Justin vallon(a)mindspring.com

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 October 1999