emacs-20.3 unexec problem

emacs-20.3 unexec problem

Post by Douglas G. Hen » Tue, 17 Nov 1998 04:00:00



I've been trying without success to hack the following problem for about a
week:

Compiling emacs 20.3 seems to build temacs fine, runs it, loads a bunch
of list code, dumps (unexecs) to produce an emacs binary. When the
makefile runs the emacs binary:

   ./emacs -q -batch -f list-load-path-shadows

the dumped state information seems to not be loaded. I see:

   Bare impure Emacs (standard Lisp code not loaded)

and it sits there waiting for input. If I send EOF, I can finish the
build and install, but the installed emacs just displays the above
output in the minibuffer and isn't otherwise useful.

Emacs was configure using:

   ./configure --prefix=/pkg/gnu/emacs-20.3

and compiled using "make". CC, CFLAGS, LDFLAGS, LDLIBS and suchlike
were unset during both configuration and make.

I can work around this by aliasing emacs to "emacs -l loadup" but this
is far too slow to be actually useful.

My system:
   Alpha Noname (166MHz, uniprocessor)
   emacs 20.3
   egcs 1.1b (aka egcs-2.91.57 19980901 release)
   binutils 2.9.1.0.15
   glibc-2.0.7pre7
   linux kernel 2.1.123
   ncurses 4.2

_NO_ X windows stuff is installed. (This is a headless machine.)

This is a fairly complete Linux system, and there is not one bit of
code on it (other than MILO) which I did not compile from scratch using
the above tools (including the tools themselves). So, I'm inclined to
think this is a "Doug can't compile emacs right" problem and not a
"Doug doesn't have a sane build environment" problem.

Any solutions, suggestions for experiments to try, comments, whacks
with the Cluebat or questions via email or this 'froup will be
warmly welcomed. In any case, thanks for reading this far.

(Also, I keep hearing people mention a glibc-2.0.7 release, and/or
a glibc-2.1. Anybody have a URL?)

--
Headers munged to avoid email spam. Mail to henke at phoenix dot net.

 
 
 

1. emacs-20.4 and AIX-4.2: some solution

Hi all,

Generally it is a bad habit to answer one's own questions.
This answer is (fortunately only partly) my own answer on
my own question.

Problem was:
Building emacs-20.4 on AIX-4.2.1.0 results in a core-dumping
emacs-dump.

Searching deja.com I came upon a few alike things and tried
the following:

I copied src/unexaix.c of the xemacs-21.1.6 distribution over
the one of emacs-20.4. This did not compile and I still do
not know why........next I edited this unexaix.c such that
it read:
int unexec (new_name, a_name, data_start, bss_start, entry_address)
     char *new_name, *a_name;
     unsigned data_start, bss_start, entry_address;

and not:
int unexec (char *new_name,
        char *a_name,
        uintptr_t data_start,
        uintptr_t bss_start,
        uintptr_t entry_address)

Then it compiled and I get a working emacs.

If anyone knows why this editing was necessary I would be
very curious about it.

--

Mazzel, cheers, bye, tabe, moi, tot ziens, have a nice day,
Koos
__________________________to be Y999T-compliant_____________________

Institute for Theoretical Physics    |  Phone: +31 15 2566804       |
University of Groningen              |  Phone: +31 70 3116092       |
P.O. Box 800                         |  Fax:   +31 70 3112133       |
9700 AV Groningen, The Netherlands.  |  Yell:  Very, Very loud      |
---------------------- use: yyyyyyyyyyyyyyy/mm/dd-------------------

2. ls not working right for anonymous ftp setup?

3. Emacs-20.2 hangs in RedHat 5.0 alpha

4. Cross mounting peripherals via NFS

5. NetBSD 1.5 and Emacs-20.7/20.4

6. anacron runs daily at 4am (cron is not starting it, WHAT IS?)

7. Anyone had success installing emacs-20.3 on AIX 4.3.2 ??

8. Lottery Information

9. problem with emacs unexec and malloc on linux

10. Emacs-20.4 on 3.2

11. trouble installing emacs-20.2 with Caldera linux-base 1.1

12. gnuserv and emacs-20.3

13. Solaris-2.6 Emacs-20 ignores most characters in X11 mode