This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: Comments on check-abi

From: Andreas Jaeger <aj at suse dot de>
To: Benjamin Kosnik <bkoz at redhat dot com>
Cc: libstdc++ at gcc dot gnu dot org
Date: Sat, 14 Jun 2003 17:44:44 +0200
Subject: Re: Comments on check-abi
References: <u8of17mh9n.fsf@gromit.moeb><20030611161335.42c846ac.bkoz@redhat.com>

Benjamin Kosnik <bkoz@redhat.com> writes:

> [...]
>>- We should always run the testsuite and consider a failure in
>>  check-abi a hard error.
>
> On a release branch only. But, once a release branch is set, and the ABI
> bits have been versioned, I'm for this.

Shouldn't we do it everywhere?  Currently make check-abi will not
return an error code if it fails, so we can let it run always.  This
will detect unneeded ABI changes directly.

Andreas
-- 
 Andreas Jaeger, SuSE Linux AG, aj@suse.de, http://www.suse.de/~aj
  GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Attachment: pgp00000.pgp
Description: PGP signature

References:
- Comments on check-abi
  - From: Andreas Jaeger
- Re: Comments on check-abi
  - From: Benjamin Kosnik

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