🚀 go-pugleaf

In gnu.gcc.help Amos A. Gouaux writes:

>by setting prefix to /usr/local/gnu, i was able to see that a header file
>called assert.h was stuck into ($prefix)/include.  perhaps this could go
>into ($prefix)/lib/gcc-lib/include too, to be consistent.  

Putting <assert.h> in $(prefix)/lib/gcc-lib/include can cause problems
if more than one different ANSI library is used, such as using glibc.
This is because assert.h makes assert call __eprintf, which is defined
in libgcc2.c, and __eprintf uses stdio to output a message.  This
might be built with the native version of <stdio.h>; if you then
switch to using the glibc version of stdio, the wrong thing will get
passed to fprintf.  Putting <assert.h> in $(prefix)/include allows
glibc to override it; if it were in $(prefix)/lib/gcc-lib/include,
then it would always be found first, and glibc would be out of luck.

Ian Taylor