Floating Point Hardware 2 - newlib link problem

--- Quote Start ---

I think you should post the code that generates the normal C summary. It looks like you have a %s corresponding to an uninitialized pointer or something along those lines. But it might be something deeper...

--- Quote End ---

Are you referring to the issue of this thread or the fact that my BSP takes >1 hour to build? To set the scene, I have a

successfully built application that was developed under Quartus 13.1 (including the FPH 2). On 13.1 the BSP takes > 1

hour to build on a reasonably fast machine with 16 GB RAM. I am now migrating the same design (hardware and

software) to Quartus 14.1 and have encountered the issue that is the subject of this thread. I would be keen to

improve the BSP build speed when using the FPH 2, however my first concern is to get a successful build, which

means fixing the newlib link issue.