From: Andrew Choi <akochoi_NOSPAM_@shaw.ca>
Subject: Re: carbon emacs won't build with Dec 2002 dev tools?
Date: Sat, 21 Dec 2002 22:24:10 GMT [thread overview]
Message-ID: <m2d6nvdn91.fsf@owlbear.local> (raw)
In-Reply-To: XP4N9.452053$QZ.70246@sccrnsc02
Hugo Wolf <hwolf@deutsches.lieder.net> writes:
> In article <m265tn3x2t.fsf@owlbear.local>, Andrew Choi wrote:
> > An obvious thing to try to modify unexmacosx.c to treat the section
> > `__cfstring' like other sections not requiring relocation, such as
> > `__la_symbol_ptr' and others.
>
> Obvious to you maybe :) I'll look into this and see if I can figure
> something out. Thanks for the hint.
It really is, if you use gdb to check where temacs failed.
The change to make is to add an additional comparison
|| strncmp (sectp->sectname, "__cfstring", 16) == 0
to the following comparison in unexmacosx.c (copy_data_segment).
...
else if (strncmp (sectp->sectname, "__la_symbol_ptr", 16) == 0
|| strncmp (sectp->sectname, "__nl_symbol_ptr", 16) == 0
|| strncmp (sectp->sectname, "__dyld", 16) == 0
|| strncmp (sectp->sectname, "__const", 16) == 0)
Would appreciate it if you can report the result to the list, for the
benefit of those who are thinking about installing the new developer
tools.
next prev parent reply other threads:[~2002-12-21 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 19:28 carbon emacs won't build with Dec 2002 dev tools? Hugo Wolf
2002-12-21 21:02 ` Andrew Choi
2002-12-21 21:13 ` Hugo Wolf
2002-12-21 22:24 ` Andrew Choi [this message]
2002-12-21 23:41 ` Hugo Wolf
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=m2d6nvdn91.fsf@owlbear.local \
--to=akochoi_nospam_@shaw.ca \
/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).