Release notes -- package update 1998/09/19
27 years
SL Baur
SL Baur
[Important question for the folks working on package installers at the
bottom.]
I've updated all the packages in
ftp://ftp.xemacs.org/pub/xemacs/packages/
A massive SUMO tarball of the staging area after I was done building
(which should now be equivalent to the results obtained installing
everything by hand) is at:
ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-SUMO-1998-09-19.tar.gz
It's probably not runnable without deleting some packages by hand first.
The index file is:
ftp://ftp.xemacs.org/pub/xemacs/packages/package-get-base.el-1998-09-19
The only code updates were
vm-1.11:
Synch with VM 6.62
pgnus-1.01:
Synch with Pterodactyl Gnus 0.31
Everything else is repackaging. A handful of packages had some files
rearranged. mule-base no longer creates two subdirectories in etc/.
rmail, xemacs-base, and viper no longer create subdirectories for
their data files. A handful of packages had their READMEs and other
documentation restored.
The user visible changes are:
No more _pkg.el files. I haven't decided whether this is a good idea
or not. *Not* including them means that the auto-autoloads.el can't
be properly updated and this is probably a bad thing.
Every package includes a manifest file of the form
pkginfo/MANIFEST.$(PACKAGE). This should make a safe package delete
function a slam dunk.
TexInfo sources are now included in subdirectories of a new package
top-level directory called man. There probably ought to be an option
at installation time as to whether they should be installed or not,
since they're not actually needed at run-time.
Build level changes:
The way files are copied to the installation or staging area has been
fixed. There is no much more restricted use of wildcards, and it
should now be possible to safely `make install' into a tree you are
running from. In particular, the copy *.el* is now history.
Packages that are custom-ized are now required to have
GENERATED += custom-load.elc
after they include XEmacs.rules.
For packages with data files that go into etc/, there are two symbols
which must be defined. The symbol `DATA_FILES' should be a list of
files to be copied relative to the package build directory
(eg. comm/footnote, etc.) in exactly the same fashion ELCS works now.
examples:
DATA_FILES = relative/path/to/each/data/file
DATA_FILES = $(wildcard images/*.png)
The symbol DATA_DEST indicates where in etc/ the files are to be
copied to. Typically it should be set to $(PACKAGE), but if files
need to be placed directly in etc/, it can be ".". The installation
directory is built up as `etc/$(DATA_DEST)/'.
The semantics of INFO_FILES has been changed so that it works the same
way `ELCS' and `DATA_FILES' does. Every file listed gets installed
into info/.
For packages with texinfo documentation, there are two new symbols.
`TEXI_FILES', which should be set the same way `ELCS', `DATA_FILES',
and `INFO_FILES' are set and `MANUAL'. Every file listed in
`TEXI_FILES' will be installed into the directory man/$(PACKAGE)/.
The variable `MANUAL' is left as a hook if someone wants to hack
together something to build hardcopy.
example assuming two manuals, `foo' and `bar':
TEXI_FILES = texi/foo.texi texi/bar.texi texi/gpl.texinfo
MANUAL = foo bar
It is important for packages that do not have data files, or texinfo
files to not set these variables (I found one package which did, but I
fixed it).
I'm going to try to create a template package Makefile tonight, and
write some formal documentation on this. With only two primary[1]
exceptions (Gnus[2] and psgml[3]), every package now has a generic
build target.
*Question for the people who have been coding installation clients:*
The `standards-version' has been held at 1.0, but there is enough of
an interface change, particularly the new existence of a MANIFEST file ,
to warrant changing the version number. Will this help out coding?
Basically, you would know that any package with standards-version 1.0
doesn't have delete information, and anything higher means it does.
Footnotes:
[1] As opposed to the three packages which contain no installable
lisp and need some handholding because there is no non-source install
target.
[2] Multiple etc/ directories aren't handled automatically.
[3] 2nd level subdirectories in etc/ are now not handled automatically.
- 2 participants
- 1 comments
[Success] XEmacs 21.0 "Norwegian", sparc-sun-solaris2.5.1
27 years
Adrian Aichner
Adrian Aichner
--Multipart_Sun_Sep_20_17:32:38_1998-1
Content-Type: text/plain; charset=US-ASCII
In order test test Steven's SUMO tarball
ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-SUMO-1998-09-19.tar.gz
I re-ran configure with a
modified setting for --package-path, which I have normally set to
/export/home/tmp/packages-21.0 (I forgot to change --infopath,
though).
I ran make all (without running make distclean before-hand).
He is the build-report. Steven might be intersted in all the shadow
warnings I get after using SUMO out-of-the-box.
Although
(locate-library "gnus")
leads
"/export/home/tmp/sumo-21.0/lisp/gnus/gnus.elc"
and most, if not all, of
/export/home/tmp/sumo-21.0/lisp/gnus/*
hides
/export/home/tmp/sumo-21.0/lisp/pgnus/*
I seem to run with
gnus-version
"Pterodactyl Gnus v0.31"
Does this make sense?
I just found both
/export/home/tmp/sumo-21.0/lisp/gnus/gnus.el
and
/export/home/tmp/sumo-21.0/lisp/pgnus/gnus.el
to have
(defconst gnus-version-number "0.31"
"Version number for this version of Gnus.")
(defconst gnus-version (format "Pterodactyl Gnus v%s" gnus-version-number)
"Version string for this version of Gnus.")
although md5sums are different:
985258ceeebb62383b6f85e13990f6a6 pgnus
59adca2a9a43367b18c0cb9834575d05 gnus
Is this how it was intended?
Best regards,
Adrian
> XEmacs Build Report as generated
> by build-report-version $Revision: 1.45 $ follows:
> Contents of /export/home/tmp/CVSroot/xemacs-20/Installation:
> (Output from most recent run of ./configure)
--Multipart_Sun_Sep_20_17:32:38_1998-1
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: attachment; filename="Installation"
Content-Transfer-Encoding: 7bit
uname -a: SunOS tomorrow 5.5.1 Generic sun4u sparc SUNW,Ultra-1
configure '--package-path=/export/home/tmp/sumo-21.0/' '--rel-alloc' '--debug' '--error-checking=no' '--no-doc-file=no' '--use-union-type' '--with-mule' '--with-pop' '--with-site-lisp' '--infopath=/export/home/tmp/CVSroot/xemacs-20/info/:/export/home/tmp/packages-21.0/info:/opt/gnu/info:/usr/local/info/' '--compiler=cc' '--cflags=-g -xO4' '--site-prefixes=/usr/local/' '--gung-ho'
XEmacs 21.0 "Norwegian" configured for `sparc-sun-solaris2.5.1'.
Where should the build process find the source code? /export/home/tmp/CVSroot/xemacs-20
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/sol2.h' and `m/sparc.h'
What compiler should XEmacs be built with? cc -g -xO4
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/openwin/include
Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib
Additional prefixes: /usr/local/
Runtime library search path: /usr/local//lib:/usr/dt/lib:/usr/openwin/lib:/opt/SUNWdt/lib
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in support for X-Face message headers.
Compiling in native sound support.
Compiling in support for GNU DBM.
Compiling in Mule (multi-lingual) support.
Compiling in XIM (X11R5+ I18N input method) support.
Using Motif to provide XIM support.
Compiling in support for CDE.
Compiling in support for ToolTalk.
Compiling in EXPERIMENTAL support for Drag'n'Drop ( 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 POP for mail access
Using the union type for Lisp_Objects.
Using Lisp_Objects with minimal tagbits.
Using indexed lrecord implementation.
Compiling in extra code for debugging.
Compiling in code for checking XEmacs memory usage.
> Contents of //export/home/tmp/CVSroot/xemacs-20/xemacs-20-make-all-for-sumo.err
> keeping lines matching
> "^--\[\[\|\]\]$\|make\[\|errors?.*\(
\s-+.+\)*\|warnings?.*\(
\s-+.+\)*\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compilation\|^Resetting\s-\|not\s-+found\|^Note:\|^While\s-+compiling.*\(
\s-+.+\)*"
> and then deleting lines matching
> "confl.*with.*auto-inlining"
--Multipart_Sun_Sep_20_17:32:38_1998-1
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: attachment ; filename="xemacs-20-make-all-for-sumo.err"
Content-Transfer-Encoding: 7bit
Compilation started at Sun Sep 20 11:21:36 1998
"/export/home/tmp/CVSroot/xemacs-20/lib-src/gnuserv.c", line 912: warning: statement not reached
"emacs.c", line 2523: warning: argument #1 is incompatible with prototype:
prototype: pointer to const char : "/usr/include/string.h", line 58
argument : pointer to uchar
"mule-coding.c", line 4808: warning: empty translation unit
Purespace usage: 106620 of 946844 (11% -- 820k wasted).
Purespace usage: 901208 of 946844 (95% -- 44k wasted).
XEmacs: Pure size adjusted, Don't Panic! I will restart the `make'
*** Error code 1 (ignored)
Purespace usage: 901208 of 901208 (100%).
/export/home/tmp/sumo-21.0/lisp/leim/greek hides /export/home/tmp/sumo-21.0/lisp/mule-base/greek
/export/home/tmp/sumo-21.0/lisp/leim/cyrillic hides /export/home/tmp/sumo-21.0/lisp/mule-base/cyrillic
/export/home/tmp/sumo-21.0/lisp/gnus/rfc2231 hides /export/home/tmp/sumo-21.0/lisp/pgnus/rfc2231
/export/home/tmp/sumo-21.0/lisp/gnus/mail-parse hides /export/home/tmp/sumo-21.0/lisp/pgnus/mail-parse
/export/home/tmp/sumo-21.0/lisp/gnus/mm-view hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm-view
/export/home/tmp/sumo-21.0/lisp/gnus/mailcap hides /export/home/tmp/sumo-21.0/lisp/pgnus/mailcap
/export/home/tmp/sumo-21.0/lisp/gnus/time-date hides /export/home/tmp/sumo-21.0/lisp/pgnus/time-date
/export/home/tmp/sumo-21.0/lisp/gnus/drums hides /export/home/tmp/sumo-21.0/lisp/pgnus/drums
/export/home/tmp/sumo-21.0/lisp/gnus/date hides /export/home/tmp/sumo-21.0/lisp/pgnus/date
/export/home/tmp/sumo-21.0/lisp/gnus/mm-bodies hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm-bodies
/export/home/tmp/sumo-21.0/lisp/gnus/rfc2047 hides /export/home/tmp/sumo-21.0/lisp/pgnus/rfc2047
/export/home/tmp/sumo-21.0/lisp/gnus/rfc1522 hides /export/home/tmp/sumo-21.0/lisp/pgnus/rfc1522
/export/home/tmp/sumo-21.0/lisp/gnus/qp hides /export/home/tmp/sumo-21.0/lisp/pgnus/qp
/export/home/tmp/sumo-21.0/lisp/gnus/nnweb hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnweb
/export/home/tmp/sumo-21.0/lisp/gnus/nnlistserv hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnlistserv
/export/home/tmp/sumo-21.0/lisp/gnus/mm hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm
/export/home/tmp/sumo-21.0/lisp/gnus/mm-util hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm-util
/export/home/tmp/sumo-21.0/lisp/gnus/mm-encode hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm-encode
/export/home/tmp/sumo-21.0/lisp/gnus/mm-decode hides /export/home/tmp/sumo-21.0/lisp/pgnus/mm-decode
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-mh hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-mh
/export/home/tmp/sumo-21.0/lisp/gnus/base64 hides /export/home/tmp/sumo-21.0/lisp/pgnus/base64
/export/home/tmp/sumo-21.0/lisp/gnus/smiley hides /export/home/tmp/sumo-21.0/lisp/pgnus/smiley
/export/home/tmp/sumo-21.0/lisp/gnus/score-mode hides /export/home/tmp/sumo-21.0/lisp/pgnus/score-mode
/export/home/tmp/sumo-21.0/lisp/gnus/pop3 hides /export/home/tmp/sumo-21.0/lisp/pgnus/pop3
/export/home/tmp/sumo-21.0/lisp/gnus/parse-time hides /export/home/tmp/sumo-21.0/lisp/pgnus/parse-time
/export/home/tmp/sumo-21.0/lisp/gnus/nnvirtual hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnvirtual
/export/home/tmp/sumo-21.0/lisp/gnus/nntp hides /export/home/tmp/sumo-21.0/lisp/pgnus/nntp
/export/home/tmp/sumo-21.0/lisp/gnus/nnspool hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnspool
/export/home/tmp/sumo-21.0/lisp/gnus/nnsoup hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnsoup
/export/home/tmp/sumo-21.0/lisp/gnus/nnoo hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnoo
/export/home/tmp/sumo-21.0/lisp/gnus/nnml hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnml
/export/home/tmp/sumo-21.0/lisp/gnus/nnmh hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnmh
/export/home/tmp/sumo-21.0/lisp/gnus/nnmbox hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnmbox
/export/home/tmp/sumo-21.0/lisp/gnus/nnmail hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnmail
/export/home/tmp/sumo-21.0/lisp/gnus/nnkiboze hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnkiboze
/export/home/tmp/sumo-21.0/lisp/gnus/nnheaderxm hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnheaderxm
/export/home/tmp/sumo-21.0/lisp/gnus/nnheader hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnheader
/export/home/tmp/sumo-21.0/lisp/gnus/nngateway hides /export/home/tmp/sumo-21.0/lisp/pgnus/nngateway
/export/home/tmp/sumo-21.0/lisp/gnus/nnfolder hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnfolder
/export/home/tmp/sumo-21.0/lisp/gnus/nneething hides /export/home/tmp/sumo-21.0/lisp/pgnus/nneething
/export/home/tmp/sumo-21.0/lisp/gnus/nndraft hides /export/home/tmp/sumo-21.0/lisp/pgnus/nndraft
/export/home/tmp/sumo-21.0/lisp/gnus/nndoc hides /export/home/tmp/sumo-21.0/lisp/pgnus/nndoc
/export/home/tmp/sumo-21.0/lisp/gnus/nndir hides /export/home/tmp/sumo-21.0/lisp/pgnus/nndir
/export/home/tmp/sumo-21.0/lisp/gnus/nndb hides /export/home/tmp/sumo-21.0/lisp/pgnus/nndb
/export/home/tmp/sumo-21.0/lisp/gnus/nnbabyl hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnbabyl
/export/home/tmp/sumo-21.0/lisp/gnus/nnagent hides /export/home/tmp/sumo-21.0/lisp/pgnus/nnagent
/export/home/tmp/sumo-21.0/lisp/gnus/messcompat hides /export/home/tmp/sumo-21.0/lisp/pgnus/messcompat
/export/home/tmp/sumo-21.0/lisp/gnus/messagexmas hides /export/home/tmp/sumo-21.0/lisp/pgnus/messagexmas
/export/home/tmp/sumo-21.0/lisp/gnus/message hides /export/home/tmp/sumo-21.0/lisp/pgnus/message
/export/home/tmp/sumo-21.0/lisp/gnus/mailheader hides /export/home/tmp/sumo-21.0/lisp/pgnus/mailheader
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-xmas hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-xmas
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-win hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-win
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-vm hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-vm
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-uu hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-uu
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-util hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-util
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-undo hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-undo
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-topic hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-topic
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-sum hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-sum
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-start hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-start
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-srvr hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-srvr
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-spec hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-spec
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-soup hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-soup
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-setup hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-setup
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-score hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-score
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-salt hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-salt
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-range hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-range
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-picon hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-picon
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-nocem hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-nocem
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-msg hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-msg
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-move hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-move
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-logic hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-logic
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-load hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-load
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-kill hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-kill
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-int hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-int
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-group hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-group
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-gl hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-gl
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-ems hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-ems
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-eform hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-eform
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-dup hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-dup
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-draft hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-draft
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-demon hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-demon
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-cus hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-cus
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-cite hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-cite
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-cache hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-cache
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-bcklg hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-bcklg
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-audio hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-audio
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-async hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-async
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-art hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-art
/export/home/tmp/sumo-21.0/lisp/gnus/gnus-agent hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus-agent
/export/home/tmp/sumo-21.0/lisp/gnus/earcon hides /export/home/tmp/sumo-21.0/lisp/pgnus/earcon
/export/home/tmp/sumo-21.0/lisp/gnus/gnus hides /export/home/tmp/sumo-21.0/lisp/pgnus/gnus
/export/home/tmp/sumo-21.0/lisp/vc/vc hides /export/home/tmp/sumo-21.0/lisp/vc-cc/vc
/export/home/tmp/sumo-21.0/lisp/vc/vc-hooks hides /export/home/tmp/sumo-21.0/lisp/vc-cc/vc-hooks
/export/home/tmp/sumo-21.0/lisp/gnus/mm hides /export/home/tmp/sumo-21.0/lisp/w3/mm
/export/home/tmp/sumo-21.0/lisp/gnus/base64 hides /export/home/tmp/sumo-21.0/lisp/w3/base64
95 Emacs Lisp load-path shadowings were found
While compiling toplevel forms in file /export/home/tmp/CVSroot/xemacs-20/lisp/package-get-base.el:
** assignment to free variable package-get-base
Compilation finished at Sun Sep 20 11:44:53
--
Adrian Aichner
Applications Engineer
Teradyne GmbH
Semiconductor Test Group Telephone +49/89/41861(0)-208
Dingolfinger Strasse 2 Fax +49/89/41861-217
D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com
--Multipart_Sun_Sep_20_17:32:38_1998-1--
- 1 participants
- 0 comments
Re: XEmacs packages poll
27 years
SL Baur
SL Baur
Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org:
> SL Baur <steve(a)xemacs.org> writes:
>> Is there a volunteer to create such a Makefile? You can assume that
>> the template will be passed the names of the manual(s), that there
>> is no need to worry about dependencies of source files (they're
>> really handled in the canonical-for-XEmacs sources), and you can
>> assume GNU Make is being used.
> Is GNU make really needed? Not all of us are running under Linux.
GNU make is very much needed for package building the same as it is
required to build XEmacs with the --srcdir flag. The autoconf idea
is fine. If you can make hardcopy building work without GNU make,
that's fine with me.
As soon as I get finished updating all the Makefiles, there is going
to be an installed directory structure that adds stuff like this:
pkginfo/MANIFEST.gnats
pkginfo/MANIFEST.gnus
pkginfo/MANIFEST.mailcrypt
...
man/gnats/categ.texi
man/gnats/fields.texi
man/gnats/flowchart.eps
...
man/gnus/message.texi
man/gnus/gnus.texi
man/gnus/gnus-faq.texi
man/mailcrypt/mailcrypt.texi
...
in addition to the existing etc/, lisp/, and info/ directories.
Hmm. The package-info file ought to be thrown into pkginfo as well.[1]
That will satisfy the problems caused by sounds-wav/sounds-au/locale
which don't have _pkg.el files because they don't have lisp directories.
Footnotes:
[1] I can't make the build system do that, because of the MD5 checksum,
the package-info file cannot be built until after the tar.gz file is
created.
- 1 participants
- 0 comments
Re: XEmacs dumps core after 'C-h f'.
27 years
Jim Radford
Jim Radford
Dar Efroni <efroni(a)emc.com> writes:
> #4 0xf03d4 in Fskip_syntax_backward (syntax=1976900, lim=2568196,
> buffer=2568196) at search.c:941
This is caused by a bug in gcc (on Solaris). egcs <= 1.03 had this bug,
but it is fixed in egce-1.1b. I think gcc 2.8.x had the bug as well,
but I can't remember.
Steve, I think this should go in the FAQ.
-Jim
- 1 participants
- 0 comments
Re: XEmacs packages poll
27 years
Hrvoje Niksic
Hrvoje Niksic
SL Baur <steve(a)xemacs.org> writes:
> Is there a volunteer to create such a Makefile? You can assume that
> the template will be passed the names of the manual(s), that there
> is no need to worry about dependencies of source files (they're
> really handled in the canonical-for-XEmacs sources), and you can
> assume GNU Make is being used.
Is GNU make really needed? Not all of us are running under Linux.
(or, is it "modified versions of GNU?" *snicker*)
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Reporter: Mr Gandhi, what do you think of Western Civilization?
Gandhi: I think it would be a good idea.
- 1 participants
- 0 comments
Re: XEmacs packages poll
27 years
William M. Perry
William M. Perry
SL Baur <steve(a)xemacs.org> writes:
> We need a delete function for XEmacs packages. I can make binary
> packages include a MANIFEST file that can be used by a lisp-level
> delete function. Where should this MANIFEST file be placed?
>
> a) The top level
> b.1) A subdirectory
> b.2) If yes to b.1, where? My suggestion is `pkginfo/MANIFEST.${PACKAGE}'
> or pkginfo/${PACKAGE}
Subdirectory - pkginfo/MANIFEST.${PACKAGE} looks good.
> I'm in the process of adding texinfo sources to binary package kits. In
> order to facilitate processing by the user, it would be nice to add a
> generic Makefile to create hardcopy. Functionally this can work as a
> template Makefile copied from the toplevel XEmacs package source
> directory into the generated tarball. Is there a volunteer to create
> such a Makefile? You can assume that the template will be passed the
> names of the manual(s), that there is no need to worry about dependencies
> of source files (they're really handled in the canonical-for-XEmacs
> sources), and you can assume GNU Make is being used. Martin first asked
> for this, so he is the obvious primary candidate. Any other takers?
Why not just use autoconf? For the packages as well as the info stuff?
This would remove the need for GNU make, and is similar to how everything
else works.
I've already got all the stuff built for doing various info generating
stuff in autoconf (HTML, DVI, makeinfo, info from Emacs/XEmacs).
It would not be hard to hack something together to deal with all
exisiting subdirectories when doing recursion instead of just having them
in the configure file directly.
People should be able to build packages without external dependencies,
same way they can build XEmacs with non-GNU make and compilers, etc, etc.
I'd like to see them be able to do:
cd /emacs/xemacs/package-source
./configure --with-emacs=/usr/local/bin/xemacs
make
Look familiar? :)
-Bill P.
- 1 participants
- 0 comments
XEmacs packages poll
27 years
SL Baur
SL Baur
We need a delete function for XEmacs packages. I can make binary
packages include a MANIFEST file that can be used by a lisp-level
delete function. Where should this MANIFEST file be placed?
a) The top level
b.1) A subdirectory
b.2) If yes to b.1, where? My suggestion is `pkginfo/MANIFEST.${PACKAGE}'
or pkginfo/${PACKAGE}
I'm in the process of adding texinfo sources to binary package kits.
In order to facilitate processing by the user, it would be nice to
add a generic Makefile to create hardcopy. Functionally this can
work as a template Makefile copied from the toplevel XEmacs package
source directory into the generated tarball. Is there a volunteer to
create such a Makefile? You can assume that the template will be
passed the names of the manual(s), that there is no need to worry
about dependencies of source files (they're really handled in the
canonical-for-XEmacs sources), and you can assume GNU Make is being
used. Martin first asked for this, so he is the obvious primary
candidate. Any other takers?
- 1 participants
- 0 comments
Xemacs vs toolbars
27 years
Manuel.Serrano＠unice.fr
Manuel.Serrano＠unice.fr
Hi to all of you,
first of all, I would like to apologies in advance. This mail reports
problems I have with the XEmacs20.4 (and older) and the Toolbar and
XEmacs and glyph. I think my problems are coming from XEmacs bugs but
it is quiet possible that I have missed many things and thus it is
quiet possible that I be wrong too.
*** 1: I think there is a bug in the design of the toolbar. To me (may be you
will explain to me why I'm wrong), the global X-window size of XEmacs should
be independent of the toolbars. I mean, enabling/disabling the toolbar should
not change the XEmacs X-window size. That's the main problem with the toolbar.
I think XEmacs toolbars should behaves as Netscape toolbars. With Netscape,
when you hide toolbar, the X-Window size does not change. I think, for that's
the good choice. This story of X-window sizes changing with the toolbar,
makes mostly impossible to use different toolbars in different buffers.
It is not possible to have a small toolbar (such as 3 pixels height
toolbar in a buffer) and a large toolbar (such as 30 pixels) in another
buffer because if you do this, your X-window will be reshaped each time
you active one buffer or this other!
*** 2: Because changing the toolbar size, changes the XEmacs X-window size,
one has to write code like:
(defun bee-shrink-frame-for-toolbar (delta)
(let* ((frame (selected-frame))
(fr-height (frame-pixel-height frame)))
(if (< delta 0)
(while (> (- (frame-pixel-height frame) fr-height) delta)
(set-frame-height frame (- (frame-height frame) 1)))
(while (< (- (frame-pixel-height frame) fr-height) delta)
(set-frame-height frame (+ (frame-height frame) 1))))))
This is really a pain (and this is rather incorrect).
*** 3: I have tried to use buffer specific toolbar. It works until toolbar have
different sizes. Try that code:
(let ((old-height (specifier-instance default-toolbar-height))
(new-height 3))
(set-specifier default-toolbar-height 3))
It works fine, it resizes every toolbar sizes.
it should be possible to use:
(let ((old-height (specifier-instance default-toolbar-height))
(new-height 3))
(set-specifier default-toolbar-height 3 (current-buffer)))
or
(let ((old-height (specifier-instance default-toolbar-height))
(new-height 3))
(set-specifier default-toolbar-height 3 (selected-window-buffer)))
This does not work. Why?
*** 4: I have had trouble while printing glyph inside regular text. It took
me some time to figure out that the problem was coming from the pixel
height of the glyph. I have the following code:
(defvar a-glyph
(make-glyph....))
(setq extent (make-extent 1 1 buffer))
(set-extent-face extent 'a-face)
(set-extent-begin-glyph extent a-glyph)
If the glyph's height is bigger than a value that depends on the font pixel
size, the extent won't appear on the screen. The trouble is
that there is no way to discover that something went wrong and that nothing
is printed.
*** 5: I would like to make a suggestion for the coming releases. Would it be
possible to print text with properties inside menus? For instance, I would
like to print in a different colors, the header of a menu and in a different
colors, the items of a submenu.
I hope these remarks will help. I you need more details, I will be happy
to help.
Sincerely,
--Manuel Serrano--
- 1 participants
- 0 comments
XEmacs dumps core after 'C-h f'.
27 years
Dar Efroni
Dar Efroni
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.2 "Aeolus" [Lucid] (sparc-sun-solaris2.6) of Fri Sep 4 1998 on lss8085
configured using `configure --with-gnu-make --dynamic=yes --gung-ho --error-checking=none --site-prefixes=/usr/local/X11R6.4 --site-runtime-libraries=/usr/local/X11R6.4/lib:/usr/dt/lib --package-path=/usr/local/src/packages'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
uname -a: SunOS lss8085 5.6 Generic_105181-03 sun4u sparc SUNW,Ultra-2
./configure '--with-gnu-make' '--dynamic=yes' '--gung-ho' '--error-checking=none' '--site-prefixes=/usr/local/X11R6.4' '--site-runtime-libraries=/usr/local/X11R6.4/lib:/usr/dt/lib' '--package-path=/usr/local/src/packages'
XEmacs 21.2-b1 "Aeolus" configured for `sparc-sun-solaris2.6'.
Where should the build process find the source code? /usr/local/src/xemacs-21.2-b1
What installation prefix should install use? /usr/local
What operating system and machine description files should XEmacs use?
`s/sol2.h' and `m/sparc.h'
What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch
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/openwin/include
Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib
Additional prefixes: /usr/local/X11R6.4
Runtime library search path: /usr/local/X11R6.4/lib:/usr/dt/lib
Compiling in support for XAUTH.
Compiling in support for XPM images.
Compiling in support for GNU DBM.
Compiling in support for CDE.
Compiling in support for ToolTalk.
Compiling in EXPERIMENTAL support for Drag'n'Drop ( 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.
Program terminated with signal 11, Segmentation Fault.
Reading symbols from /usr/dt/lib/libXm.so.3...done.
Reading symbols from /usr/local/X11R6.4/lib/libXpm.so...done.
Reading symbols from /usr/dt/lib/libDtSvc.so.1...done.
Reading symbols from /usr/dt/lib/libtt.so.2...done.
Reading symbols from /usr/local/X11R6.4/lib/libXmu.so.6.0...done.
Reading symbols from /usr/local/X11R6.4/lib/libXt.so.6.0...done.
Reading symbols from /usr/local/X11R6.4/lib/libXext.so.6.4...done.
Reading symbols from /usr/local/X11R6.4/lib/libX11.so.6.1...done.
Reading symbols from /usr/local/X11R6.4/lib/libSM.so.6.0...done.
Reading symbols from /usr/local/X11R6.4/lib/libICE.so.6.3...done.
Reading symbols from /usr/lib/libdl.so.1...done.
Reading symbols from /usr/lib/libkvm.so.1...done.
Reading symbols from /usr/lib/libkstat.so.1...done.
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libm.so.1...done.
Reading symbols from /usr/lib/libsocket.so.1...done.
Reading symbols from /usr/lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libelf.so.1...done.
Reading symbols from /usr/lib/libc.so.1...done.
Reading symbols from /usr/openwin/lib/libXt.so.4...done.
Reading symbols from /usr/openwin/lib/libX11.so.4...done.
Reading symbols from /usr/lib/libmp.so.2...done.
Reading symbols from /usr/openwin/lib/libSM.so.6...done.
Reading symbols from /usr/openwin/lib/libICE.so.6...done.
Reading symbols from /usr/openwin/lib/libXext.so.0...done.
Reading symbols from /usr/platform/SUNW,Ultra-2/lib/libc_psr.so.1...done.
#0 0xef1072e0 in _libc_kill ()
(gdb) where
#0 0xef1072e0 in _libc_kill ()
#1 0x47b14 in fatal_error_signal (sig=11) at emacs.c:262
#2 <signal handler called>
#3 skip_chars (buf=0x53ae00, forwardp=0, syntaxp=1, string=1976918, lim=1)
at buffer.h:643
#4 0xf03d4 in Fskip_syntax_backward (syntax=1976900, lim=2568196,
buffer=2568196) at search.c:941
#5 0x4ca50 in funcall_recording_as (recorded_as=2684988, nargs=1,
args=0xefffe000) at eval.c:3193
#6 0x50ffc in Ffuncall (nargs=2, args=0xefffe000) at eval.c:3238
#7 0x26c44 in Fbyte_code (bytestr=1976684, vector=1976776, maxdepth=2378752)
at bytecode.c:416
#8 0x4c29c in Feval (form=1976660) at eval.c:3063
#9 0x49488 in condition_case_1 (handlers=1976952, bfun=0x4ba10 <Feval>,
barg=1976660, hfun=0x494cc <run_condition_case_handlers>, harg=2568196)
at eval.c:1653
#10 0x49710 in condition_case_3 (bodyform=1976660, var=2568196,
handlers=1976952) at eval.c:1715
#11 0x27104 in Fbyte_code (bytestr=1976596, vector=1976624, maxdepth=2378752)
at bytecode.c:576
#12 0x4df8c in funcall_lambda (fun=1977144, nargs=0, arg_vector=0xefffe658)
at eval.c:3597
#13 0x4d8e0 in apply_lambda (fun=1977144, numargs=0, unevalled_args=2568196)
---Type <return> to continue, or q <return> to quit---
at eval.c:3501
#14 0x4c460 in Feval (form=1977576) at eval.c:3085
#15 0x48990 in FletX (args=1977528) at eval.c:853
#16 0x4bfe8 in Feval (form=1977516) at eval.c:2997
#17 0x28568 in Fcall_interactively (function=3474980, record_flag=2568196,
keys=2568196) at callint.c:339
#18 0x4b220 in Fcommand_execute (cmd=3474980, record=2568196, keys=2568196)
at eval.c:2584
#19 0x749a0 in execute_command_event (command_builder=0x3b3700, event=5642592)
at event-stream.c:4346
#20 0x74ff0 in Fdispatch_event (event=5642592) at event-stream.c:4637
#21 0x2e2f8 in Fcommand_loop_1 () at cmdloop.c:579
#22 0x2e528 in command_loop_1 (dummy=2568196) at cmdloop.c:494
#23 0x49488 in condition_case_1 (handlers=2568308,
bfun=0x2e50c <command_loop_1>, barg=2568196, hfun=0x2e588 <cmd_error>,
harg=2568196) at eval.c:1653
#24 0x2e698 in command_loop_2 (dummy=2568196) at cmdloop.c:256
#25 0x50db0 in internal_catch (tag=2646524, func=0x2e64c <command_loop_2>,
arg=2568196, threw=0x0) at eval.c:1328
#26 0x2de08 in initial_command_loop (load_me=190028) at cmdloop.c:305
#27 0x464e4 in xemacs_21_2_b1_sparc_sun_solaris2_6 (argc=2, argv=0xeffff344,
envp=0xeffff350, restart=0) at emacs.c:1702
#28 0x47cfc in main (argc=0, argv=0xeffff344, envp=0xeffff350) at emacs.c:2119
Recent keystrokes:
M-x button2 button2up BS RET C-x 1 misc-user
Recent messages (most recent first):
Parsing /emc/efroni/.mailrc...
Loading mail-abbrevs...done
Loading mail-abbrevs...
Loading emacsbug...done
Loading emacsbug...
Loading view-less...done
Loading view-less...
No diary entries for Thursday, September 17, 1998
Loading cal-china...done
Loading cal-china...
- 1 participants
- 0 comments
In search for a GOOD package-get-base.el
27 years
Adrian Aichner
Adrian Aichner
Hello All,
I have taken SOME effort to followup on the exchanges about bad
package-get-base.el
I found the one Steven mailed in
> From: SL Baur <steve(a)xemacs.org>
> Subject: Re: Updated 21.x XEmacs lisp packages
> To: xemacs-beta(a)xemacs.org
> Date: 08 Sep 1998 03:48:35 -0700
> Mail-Copies-To: never
> References: <m2lnnvue6e.fsf(a)altair.xemacs.org> <byhfyiew1w.fsf(a)bolzano.math.ethz.ch>
> Message-ID: <m27lzevq0s.fsf(a)altair.xemacs.org>
Even in that one the MD5SUMs are incorrect for at least ispell, gnus,
text-modes, ...
Is there a canonical place yet where to get good versions of
package-get-base.el?
For now I would very much appreciate if someone could mail me her/his
working copy.
Thanks,
Adrian
--
Adrian Aichner
Applications Engineer
Teradyne GmbH
Semiconductor Test Group Telephone +49/89/41861(0)-208
Dingolfinger Strasse 2 Fax +49/89/41861-217
D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com
- 1 participants
- 0 comments