This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH][PING] Pass --with-dwarf2 on darwin8

From: Jack Howarth <howarth at bromo dot med dot uc dot edu>
To: IainS <developer at sandoe-acoustics dot co dot uk>
Cc: Mike Stump <mrs at gcc dot gnu dot org>, gcc patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 8 Sep 2010 21:24:38 -0400
Subject: Re: [PATCH][PING] Pass --with-dwarf2 on darwin8
References: <20100908133759.GA634@bromo.med.uc.edu> <77E53E3C-9E8E-4CB1-AB8A-0E4E385848AC@comcast.net> <A426F980-D8C3-4927-9877-D5315E1B4A2A@sandoe-acoustics.co.uk> <20100908231817.GA4084@bromo.med.uc.edu> <1DE1E31E-D8E3-4EF5-A2F7-74650CE6A057@sandoe-acoustics.co.uk>

On Thu, Sep 09, 2010 at 12:55:55AM +0100, IainS wrote:
>
>
> Have you any information on when x86_64 broke on the 4.5 branch ?

I didn't say that x86_64 broke on 4.5 branch. What I said was that
the use of --with-dwarf2 causes issues with the resulting x86_64
binaries on darwin8. See...

http://www.mail-archive.com/fink-devel@lists.sourceforge.net/msg20515.html

Which, as I understood the reports, was trying to use the x86_64 multilib
from a i386-apple-darwin8 compiler build.
                    Jack

>
> At present, I am only testing darwin 8 @ m32,
>
> Iain

References:
- [PATCH][PING] Pass --with-dwarf2 on darwin8
  - From: Jack Howarth
- Re: [PATCH][PING] Pass --with-dwarf2 on darwin8
  - From: Mike Stump
- Re: [PATCH][PING] Pass --with-dwarf2 on darwin8
  - From: IainS
- Re: [PATCH][PING] Pass --with-dwarf2 on darwin8
  - From: Jack Howarth
- Re: [PATCH][PING] Pass --with-dwarf2 on darwin8
  - From: IainS

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]