Paul Eggert wrote:
> This works
> around bugs in packages that mistakenly include after
> including (typically due to double-inclusion of
> ).
Formally, I don't think it's a bug to include twice in the
same compilation unit. We have documented [1] that it needs to included
first, but not that i
* m4/assert_h.m4 (gl_ASSERT_H): Arrange for to not
include if assert is already defined. This works
around bugs in packages that mistakenly include after
including (typically due to double-inclusion of
). Found in coreutils, which I plan to fix.
---
ChangeLog | 7 +++
m4/assert_h.m4
