1 |
Karl-Johan 'Creideiki' Karlsson wrote: |
2 |
> On Thursday 24 November 2005 19.23, Stephen P. Becker wrote: |
3 |
>> If you aren't already, try using binutils-2.16.1. |
4 |
> |
5 |
> Now that's interesting. I built the system using binutils-2.16.90.0.3 (~mips |
6 |
> at the time), then downgraded to 2.16.1 to solve bug #112809. Now, Emacs |
7 |
> won't even emerge - the temacs binary (seems to be a semi-standalone elisp |
8 |
> compiler used to bootstrap Emacs) segfaults immediately upon start, and GDB |
9 |
> only says: |
10 |
> |
11 |
> (gdb) run -batch -l loadup dump |
12 |
> Starting program: /var/tmp/portage/emacs-21.4-r1/work/emacs-21.4/src/temacs |
13 |
> -batch -l loadup dump |
14 |
> Warning: |
15 |
> Cannot insert breakpoint -2. |
16 |
> Error accessing memory address 0x266f3: Input/output error. |
17 |
> |
18 |
> Binutils-2.16.91.0.2 gives the same error, but with 2.16.90.0.3 at least Emacs |
19 |
> builds, even though it doesn't run in X. Perhaps rebuilding the entire system |
20 |
> with 2.16.1 or 2.16.91.0.2 would make Emacs build? |
21 |
|
22 |
This tells me it's some super-funky binutils b0rkage going on. Try |
23 |
binutils-2.16.91.0.3 and 2.16.91.0.4 if you can (they're not keyworded, so |
24 |
you'll have to employ an overlay or the files in /etc/portage to unmask them). |
25 |
I know that 2.16.91.0.3 acts funny on glibc (iirc), but I haven't tested |
26 |
2.16.91.0.4 on anything. |
27 |
|
28 |
That all said, looks like a binutils thing, which are usually tricky to track |
29 |
down. This will probably mean that emacs will remain unkeyworded for mips until |
30 |
the bug is ever found and nailed. |
31 |
|
32 |
|
33 |
--Kumba |
34 |
|
35 |
-- |
36 |
Gentoo/MIPS Team Lead |
37 |
Gentoo Foundation Board of Trustees |
38 |
|
39 |
"Such is oft the course of deeds that move the wheels of the world: small hands |
40 |
do them because they must, while the eyes of the great are elsewhere." --Elrond |
41 |
-- |
42 |
gentoo-mips@g.o mailing list |