Matthias Klose writes:
> Russ Allbery schrieb:
>> Matthias Klose writes:
>>> well, more headers are fixed, but I don't include these in the gcc
>>> package. I still think to find out how many headers are affected, we
>>> have to run the test at least once. Not sure how many many header
>>> files
Russ Allbery schrieb:
> Matthias Klose writes:
>
>> well, more headers are fixed, but I don't include these in the gcc
>> package. I still think to find out how many headers are affected, we
>> have to run the test at least once. Not sure how many many header files
>> will be found.
>
> Okay, in
Matthias Klose writes:
> well, more headers are fixed, but I don't include these in the gcc
> package. I still think to find out how many headers are affected, we
> have to run the test at least once. Not sure how many many header files
> will be found.
Okay, in that case I'll take a look at add
Russ Allbery schrieb:
> Matthias Klose writes:
>
>> gcc checks at build time all "system" headers (in /usr/include) and
>> fixes those headers which are not ANSI compliant. Because of
>> conflicting -dev packages, not all headers can be checked at gcc's
>> build time, so that could be made a lint
Matthias Klose writes:
> gcc checks at build time all "system" headers (in /usr/include) and
> fixes those headers which are not ANSI compliant. Because of
> conflicting -dev packages, not all headers can be checked at gcc's
> build time, so that could be made a lintian check (warning). I made an
5 matches
Mail list logo
