November 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Install from read-only FS not possible 25 years, 6 months

Neal D. Becker

OK, you're probably right - it's probably not worth worrying about.

1 participants
0 comments

Re: Install from read-only FS not possible 25 years, 6 months

Didier Verna

nbecker writes: nbecker> One possibility is that the compilied lisp goes to a local dir. But it would be a waste of disk. Is it really worth it ? Why can't the guy that installed the sources do a first compilation ? They don't change after that. Then, you can recompile the executable with any fancy option you want without dealing with lisp byte-compilation. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: Install from read-only FS not possible 25 years, 6 months

Neal D. Becker

>>>>> "dv" == Didier Verna <verna(a)inf.enst.fr> writes: dv> nbecker writes: nbecker> You can configure in a different directory. But the build will nbecker> create a link to the lisp source, and will try to byte-compile to nbecker> that directory. So building with read-only access will not work. dv> You've got a point there, I think. The original policy was logical dv> however: you only replicate what can be architecture dependant. How is it that dv> somebody installs the sources read-only without doing at least one whole dv> compilation ? One possibility is that the compilied lisp goes to a local dir.

1 participants
0 comments

Re: Install from read-only FS not possible 25 years, 6 months

Michael Sperber

>>>>> "dv" == Didier Verna <verna(a)inf.enst.fr> writes: dv> nbecker writes: nbecker> You can configure in a different directory. But the build will nbecker> create a link to the lisp source, and will try to byte-compile to nbecker> that directory. So building with read-only access will not work. dv> You've got a point there, I think. The original policy was logical dv> however: you only replicate what can be architecture dependant. How is it that dv> somebody installs the sources read-only without doing at least one whole dv> compilation ? Don't we ship releases with .elc files? For beta versions, read-only sources don't seem to make much sense. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Install from read-only FS not possible 25 years, 6 months

Didier Verna

nbecker writes: nbecker> You can configure in a different directory. But the build will nbecker> create a link to the lisp source, and will try to byte-compile to nbecker> that directory. So building with read-only access will not work. You've got a point there, I think. The original policy was logical however: you only replicate what can be architecture dependant. How is it that somebody installs the sources read-only without doing at least one whole compilation ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

alpha-linux build failure 25 years, 6 months

Neal D. Becker

[...] Loading site-load... (368) Finding pointers to doc strings... Finding pointers to doc strings...done Dumping under the name xemacs Purespace usage: 1283232 of 1283232 (100%). Testing for Lisp shadows ... temacs can only be run in -batch mode. make[2]: Leaving directory `/usr/local/src/xemacs-20/src' make[1]: Leaving directory `/usr/local/src/xemacs-20/src' Building finder database ... temacs can only be run in -batch mode. This scary warning may be related: /usr/bin/ld: Warning: size of symbol `re_syntax_options' changed from 4 to 8 in /lib/libc.so.6.1

1 participants
0 comments

Install from read-only FS not possible 25 years, 6 months

Neal D. Becker

You can configure in a different directory. But the build will create a link to the lisp source, and will try to byte-compile to that directory. So building with read-only access will not work.

1 participants
0 comments

pc-select bug/feature? 25 years, 6 months

Sean MacLennan

Gary D. Foster, I have `(setq signal-error-on-buffer-boundary nil)' in my .emacs and always wondered why it didn't work but never got around to looking into it. However, I installed Linux 5.2, put a new board in my system, recompiled XEmacs and now beeps are very slow. This forced my to look into the problem. The root of it seems to be that pc-select-move-line-up, pc-select-move-line-down (for example) call next-line directly. `signal-error-on-buffer-boundry' only works if called interactively. So changing the (next-line arg) calls to (call-interactively 'next-line arg) fixes the problem. I am not sure if this is considered a bug or a feature. Sean -- Sean MacLennan Just crank that volume to the point of pain. Ottawa, Canada Why waste good music on a brain? http://www.storm.ca/~seanm (Spinal Tap)

1 participants
0 comments

xemacs 20.4 question 25 years, 6 months

Justin Vallon

Is this the right place for a 20.4 question, or should I try the newsgroup (or 21.0)? Config: MkLinux, gcc 2.8.0, xemacs-20.4.tar.gz. Running ./configure fails with messages in config.log saying: ld: cannot open linker script file ppc.ldscript: No such file or directory $ grep ldscript src/m/powerpc.h #define LD_SWITCH_MACHINE -T ppc.ldscript [ I think this should be -T ${srcdir}/src/ppc.ldscript if anything ] LD_SWITCH_MACHINE gets passed to gcc eventually. But, there is no ppc.ldscript anywhere in the tree. I have a ppc.ldscript 'patch' from a xemacs-20.3 rpm, and that gets configure to run to completion. Why isn't there a ppc.ldscript in xemacs-20.4? There's an ldscript /usr/lib/ldscripts/elf32ppc.x that looks very similar to ppc.ldscript. Maybe ppc.ldscript isn't needed anymore with an elf ld? I'm not up on the history of elf + ld. -Justin vallon(a)mindspring.com

1 participants
0 comments

Re: New release of toolbar-fancy package 25 years, 6 months

Jan Vroonhof

Sorry to cause guys so much problems. The makefile was picking up and old version of the lisp file somehow. I have made http://www.math.ethz.ch/~vroonhof/emacs/packages/toolbar-fancy-0.05-pkg.t... http://www.math.ethz.ch/~vroonhof/emacs/packages/toolbar-fancy-0.05-src.t... Changed 1. I have tested the bin package this time. Made sure the fixed version got in. xemacs -vanilla & (require 'toolbar-fancy) M-x customize-variable RET use-fancy-toolbar RET This gives me all the toolbars I want. 2. I have copied the NeXt icons to their captions versions. That shouldn't be needed but it is. Somebody still needs to paint the captions on. Jan

4 participants
3 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 November 1998