Cygwin/21.5-b32 bug?
11 years, 12 months
Henry S. Thompson
Henry S. Thompson
I've recently been having my XEmacs (built from source under Cygwin,
21.5-b32) go into a full-cpu un-interruptable loop. Running under gdb
shows this after the lockup:
[main] xemacs-21.5-b32 13400 sig_send: wait for sig_complete event
failed, signal -13, rc 258, Win32 error 0
gdb is also stuck at this point
procexp shows gdb stuck waiting at
ntdll.dll!NtWaitForDebugEvent+0xa
XEmacs is splitting the cpu between two threads:
wow64cpu.dll!CpuSimulate+0x16e
ntdll.dll!NtQueryInformationThread+0x12
**cygwin1.dll!lfind+0x44ab**
cygwin1.dll!getenv+0x48d2
cygwin1.dll!sigfillset+0x2df7
cygwin1.dll!setprogname+0x1cc5
cygwin1.dll!setprogname+0x224f
cygwin1.dll!setprogname+0x2df1
and
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x56b
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlIsDosDeviceName_U+0x24c87
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!ZwDelayExecution+0x15
**cygwin1.dll!lfind+0x44d9**
xemacs-21.5-b32.exe+0x201cf6
xemacs-21.5-b32.exe+0x7c6f9
xemacs-21.5-b32.exe+0x1e96ba
xemacs-21.5-b32.exe+0x2302de
xemacs-21.5-b32.exe+0x230319
WINMM.DLL!DriverCallback+0x4e
WINMM.DLL!timeEndPeriod+0x54a
WINMM.DLL!timeEndPeriod+0x449
cygwin1.dll!setprogname+0x319d
The ** lines show the up (from the bottom) through which the stack is
stable, the loop is somewhere above that.
Any ideas? Suggestions as to how to debug this?
Oh yes, the xemacs itself is in one of those semantic idle-timeout analysis
phases: the message line says
LALR/auth_ldap.inc: [####....] ... done
which is some miscellanious cousin in the file-system of the PHP code
whose buffer is showing at the moment.
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht(a)inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
XEmacs Packages have been pre-released (2012-11-21-09)
12 years
Norbert Koch
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
edit-utils-2.48-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
Sun-1.17-pkg.tar.gz upstream version: none
cc-mode-1.57-pkg.tar.gz upstream version: 5.32.2
ede-1.04-pkg.tar.gz upstream version: 1.0pre4
eudc-1.41-pkg.tar.gz upstream version: 1.32
games-1.21-pkg.tar.gz upstream version: 2.00
gnus-1.95-pkg.tar.gz upstream version: 5.10.10
hyperbole-1.18-pkg.tar.gz upstream version: 5.0.3
leim-1.33-pkg.tar.gz upstream version: none
mh-e-1.33-pkg.tar.gz upstream version: 7.4.2
mmm-mode-1.06-pkg.tar.gz upstream version: 0.4.8
net-utils-1.57-pkg.tar.gz upstream version: N/A
pgg-1.08-pkg.tar.gz upstream version: 0.1
prog-modes-2.27-pkg.tar.gz upstream version: none
ruby-modes-1.05-pkg.tar.gz upstream version: 1.8.7
speedbar-1.30-pkg.tar.gz upstream version: 1.0pre4
text-modes-2.01-pkg.tar.gz upstream version: none
w3-1.38-pkg.tar.gz upstream version: 4.0pre47
x-symbol-1.13-pkg.tar.gz upstream version: 4.5.1
xemacs-base-2.32-pkg.tar.gz upstream version: none
xemacs-devel-1.82-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/edit-utils/ChangeLog -------
2012-11-21 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 2.48 released.
2012-11-20 Vin Shelton <acs(a)xemacs.org>
* buffer-colors.el: Add autoload cookie to bc-buffer-colors-enabled-p.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFQrI/m7yJLt8ORD7cRAltoAJ9abZhO5CahL/kHOR13cNAXha5AjgCfdOzz
5MfWAsp66lQp4QL1EP0K/5o=
=/12/
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
edit-utils change breaks 21.4
12 years
Vin Shelton
Vin Shelton
Hello,
On Mon, Nov 19, 2012 at 12:55 AM, Bitbucket
<commits-noreply(a)bitbucket.org> wrote:
> https://bitbucket.org/xemacs/edit-utils/changeset/b1f2bf6133c5/
> changeset: b1f2bf6133c5
> user: skm
> date: 2012-11-19 06:51:50
> summary: fixed autoloads in buffer-colors.el
> affected #: 2 files
>
> diff -r ca2abadaf7dba3d3a5c7849fe85b5cc041bccfb1 -r b1f2bf6133c5f2607058e88d1f9e385ce87e8415 ChangeLog
> --- a/ChangeLog
> +++ b/ChangeLog
> ＠＠ -1,3 +1,11 ＠＠
> +2012-11-19 Steve Mitchell <smitchel(a)bnin.net>
> + Byrel Mitchell <byrel.mitchell(a)gmail.com>
> +
> + * buffer-colors.el : re-added autoloads with
> + checks for behavior support.
> + uses variables if behavior
> + support not available.
> +
Unfortunately, I rebuilt all my packages and now I'm getting the
following error message printed on stdout when starting 21.4:
Symbol's value as variable is void: bc-buffer-colors-enabled-p
XEmacs then terminates. Starting XEmacs with -debug-init yields no
insight and starting with -vanilla similarly yields no joy. XEmacs
-no-autoloads does allow XEmacs to start up, but, as you'd expect,
it's severely crippled.
If anyone wants to fix this before I can track it down, please have at it.
Thanks,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 1 comments
Summary of XEmacs Issue Tracking System Issues
12 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2012-11-13 - 2012-11-20)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
555 open ( +2) / 290 closed ( +0) / 845 total ( +2)
Open issues with patches: 13
Average duration of open issues: 1283 days.
Median duration of open issues: 1362 days.
Open Issues Breakdown
new 228 ( +2)
deferred 6 ( +0)
napping 3 ( +0)
verified 56 ( +0)
assigned 153 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 18 ( +0)
Issues Created Or Reopened (2)
______________________________
Please package "Evil", a Vim-emulation layer 2012-11-15
http://tracker.xemacs.org/XEmacs/its/issue846 created jasonspiro
6 lines duplicated at end of web page 2012-11-17
http://tracker.xemacs.org/XEmacs/its/issue847 created skm
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
XEmacs Packages have been pre-released (2012-11-19-09)
12 years
Norbert Koch
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
edit-utils-2.47-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
Sun-1.17-pkg.tar.gz upstream version: none
cc-mode-1.57-pkg.tar.gz upstream version: 5.32.2
ede-1.04-pkg.tar.gz upstream version: 1.0pre4
eudc-1.41-pkg.tar.gz upstream version: 1.32
games-1.21-pkg.tar.gz upstream version: 2.00
gnus-1.95-pkg.tar.gz upstream version: 5.10.10
hyperbole-1.18-pkg.tar.gz upstream version: 5.0.3
leim-1.33-pkg.tar.gz upstream version: none
mh-e-1.33-pkg.tar.gz upstream version: 7.4.2
mmm-mode-1.06-pkg.tar.gz upstream version: 0.4.8
net-utils-1.57-pkg.tar.gz upstream version: N/A
pgg-1.08-pkg.tar.gz upstream version: 0.1
prog-modes-2.27-pkg.tar.gz upstream version: none
ruby-modes-1.05-pkg.tar.gz upstream version: 1.8.7
speedbar-1.30-pkg.tar.gz upstream version: 1.0pre4
text-modes-2.01-pkg.tar.gz upstream version: none
w3-1.38-pkg.tar.gz upstream version: 4.0pre47
x-symbol-1.13-pkg.tar.gz upstream version: 4.5.1
xemacs-base-2.32-pkg.tar.gz upstream version: none
xemacs-devel-1.82-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/edit-utils/ChangeLog -------
2012-11-19 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 2.47 released.
2012-11-19 Steve Mitchell <smitchel(a)bnin.net>
Byrel Mitchell <byrel.mitchell(a)gmail.com>
* buffer-colors.el : re-added autoloads with
checks for behavior support.
uses variables if behavior
support not available.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFQqevJ7yJLt8ORD7cRAlBgAJ4xZb9Fa6rkWoVj1fjZYrYWui2lYgCfa+WB
Zt2LlOYDFRVNywJait1YX4o=
=tpf0
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
how to modify the modline (to much information)
12 years
Uwe Brauer
Uwe Brauer
Hello
The modline of a elisp file in my configuration looks like:
UTF8--*-L5716 C14 70% xemacs_init.el (.../oub/xemacs/init) Wed Nov 14 11:27 mailsym (Emacs-Lisp....
Where the last entry starting with the parenthesis contains
the mayor mode and all the minor mode.
Unfortunately on my 12 inch screen I cannot see all the
minor modes. On the other hand, at the top of my window
frame sits a string indication the file I am using, that is
why I consider the information
UTF8--*-L5716 C14 70% xemacs_init.el (.../oub/xemacs/init) Wed Nov 14 11:27 mailsym (Emacs-Lisp....
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Redundant. How can I configure the modeline such that the
file and directory information does not show up and I
hopefully can see all my minor modes?
Thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 2 comments
c-basic-common-init
12 years
jeff-xemacs＠delphioutpost.com
jeff-xemacs＠delphioutpost.com
I've been having trouble with cc based modes for the past year.
After I open a .cc file then every other mode becomes infected with
c-before-change and c-after-change hooks.
c-basic-common-init does the following.
(or (memq 'add-hook-local c-emacs-features)
(make-local-hook 'before-change-functions))
...
(or (memq 'add-hook-local c-emacs-features)
(make-local-hook 'after-change-functions))
So if add-local-hook exists as a feature then we don't call it?
Shouldn't that 'or' be an 'and' or 'if'?
I'm on 21.4.22, but I sort of doubt that matters.
-jeff
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 6 participants
- 12 comments
Re: XEmacs-Beta Digest, Vol 74, Issue 9
12 years
steven Mitchell
steven Mitchell
>>>>> "steven" == steven Mitchell<smitchel(a)bnin.net> writes:
steven> Stephen,
steven> You mentioned you would be interested in small Install How-To's,
steven> So I am offering one based on my recent install.
steven> I'm sure there are errors and misspellings, feel free to correct
steven> or ask me to correct. Same to anyone else.
steven> User-Contributed Installation How-To:
steven> xemacs-21.5.32 on Slackware64 14.0
steven> 11/8/2012
steven> user: Steven Mitchell
steven> These are the 17 steps taken to install xemacs-21.5.32.tar.gz
steven> for all users, on a slackware64 14.0 installation:
Ray> 17 steps seems overly complicated.
A lot of this depends on which operating system you are installing on.
My wife installed on a win7 machine next to me, and downloaded 1 file,
ran it, chose packages on the menu, and it installed and she was dome.
So for that case, 1 file, and you are through! definitely less complicated.
Keep in mind the install-case I am trying to document is for Skackware64 14.0
and not every other case. The INSTALL file Stephen pointed out to me gave
general directions suitable for lots of install-cases.
Which steps do you think can be eliminated?
steven> 2. as root, copy the file xemacs-21.5.32.tar.gz from where ever
steven> you downloaded it, to /usr/src with a command like this:
steven> cp/home/steve/Downloads/xemacs-21.5.32.tar.gz /usr/src/
steven> verify: ls /usr/src
steven> and look to see if the file you copied is there.
steven> If your distribution of linux doesn't have a /usr/src directory,
steven> create it with this command before copying the above file to it:
steven> mkdir -p /usr/src
Ray> I never build xemacs as root and instead just build it as myself. I
Ray> used to build and install on a server for lots of people to use. This was
Ray> never a problem, as long as I remembered to make the directories
Ray> readable/searchable.
I think a couple of steps do need to be root, like make and make install.
The rest of the steps don't need to be done as root as far as I know.
This may be some fuzz in my directions as I had them create a directory
and was not clear in my own mind if it would be created as root w/root
permissions, so for the copying, I said to be root, though that is not
strictly needed, if you have the directory permissions set accordingly.
Can you tell me 2 things, if you remember them:
Which directories did you make readable/searchable?
How did you make them readable/searchable? Was it just using chmod?
And thirdly, after what step did you make them readable/searchable?
steven> 6. Choosing command line options for ./configure.
steven> There are many command line options you can set. Almost everyone
steven> will have
steven> at least some options to specify and almost nobody will be able to
steven> install
steven> XEmacs without specifying some options.
Ray> Isn't this supposed to work without options? Granted the default
Ray> installation directory is probably wrong, but xemacs should build and
Ray> work. Nowadays, all I specify is --prefix, --with-mule, and
Ray> --with-xft, and the latter two are only because I want mule and xft
Ray> support.
I've tried just running ./configure with no options specified 2 times, once with
21.5.29 and once with an older version, maybe 21.5.24?, and both times I got an
installation that did not work right. I'd have to do it again to report the exact
problems I got. I can do that if someone truly wants to know, but in my experience
I have not been successful in just running ./configure with no options at all
on a slackware linux system.
I documented the exact external libraries I wanted to use in my ./configure line,
but since noticed that a couple of the ones I specified were actually defaults
and I could have left them off my ./configure line.
steven> 9. To bootstrap the packaging system, download 2 files:
Ray> I also never go hunting around for the packages and just grab the
Ray> xemacs and mule sumo tarballs. If you're new to xemacs, this is much
Ray> easier.
I read on the XEmacs web site (I think that was where it was) that the sumo
tarballs were not going to be supported on all platforms that you can install
XEmacs on. What I don't want to have happen is the new-installer get to this
point and look for a suitable tarball and be frustrated when he cannot find it.
It could be that the info on the web site is out of date,
And tarballs are available for all systems now, in both mule and non-mule flavors.
Can anyone tell me for sure if tarballs are currently, and will continue to be,
available for all platforms and mule/non-mule versions of XEmacs?
Another point about choosing to install the tarballs, is that assumes you want
every package installed. I typically don't install every package possible.
I never use any form of IRC and don't access email from XEmacs so don't install
those packages. Despite living in Germany a few years as a child, I do
everything in the English language and cannot read any other language, so don't
see the use of having mule installed. Not promoting English over any other
language, just saying it does no good for *me* to have it installed. So I go non-mule.
Make a case that mule is better for me to have, and I will probably install it.
I can modify the instructions to show how to use the mule or non-mule sumo
tarballs, then people could choose to do it that way if they want to.
Ray, can you give me exact directions to install the sumo tarballs?
exact commands and paths you used?
where are sumo-tarballs located?
If it has been a while, can you give me approximate commands and I will reinstall
to try it out.
Thanks,
Steven Mitchell
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 2 comments
Summary of XEmacs Issue Tracking System Issues
12 years
XEmacs Issue Tracking System
XEmacs Issue Tracking System
ACTIVITY SUMMARY (2012-11-06 - 2012-11-13)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
553 open ( +0) / 290 closed ( +0) / 843 total ( +0)
Open issues with patches: 13
Average duration of open issues: 1281 days.
Median duration of open issues: 1357 days.
Open Issues Breakdown
new 226 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 56 ( +0)
assigned 153 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 18 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: User submitted Install How To
12 years
steven Mitchell
steven Mitchell
Stephen,
You mentioned you would be interested in small Install How-To's,
So I am offering one based on my recent install.
I'm sure there are errors and misspellings, feel free to correct
or ask me to correct. Same to anyone else.
User-Contributed Installation How-To:
xemacs-21.5.32 on Slackware64 14.0
11/8/2012
user: Steven Mitchell
These are the 17 steps taken to install xemacs-21.5.32.tar.gz
for all users, on a slackware64 14.0 installation:
1. Download xemacs-21.5.32.tar.gz
Download the md5sum and make sure you have a good download.
verify: md5sum xemacs-21-5-32.tar.gz
md5sum returns a long number.
compare the md5sum you get to the md5sum file available
from the place you downloaded the file. If they are the same,
we have a good downloaded copy.
2. as root, copy the file xemacs-21.5.32.tar.gz from where ever
you downloaded it, to /usr/src with a command like this:
cp /home/steve/Downloads/xemacs-21.5.32.tar.gz /usr/src/
verify: ls /usr/src
and look to see if the file you copied is there.
If your distribution of linux doesn't have a /usr/src directory,
create it with this command before copying the above file to it:
mkdir -p /usr/src
3. cd to /usr/src/ and unpack the the file in /usr/src/ with this command:
gzip -dc xemacs-21.5.32.tar.gz | tar xf -
verify: ls -l
to check that the file did get unpacked.
It should have created a directory: /usr/src/xemacs-21.5.32 with some
subdirectories and files.
4. Read the INSTALL file in the /usr/src/xemacs-21.5.32 directory to
determine if you will want to download and install any of the external
libaries that XEmacs can use. These need to be downloaded and installed
sometime before you run ./configure which checks that these external
libraries are installed.
verify: To tell if you have each of the libraries in the list
installed,
run the command ldconfig to see a list of all libaries installed:
/sbin/ldconfig -p
To search to see if a certain library is installed, run this command:
/sbin/ldconfig -p |grep <full/partial library name, eg. xpm>
Once you have all of the external libraries you think you might want to
have installed, continue to the next step.
5. cd xemacs-21.5.32
verify: pwd
the pwd command prints the working directory, the directory you
are currently "in". Check to see that is it correct.
6. Choosing command line options for ./configure.
There are many command line options you can set. Almost everyone
will have
at least some options to specify and almost nobody will be able to
install
XEmacs without specifying some options.
To get a list of the valid options for configuring xemacs, in the
/usr/src/xemacs-21-5-32 directory, as root, run the command:
./configure -help=short
It is longer than one page, so you might want to run it piped to less:
./configure -help=short | less
Note which options you want for your installation. and keep a list of
the options you need to put on the command line.
It is particularly important to set the paths options to have it
install
correctly.
Here is an example of the ./configure options for my system:
Run ./configure in the /usr/src/xemacs-21-5-32 with these options set:
--prefix=/usr/local (prefix for installation)
--with-widgets=yes (use this if you want buffer tabs)
(if compiled in, can still be turned on/off)
--with-jpeg (to process .jpg's in w3, email, etc)
--with-xpm (use the .xpm graphics file format)
--with-png (use the .png graphics file format)
--with-mule=no (no=w/o international character support)
(with-mule = with international character
support)
So my command line for ./configure looks like this (all on one line):
bash-4.1# ./configure --prefix=/usr/local --with-widgets=yes
--with-jpeg --with-xpm --with-png --with-mule=no
Note paths do not have to be quoted. If multiple locations are
specified
for any of the paths, the syntax is a list with each element in quotes:
( "/path1" "/path2" "/path3")
Assemble a command line with ./configure and all options you choose for
your installation and run it.
verify: if ./configure ends with no errors, go to the next step.
7. While still in the directory /usr/src/xemacs-21-5-32, run the command:
make
verify: When make ends, fix any errors till it "makes" without errors,
then continue.
At this point it is possible to try-out the program without installing
the executable and other files to where they go once installed.
To do so, run this command from within the /usr/src directory:
./src/xemacs
8. To finish the install, putting all the files where they go in your
Linux system, run the command:
make install
(must be root, and still in the directory /usr/src/xemacs-21-5-32)
verify: to be sure you are root, run the command:
whoami
Which will print your user name.
To be sure you are in the right directory, run
pwd
Which will print the current dirctory.
If there are no errors when "make install" is finished, then continue.
------------------------------------------------------------------------------
---------- That is the end of installing the main xemacs program
-------------
------------ To make it fully usable, we need some packages
------------------
----- Next step is bootstrapping the packaging system, Which consists
of------
-------- downloading & manually installing 2 packages, then using the
--------
--------- package manager to download the rest of the xemacs
packages---------
------------------------------------------------------------------------------
9. To bootstrap the packaging system, download 2 files:
efs-1.34-pkg.tar.gz
xemacs-base-2.27-pkg.tar.gz
One place to get them is the xemacs ftp site:
http://ftp.xemacs.org/pub/xemacs/packages/
verify: run
md5sum <archive name>
to generate the md5sum for your downloaded files. Compare these
to the
md5sums in README.MD5 file in the ftp directory they were
downloaded from.
10. Create an xemacs package directory, as root:
mkdir /PREFIX/share/xemacs/xemacs-packages
PREFIX is the prefix option you specified on the ./configure
command above.
Using the --prefix in my example above, this now expands to this
command:
mkdir /usr/local/share/xemacs/xemacs-packages
Execute this command, substituting what *you* specified for PREFIX.
We will refer to this PREFIX in the following commands as well.
verify: use ls -l /PREFIX/share/xemacs/ to see that the directory
is there.
Note: These directions are for XEmacs 21.5 or later, the install
path was
slightly different for XEmacs before 21.5:
before 21.5: install path was /PREFIX/lib/xemacs/
21.5 and after: install path was /PREFIX/share/xemacs/
11. As root, copy these two files from where you downloaded them to the
/usr/src
directory:
cp <your-download-path>/efs-1.34-pkg.tar.gz /usr/src
cp <your-download-path>/xemacs-base-2.27-pkg.tar.gz /usr/src
verify: ls -l in /usr/src to check if the files are copied right.
Note: it is not strictly necessary to put these files in
/usr/src/--they could be
unpacked and installed from most any directory, but for the sake of
giving
clear directions with the least amount of confusion, I am treating
this as a step in
the directions.
12. Change to the newly created directory for packages:
cd /PREFIX/share/xemacs/xemacs-packages
verify: execute pwd to see that you are in the right directory.
13. In the new xemacs-packages directory, as root, unpack the two files
we just copied
tar -xzvvf /usr/src/efs-1.34-pkg.tar.gz
tar -xzvvf /usr/src/xemacs-base-2.27-pkg.tar.gz
verify: ls -l should show that there are now directories named
etc, info, lisp, man, and pkginfo
14. start xemacs by typing xemacs in a root terminal:
xemacs
verify: If you had a version of xemacs installed before, xemacs
might find
and try to load your old .init.el, and if any packages were
specified in
your previous .xemacs, you may get errors.
OK to ignore them for the moment and continue setting up the
package manager.
If the errors are severe and prevent xemacs from starting up, try
starting
xemacs with this command:
xemacs -vanilla
which loads XEmacs without configuration files.
15. First of three steps in setting up the package manager is to specify
a site
to download packages from:
on the menu, choose [tools][packages][set download site][official
releases]
then choose a download site from the list given. The menu allows
there to
be 2 download sites to be specified (numbered 1 and 2 in the menu).
Both can be set now, but it is only necessary to set 1 of them (the
first one)
at this time. The [pre-releases] and [site releases] menu items do
not
need set at this time.
16. Second of three steps is to download a list of available packages.
on the menu, choose [tools][packages][update package list]
this will go online and find the current xemacs packages list.
One error that may come up at this step is the minibuffer may display:
Symbol's value as variable is void: allow-remote-paths
The most likely problem to cause this error is xemacs is not
finding the 2
packages (efs and xemacs-base) that we downloaded and installed in
previous
steps.
Check carefully the ./configure options that you selected before
compiling
the xemacs source code. particularly the options having to do with
paths.
You may have to go back to the /usr/src/ directory and assemble a new
./configure command line, and start the install process over from
that point,
since the paths for your installation are set by running
./configure and
are compiled into your xemacs executable.
17. Third step of three steps is to choose and install the rest of the
packages
that you want to use. On the menu, choose [tools][packages][List
And Install]
this will start the package manager and present you with a list of
packages
that are available. For directions, go to the bottom of the page
to see a
list of keystrokes to mark, unmark, uninstall, and install packages.
Choose packages with the plus key and then x to install the all the
selected
packages.
verify: when the package installing is done, exit xemacs and start
it again
and repeat step 17 to see which packages it now shows as installed.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 9 comments