Bugzilla Bug 174884

Please re-keyword app-editors/emacs-21.4-r12. This was tested for one month in
the Emacs overlay and moved to Portage now.

For reference, the ChangeLog from the overlay is here:
<http://overlays.gentoo.org/proj/emacs/browser/emacs-overlay/app-editors/emacs/ChangeLog?rev=252>

added ~amd64

~ia64 done

Marked ~hppa.

~sparc'd.

Alpha done.

Compilation fails on ppc64, because the resulting emacs does not run:


[...]
 * Recompiling patched lisp files...
make recompile
../src/emacs -batch --no-site-file --multibyte -f
batch-byte-recompile-directory
/var/tmp/paludis/app-editors/emacs-21.4-r12/work/emacs-21.4/lisp
Fatal error (6).make: *** [recompile] Aborted

!!! ERROR in app-editors/emacs-21.4-r12:
!!! In src_compile at line 3842
!!! (no message provided)


# cd /var/tmp/paludis/app-editors/emacs-21.4-r12/work/emacs-21.4/ && gdb
src/emacs
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc64-unknown-linux-gnu"...
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) run
Starting program:
/var/tmp/paludis/app-editors/emacs-21.4-r12/work/emacs-21.4/src/emacs 
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: Breakpoint address adjusted from 0x101c3f60 to 0x1000cc90.

Program received signal SIGABRT, Aborted.
0x000004000098a0e8 in .kill () from /lib/tls/libc.so.6
(gdb) bt
#0  0x000004000098a0e8 in .kill () from /lib/tls/libc.so.6
#1  0x00000000100bb50c in abort () at emacs.c:387
#2  0x000000001011ef1c in wrong_type_argument (predicate=1152921504878995992,
value=8462952429752967021)
    at data.c:117
#3  0x00000000100e1128 in Fget_buffer (name=6) at buffer.c:268
#4  0x00000000100e1e4c in Fget_buffer_create (name=0) at buffer.c:338
#5  0x0000000010027024 in message_dolog (m=0x101a2630 "", nbytes=0, nlflag=1,
multibyte=0) at xdisp.c:5657
#6  0x00000000100bca38 in main (argc=<value optimized out>, argv=0xfffffed6158,
envp=<value optimized out>)
    at emacs.c:1317
(gdb)

(In reply to comment #6)
> Compilation fails on ppc64, because the resulting emacs does not run:

Is this a regression, i.e. does emacs-21.4-r8 compile and run?

(In reply to comment #7)
> Is this a regression, i.e. does emacs-21.4-r8 compile and run?

Now that you say that you remind me of bug #152006. Should I add ~ppc64 back
in? I don't really know..

/me prays that emacs 22.0 will be released soon...

added ~ppc64

Added ~ppc keywords. Apologies for the delay.

Remaining target keywords for emacs-21.4-r12:
~arm ~s390 ~sh ~x86-fbsd

arm: Could you also check if the !arm inverse arch flag for Xaw3d and motif is
still necessary for you?

~arm done, thanks Jokey.

~x86-fbsd done

s390, sh:
In principle, we would even like 21.4-r12 to be marked stable (see bug
#180100), so we can get rid of -r4 and -r8 at some point. (Just mentioning
this; I don't know what are your rules for stabilisation.)

21.4-r12 is vulnerable to security bug #197313. Closing.