Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Build broken with new gcc 4.8.3.

To: Christos Zoulas <christos%astron.com@localhost>
Subject: Re: Build broken with new gcc 4.8.3.
From: Martin Husemann <martin%duskware.de@localhost>
Date: Sun, 2 Mar 2014 21:08:44 +0100

On Sun, Mar 02, 2014 at 04:16:47PM +0000, Christos Zoulas wrote:
> Yes, we should probably add -gdwarf-2; Even dwarf-3 does not work properly.

What exactly is affected? Standard builds (even with HAVE_GCC=48) are
not (I just did one on amd64).

Fixing broken tools would be preferable, otherwise at least make the -gdwarf-2
conditional on dtrace (or whatever).

Martin

Follow-Ups:
- Re: Build broken with new gcc 4.8.3.
  - From: Martin Husemann
- Re: Build broken with new gcc 4.8.3.
  - From: Christos Zoulas

References:
- Build broken with new gcc 4.8.3.
  - From: henning petersen
- Re: Build broken with new gcc 4.8.3.
  - From: Christos Zoulas

Prev by Date: Re: Build broken with new gcc 4.8.3.
Next by Date: Re: Build broken with new gcc 4.8.3.
Previous by Thread: Re: Build broken with new gcc 4.8.3.
Next by Thread: Re: Build broken with new gcc 4.8.3.
Indexes:

Home | Main Index | Thread Index | Old Index