bug-ddd
[Top][All Lists]
Advanced

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

RE: GCC 2.8.1 fails to build 3.2.95 (3.2.93 was ok)


From: Derks, Victor
Subject: RE: GCC 2.8.1 fails to build 3.2.95 (3.2.93 was ok)
Date: Wed, 17 Jan 2001 10:21:57 +0100

Note: 

The INSTALL text of DDD 3.2.95 only recommends GCC 2.95, version 2.7.2 is
the minimum. 
Should that line not be updated to indicate that GCC 2.95 is the minimum?

Victor

> -----Original Message-----
> From: Andreas Zeller [SMTP:andreas.zeller@fmi.uni-passau.de]
> Sent: Wednesday, January 17, 2001 10:16 AM
> To:   Derks, Victor
> Cc:   'bug-ddd@gnu.org'
> Subject:      Re: GCC 2.8.1 fails to build 3.2.95 (3.2.93 was ok)
> 
> Hi!
> 
> "Derks, Victor" <Victor.Derks@nl2.vdogrp.de> writes:
> 
> > Environment:
> > 
> > Solaris 2.6
> > GCC   2.8.1
> > 
> > Problem:
> > 
> > GCC generates errors for constructors which call explicit an empty
> > constructor to initialize a member:
> > 
> > XErrorB.h
> > 
> >     XErrorBlocker(const XErrorBlocker&)
> >     : _display(0), _error_occurred(false), 
> >       saved_active(0), _event() <== _event() IS THE PROBLEM
> >     {
> >     assert(0);
> >     } 
> > 
> > 
> > by removing _event(),_event is a private member of the class of type
> > XErrorEvent which is defined as a struct with no constructor, 
> > I could remove the error. The same construction appears also in the
> files
> > DDD.C SignalB.C
> 
> Thanks!  This will be fixed in the final DDD 3.3 release.  
> 
> (However, the `INSTALL' requirements will state explicitly that DDD
> 2.95 or later is required, although older GCC versions may work.)
> 
> Andreas
> 
> -- 
> Andreas Zeller     Universitaet Passau
>                    http://www.fmi.uni-passau.de/st/staff/zeller/
> 
> 
> -----------------------------------------------------------
> This Mail has been checked for Viruses
> Attention: Encrypted Mails can NOT be checked !
> 
> ***
> 
> Diese Mail wurde auf Viren ueberprueft
> Hinweis: Verschluesselte Mails koennen NICHT geprueft werden!
> ------------------------------------------------------------



reply via email to

[Prev in Thread] Current Thread [Next in Thread]