Duplicate definitions of least32 workaround

See this patch

mentioned in merge request relibc!146 (merged)

I am still wondering why this is caused by relibc but not newlib.

I am too. When finding the patch I linked I saw someone say it happened to newlib too, guessing that was an older version or something. One thing I noticed is that changing integer types around works, such as having uint32_t be an unsigned int instead of unsigned long (see the temporary workaround I used in the first version of my relibc PR). Tricky stuff.

Closed somehow by @feliwir's changes to stdint!

closed