unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Chris Waterson <waterson@netscape.com>
Subject: Re: Emacs 21.3.50 on OS X 10.2.2
Date: Tue, 12 Nov 2002 18:45:40 -0800	[thread overview]
Message-ID: <aqsekd$8i0$1@pixie.nscp.aoltw.net> (raw)
In-Reply-To: <f67cd586.0211111752.1040b258@posting.google.com>

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

  parent reply	other threads:[~2002-11-13  2:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  1:52 Emacs 21.3.50 on OS X 10.2.2 Gavin White
2002-11-12  2:22 ` Hugo Wolf
2002-11-12 21:47   ` Chris Brierley
2002-11-12 23:09     ` Schone Mullerin
2002-11-13  6:51       ` Amos
2002-11-13 11:08         ` Hugo Wolf
2002-11-13 12:24         ` Joseph Kiniry
2002-11-13 12:58           ` Hugo Wolf
2002-11-13 13:17         ` Henrik Holm
2002-11-13 21:01     ` Heiko Hellweg
2002-11-14  6:24       ` Amos
2002-11-14  8:03         ` Heiko Hellweg
2002-11-13  2:45   ` Chris Waterson [this message]
2002-11-13 11:22     ` Hugo Wolf
2002-11-13 19:36       ` Chris Waterson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='aqsekd$8i0$1@pixie.nscp.aoltw.net' \
    --to=waterson@netscape.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).