List Archive: gentoo-mips
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Karl-Johan 'Creideiki' Karlsson wrote:
> On Thursday 24 November 2005 19.23, Stephen P. Becker wrote:
>> If you aren't already, try using binutils-2.16.1.
> Now that's interesting. I built the system using binutils-184.108.40.206.3 (~mips
> at the time), then downgraded to 2.16.1 to solve bug #112809. Now, Emacs
> won't even emerge - the temacs binary (seems to be a semi-standalone elisp
> compiler used to bootstrap Emacs) segfaults immediately upon start, and GDB
> only says:
> (gdb) run -batch -l loadup dump
> Starting program: /var/tmp/portage/emacs-21.4-r1/work/emacs-21.4/src/temacs
> -batch -l loadup dump
> Cannot insert breakpoint -2.
> Error accessing memory address 0x266f3: Input/output error.
> Binutils-220.127.116.11.2 gives the same error, but with 18.104.22.168.3 at least Emacs
> builds, even though it doesn't run in X. Perhaps rebuilding the entire system
> with 2.16.1 or 22.214.171.124.2 would make Emacs build?
This tells me it's some super-funky binutils b0rkage going on. Try
binutils-126.96.36.199.3 and 188.8.131.52.4 if you can (they're not keyworded, so
you'll have to employ an overlay or the files in /etc/portage to unmask them).
I know that 184.108.40.206.3 acts funny on glibc (iirc), but I haven't tested
220.127.116.11.4 on anything.
That all said, looks like a binutils thing, which are usually tricky to track
down. This will probably mean that emacs will remain unkeyworded for mips until
the bug is ever found and nailed.
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
firstname.lastname@example.org mailing list