From: Hugo Wolf <hwolf@deutsches.lieder.net>
Subject: Re: carbon emacs won't build with Dec 2002 dev tools?
Date: Sat, 21 Dec 2002 21:13:27 GMT [thread overview]
Message-ID: <XP4N9.452053$QZ.70246@sccrnsc02> (raw)
In-Reply-To: m265tn3x2t.fsf@owlbear.local
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.
> Otherwise just don't upgrade to the new version of the Developer Tools
> yet.
It has a number of important bug fixes that I need for other packages,
and so far hasn't choked on anything else. All in all I'm better off
with it, as I suspect most osx users probably will be.
next prev parent reply other threads:[~2002-12-21 21:13 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 [this message]
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='XP4N9.452053$QZ.70246@sccrnsc02' \
--to=hwolf@deutsches.lieder.net \
/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).