[ Date Prev][ Date Next][ Thread Prev][ Thread Next][ Date Index][ Thread Index]
Re: [coldfire-gnu-discuss] Override printf
- To: Nathan Sidwell <nathan@xxxxxxxxxxxxxxxx>
- Subject: Re: [coldfire-gnu-discuss] Override printf
- From: Daniel Jacobowitz <dan@xxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jul 2008 10:25:04 -0400
On Fri, Jul 11, 2008 at 08:08:18AM +0100, Nathan Sidwell wrote:
>> It looks like this is part of the CS3 library so I am guessing that
>> Newlib is getting linked in which then makes calls to the functions
>> above and that CS3 is complaining that they don’t exist since I haven’t
>> provided them for my hardware. Is this correct? How can I get rid of
>> these warnings? If Newlib is being linked in (which I think it is
>> because my final binary is MUCH bigger than before), how do I get it not
>> to link in and instead use my provided printf?
>
> You are most likely correct that newlib is still being linked in. You can
> track this down by using the -v option on your final link, to see how the
> linker is being invoked. The -Wl,-Map,a.map option may also be useful to
> determine what is pulling in newlib.
At a guess, it is referenced by the linker script (the INPUT
directive).
--
Daniel Jacobowitz
CodeSourcery
|