all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Samuel Bronson <naesten@gmail.com>
To: 9927@debbugs.gnu.org
Subject: bug#9927: 24.0.90; unexec/unexmacosx fails with GCC 4.6.1
Date: Sat, 30 Jun 2012 12:47:59 -0400	[thread overview]
Message-ID: <naesten-33B1E6.12475930062012@dough.gmane.org> (raw)
In-Reply-To: <6A5F6D17-397A-48F7-87E9-D77C09B60EC6@Freenet.DE>

Samuel Bronson <naesten@gmail.com> wrote:

> I suppose, though, that if we could be sure that we aren't linking in  
> any static libraries with these *new* BSS sections which will have  
> trouble because of Emacs' dumping them, we could just skip that part;  
> then all we'd need to do is make sure that my_endbss_static refers to  
> an address in __DATA.__bss, not __DATA.__bss1 or __DATA.bss2 like it  
> would naturally end up at on GCC 4.6 or 4.7 (respectively).  (And make  
> unexmacosx.c dump these new BSS sections, of course.)

Well, after my GCC 4.7 build finished, I had a go at building Emacs with 
it and (after getting distracted for a bit playing with the 
--enable-gcc-warnings flag) I got temacs to build and link.  (There was 
some awkwardness involving the -fobjc-exceptions flag that we'll need to 
straighten out...)

I decided I might as well try the simplest thing that could possibly 
work: just dump __DATA.__static_data in the usual way, and dump these 
new BSS sections like __DATA.__bss, only in their entirety rather than 
messing about with markers.

When my first try ended in SIGSEGV, I ran "gobjdump --all" on temacs and 
didn't see any evidence of staticly-linked libraries besides libgcc and 
gnulib; then I noticed that I hadn't looked closely enough at the code 
I'd copied and pasted into my new "else if" clause and rewrote it to 
ACTUALLY work like that for __DATA.__bss without the marker stuff, and 
then I actually got an Emacs.app that worked!

You can see my changes at:
http://bazaar.launchpad.net/~naesten/emacs/nextstep-stuff/revision/108754

Be warned that the line numbers will probably be way off of emacs trunk 
right now, since an earlier commit on my branch deletes largish swathes 
of code that wasn't really doing anything useful.






  parent reply	other threads:[~2012-06-30 16:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01  0:24 bug#9927: 24.0.90; unexec/unexmacosx fails with GCC 4.6.1 on intel Mac OS X 10.6.8 Peter Dyballa
     [not found] ` <handler.9927.B.132010738317348.ack@debbugs.gnu.org>
2012-04-17  9:17   ` bug#9927: Acknowledgement (24.0.90; unexec/unexmacosx fails with GCC 4.6.1 on intel Mac OS X 10.6.8) Peter Dyballa
2012-06-29 17:03 ` bug#9927: 24.0.90; unexec/unexmacosx fails with GCC 4.6.1 Samuel Bronson
2012-06-29 19:19   ` Peter Dyballa
2012-06-30 16:47   ` Samuel Bronson [this message]
2013-07-25 19:37     ` Glenn Morris
2014-08-09 17:05 ` bug#9927: 24.1.50; unexec/unexmacosx doesn't grok GCC 4.6+ sections Stefan Monnier
2014-08-11  1:20   ` Glenn Morris
2014-08-11  1:40   ` Samuel Bronson
2014-08-11  1:56     ` Glenn Morris
2014-09-17 18:39 ` Paul Eggert
2014-09-17 19:48   ` Glenn Morris
2014-09-17 19:59     ` Paul Eggert
2014-09-17 21:00   ` Peter Dyballa
2014-09-17 21:10     ` Paul Eggert
2014-09-18  2:37       ` Stefan Monnier
2014-09-18  5:27         ` Paul Eggert
2014-09-18 13:05           ` Stefan Monnier
2014-10-04  9:02           ` Peter Dyballa
2014-10-04 17:19             ` Paul Eggert
2014-10-04 18:18               ` Glenn Morris
2014-10-04 19:43                 ` Paul Eggert
2014-10-05 18:36               ` Peter Dyballa
2014-10-05 23:19                 ` Paul Eggert
2014-10-06  1:29                   ` Stefan Monnier
2014-10-06  2:47                     ` Paul Eggert
2014-10-06 13:15                       ` Stefan Monnier
2014-10-06 16:16           ` Peter Dyballa
2014-09-17 22:20   ` Peter Dyballa

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=naesten-33B1E6.12475930062012@dough.gmane.org \
    --to=naesten@gmail.com \
    --cc=9927@debbugs.gnu.org \
    /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.