From: David Reitter <david.reitter@gmail.com>
To: Ian Eure <ian@digg.com>
Cc: Dan Nicolaescu <dann@ics.uci.edu>,
David Engster <deng@randomsample.de>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: gcc 4.2 dump problems
Date: Tue, 25 Aug 2009 12:15:02 -0400 [thread overview]
Message-ID: <77EADE1C-D5C7-4A12-A7AA-F93850CDFD24@gmail.com> (raw)
In-Reply-To: <564D465F-EEE4-41B7-AE77-98096EF7672B@digg.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Aug 25, 2009, at 11:56 AM, Ian Eure wrote:
>> I'm reviving this old thread, since I'm now facing the same problem
>> with
>> the arrival of Mac OS X 10.6...
>>
> Perhaps you can install MacPorts and the apple-gcc40 port as a
> temporary workaround.
Anyone, please post if you've been successful. I have tried this a
while ago with "i686-apple-darwin10-gcc-4.0.1", but perhaps I didn't
pick the right compiler+linker settings.
Thankfully, Dan N has been looking into this - some info below. I
haven't found any info on this new link format - pointers appreciated.
Dan Nicolaescu wrote:
>
> On Snow Leopard:
> It looks like dumper in emacs does not understand the new compact link
> edit format in Snow Leopard. (Long term someone needs to reword
> unexecmacosx.c to deal with that)
>
> Unfortunately workarounds to not use that format like:
> -mmacosx-version-min=10.4
> or
> -mmacosx-version-min=10.5 -Wl,-no_compact_linkedit
>
> don't seem to help either.
>
> I'll let you know if I find out more.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]
next prev parent reply other threads:[~2009-08-25 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 17:25 gcc 4.2 dump problems David Reitter
2009-08-06 18:09 ` Werner LEMBERG
2009-08-06 18:24 ` Dan Nicolaescu
2009-08-06 19:03 ` David Reitter
2009-08-06 19:29 ` Dan Nicolaescu
2009-08-25 13:18 ` David Engster
2009-08-25 15:56 ` Ian Eure
2009-08-25 16:15 ` David Reitter [this message]
2009-08-26 13:32 ` David Engster
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77EADE1C-D5C7-4A12-A7AA-F93850CDFD24@gmail.com \
--to=david.reitter@gmail.com \
--cc=dann@ics.uci.edu \
--cc=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
--cc=ian@digg.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.