From: Andrew Choi <akochoi_NOSPAM_@shaw.ca>
Subject: Re: carbon emacs won't build with Dec 2002 dev tools?
Date: Sat, 21 Dec 2002 21:02:02 GMT [thread overview]
Message-ID: <m265tn3x2t.fsf@owlbear.local> (raw)
In-Reply-To: dh3N9.417215$%m4.128206@rwcrnsc52.ops.asp.att.net
Hugo Wolf <hwolf@deutsches.lieder.net> writes:
> I just updated the emacs cvs sources and installed the latst Developer
> Tools from Apple. I can no longer build emacs with carbon support.
> It seems to be failing in a link step (see below).
>
> It could be that something else in my environment is causing this, in
> particular some updated fink components. Can anyone running a more
> generic 10.2.3 with the December 2002 Developer Tools confirm this
> problem, or conversely confirm that it builds ok?
>
> [...]
>
> # cmd cmdsize name address size
> 0 LC_SEGMENT 56 __PAGEZERO 0 0x1000
> 1 LC_SEGMENT 532 __TEXT 0x1000 0x152000
> __text 0x37ac 0x138584
> __picsymbol_stub 0x13bd30 0x378c
> __symbol_stub 0x13f4bc 0
> __cstring 0x13f4bc 0x12b9c
> __literal8 0x152058 0x108
> __literal4 0x152160 0xc
> __const 0x15216c 0x96
> 2 LC_SEGMENT 532 __DATA 0x153000 0x124000
> __data 0x153000 0xe8278
> __la_symbol_ptr 0x23b278 0x62c
> __nl_symbol_ptr 0x23b8a4 0x84c
> __dyld 0x23c0f0 0x1c
> __cfstring 0x23c10c 0x10
^^^^^^^^^^
> __common 0x23c120 0xabec
> __bss 0x246d10 0x30130
>
> [...]
> unexec: unrecognized section name in __DATA segment
> make[1]: *** [bootstrap-emacs] Error 1
> make: *** [bootstrap] Error 2
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. This will work most likely, because from
its name, that section probably contains only strings.
Otherwise just don't upgrade to the new version of the Developer Tools
yet.
next prev parent reply other threads:[~2002-12-21 21:02 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 [this message]
2002-12-21 21:13 ` Hugo Wolf
2002-12-21 22:24 ` Andrew Choi
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=m265tn3x2t.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).