X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Difficulties compiling emacs with gcc 4.6.2
Date: Thu, 26 Apr 2012 00:01:52 -0700 (PDT)
Organization: http://groups.google.com
Lines: 38
Message-ID: <76d604cb-2559-414c-95e5-06504006d6af@c4g2000yqj.googlegroups.com>
References: <201204090011 DOT 41565 DOT juan DOT guerrero AT gmx DOT de> <201204212330 DOT 14769 DOT juan DOT guerrero AT gmx DOT de>
 <83d370h41v DOT fsf AT gnu DOT org> <201204251935 DOT 54557 DOT juan DOT guerrero AT gmx DOT de>
 <83zk9zemcd DOT fsf AT gnu DOT org> <8e234c5c-6499-438e-af82-a27acc6430d6 AT m13g2000yqi DOT googlegroups DOT com>
 <83wr53edd7 DOT fsf AT gnu DOT org>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1335423712 854 127.0.0.1 (26 Apr 2012 07:01:52 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Thu, 26 Apr 2012 07:01:52 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: c4g2000yqj.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19
 (KHTML, like Gecko) Chrome/18.0.1025.162 Safari/535.19,gzip(gfe)
Bytes: 2859
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q3Q7F2DN010664
Reply-To: djgpp AT delorie DOT com

Hi,

On Apr 25, 4:00 pm, Eli Zaretskii <e DOT  DOT  DOT  AT gnu DOT org> wrote:
> > From: Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com>
> > Date: Wed, 25 Apr 2012 13:13:19 -0700 (PDT)
>
> > I guess nobody ever needed unexec on DWARF to work when COFF was
> > sufficient.
>
> Not true.  Back when DJGPP switched to DWARF2 as the default debug
> info, I tried to switch Emacs to using that, but the dumped Emacs
> crashed.

Okay, didn't know you'd already tried, just assumed it was "good
enough" as long as COFF debug unexec worked.

> And I didn't (and don't) have time to work on fixing that.
> But if someone gets that to work, I will happily switch, because COFF
> debug info is barely supported in latest versions of GCC and GDB.

I know this is a dumb question, but have you tried nagging the GCC or
Cygwin people for help? Esp. for PE/COFF, what do they do for unexec?

> > > Thanks.  So it seems like we still need to use -gcoff to produce a
> > > working and debuggable binary.
>
> > It's obvious that GCC 4.5.0 broke some stuff, but that's also when
> > they removed support for "generic" COFF.
>
> The problem started long before GCC 4.5.

Well, if I'm reading Juan's chart correctly, a lot of stuff changed
around that version, so that's where I put the most blame.

But you still (exclusively?) use an older GCC for your work anyways,
right? 3.4.x? So I guess that will do for now.

Sorry I can't help further, it's all Greek to me.