Re: Emacs 21.3.50 on OS X 10.2.2

[Chris Waterson]

Hugo Wolf wrote:

> In article , Gavin
> White wrote:
>
> >I updated Jaguar to 10.2.2 today, and now Emacs won't load.
>
>
> Yep, looks like you'll have to rebuild.  I just went through that -
> see posts on comp.sys.mac.system.  I wasn't expecting this in a minor
> os upgrade (10.2.1->10.2.2).  Works fine after rebuilding though.

Hmm.  I'm not able to rebuild, either.  The build "bootstrap-emacs" that 
I have segfaults, so I can't compile any of the elisp files. 
Unfortunately, the crash is somewhere in dyld:

/usr/local/src/emacs/2002-11-01/emacs$ gdb src/bootstrap-emacs 

[...]
(gdb) run 

[...] 

Program received signal EXC_BAD_ACCESS, Could not access memory. 

0x8fe0d53c in __dyld_lookup_symbol () 

(gdb) bt 

#0  0x8fe0d53c in __dyld_lookup_symbol () 

#1  0x8fe0baac in __dyld_resolve_undefineds () 

#2  0x8fe10614 in __dyld_link_in_need_modules () 

#3  0x8fe014e4 in __dyld__dyld_init () 

(gdb)

This is making me believe that "dump-emacs" in loadup.el is just 
generating a garbage binary.

I'm getting some duplicate symbol errors when linking temacs (which will 
itself run fine):

ld: warning multiple definitions of symbol _PC 

terminfo.o definition of _PC in section (__DATA,__common) 

/usr/lib/libncurses.dylib(lib_tputs.o) definition of _PC 

ld: warning multiple definitions of symbol _BC 

terminfo.o definition of _BC in section (__DATA,__common) 

/usr/lib/libncurses.dylib(lib_termcap.o) definition of _BC 

ld: warning multiple definitions of symbol _UP 

terminfo.o definition of _UP in section (__DATA,__common) 

/usr/lib/libncurses.dylib(lib_termcap.o) definition of _UP 


#ifdef'ing these MAC_OSX in terminfo.c has no effect, sadly.

The emacs-os/x FAQ mentions bad ju-ju related to fink, so I guess my 
next trick will be uninstalling that... :-(

Help!

thanks,
chris