This is the mail archive of the
mailing list for the GCC project.
RE: Unexpected presence of __eprintf in libgcc.a when using newlib
- From: "Thomas Preud'homme" <thomas dot preudhomme at arm dot com>
- To: "GCC Development" <gcc at gcc dot gnu dot org>
- Date: Wed, 9 Apr 2014 12:41:19 +0800
- Subject: RE: Unexpected presence of __eprintf in libgcc.a when using newlib
- Authentication-results: sourceware.org; auth=none
- References: <005201cf5306$7de51cb0$79af5610$ at arm dot com> <CAKOQZ8xSmAPN1b2QXn9OjPnf_j6BLXWhFQnSKhsRTu3VCMo67w at mail dot gmail dot com> <005901cf53a1$db5fea50$921fbef0$ at arm dot com> <CA+=Sn1mhmsP+zOLj5i-qXyz=Wv4hX7E5B2MoQdaFPog3W4wJGA at mail dot gmail dot com>
> From: Andrew Pinski [mailto:email@example.com]
> I think your patch is broken since the object file (_eprintf.o) should
> not be pulled in unless it is used and it is part of an archive and
> for archives cause the linker to only bring in object files which have
> things referenced to them.
Indeed, and after spending more time on it it is clear that the culprit is a function in another library (and that function is needed unfortunately). So no problem with eprintf in libgcc.a after all, sorry for the noise.