Re: new compile command doesn't coalesce errors on the same line

[Andreas Schwab]

address@hidden (Daniel Pfeiffer) writes:

> Saluton, Moin,
>
> Miles Bader <address@hidden> skribis:
>
>> If *compilation* looks like this:
>> 
>> cray.c:33: error: `driver_num' undeclared (first use in this function)
>> cray.c:33: error: (Each undeclared identifier is reported only once
>> cray.c:33: error: for each function it appears in.)
>
> And I would say that is a bug in gcc, because the other 2 lines are
> mislabeled.  They are _not_ errors, but merely informational.  If this were:

It's a multiline error message, _not_ three different ones.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."