This is the mail archive of the
mailing list for the glibc project.
Re: gcc vs. glibc bootstrapping of libgcc_eh.a
Linas Vepstas <firstname.lastname@example.org> writes:
> Thanks Mike, silly me, it seems that crosstool_ng is exactly what I need!
> Off-topic, but .. anyone have a clue about why my canadian-cross of
> gcc is picking up its own internal limits.h, instead of glibc's
> limits.h? Since gcc's limits.h doesn't have âSSIZE_MAXâ which
> gcc/config/host-linux.c wants. I suppose I can just google the
> answer, can't I?
To clarify, your Canadian Cross should always be using gcc's internal
limits.h, so that is not surprising. The right question is why the
internal limits.h does not have a #include_next of the glibc limits.h
(via syslimits.h). I don't know the answer in your case, but I do know
that the test for whether there is a system limits.h, and that therefore
gcc should use a #include_next, is a fragile one.