Comments on check-abi

[Andreas Jaeger]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20030614/1c5b0216/attachment.sig>