Hans Reiser <reiser(a)idiom.com> writes:
If you guys could put the contents of Jan's simple instructions
in
the README, boy, it would be nice....
As I wrote. I don't know why Didier's announcement is not on the ftp
site. Combined with an undermaintained Web site (I am not sure what is
the problem there, but I presume also time constraints) we have a
serious Problem.
It is NOT obvious where sumo goes.
Even after reading README.packages (or the equivalent link on the web
site)? I wrote that README and I am afraid I cannot do better then
that. Please point out how it should be changed.
I did use Sumo. That left me having to download 5 tar balls, and
having no instructions on what goes where (It has no README saying
where it goes),
Please tell me what can be improved on the "The SUMO tarball" section
of README.packages.
> P.S. The package index signing issues is because we fell into a
trap
> set for us set for us by RSA inc, The US government and the designers
> of PGP all working together. This will (hopefully) soon be resolved.
What happened to that signatures index package? Did you guys take it off the site,
or did I just forget where I saw it?
No the problem is that the XEmacs maintainer can currently only use
GnuPG and that doesn't support PGP signatures. Unfortunately signing
with GPG causes PGP 2.6.x to report a "Package signature failed" (or
something like that) which is even worse than the current problem.
gcc -g -O3 -Wall -Wno-switch -Demacs -I../src -DHAVE_CONFIG_H
/usr/src/xemacs-21.1.4/lib-src/make-path.c -o make-path
In file included from /usr/include/bits/errno.h:25,
from /usr/include/errno.h:36,
from /usr/src/xemacs-21.1.4/lib-src/make-path.c:36:
/usr/include/linux/errno.h:4: asm/errno.h: No such file or directory
make[1]: *** [make-path] Error 1
make[1]: Leaving directory `/usr/src/xemacs-21.1.4/lib-src'
make: *** [lib-src] Error 2
Note that the including of asm/errno.h is done by
/usr/include/bits/errno.h which is included by usr/include/errno.h. It
seems to me something is screwed up with your header files.
You really should just install a working set of headers in
/usr/include and forget about the symlink. This creates some hassle in
compiling tightly bound linux tools but it is worth it.
boy, you guys sure ought to clean up a lot of warnings, you know,
just so you'll
notice if there is a warning that is significant....
Using egcs 1.1.2 are you? That compiler is broken with respect to the
warnings. Under Solaris (with CC) and with gcc 2.7.2 or gcc 2.95 there
are close to know warnings.
I didn't get a chance to try out this script Eric sent me, but
thanks for sending the script. Maybe the developers of xemacs might
take a look at it.
I didn't either. But at first glance it looks all-right.
Jan