Re: [avr32-libc-devel] Building AVR32-Libc with GNU tool chain

[Kaushik, P. <Pra...@at...>]

>-----Original Message-----
>From: Joerg Wunsch [mailto:j...@ur...] 
>Sent: Friday, July 23, 2010 12:26 AM
>To: Weddington, Eric
>Cc: Kaushik, Praveen_Kumar; avr...@li...
>Subject: Re: [avr32-libc-devel] Building AVR32-Libc with GNU tool chain


>As Weddington, Eric wrote:

>> Ah! I wasn't aware of this. We, the avr-libc developers, were never
>> able to successfully build the C++ compiler, partially due to the
>> fact that we could not build libstdc++. I'm now wondering if this
>> issue was a contributing factor.

>If I remember correctly, it's more like things as the absence of a
>full standard IO library, but it's been a long time since I've tried
>it for the last time.

Yes thats true that absence of full standard IO library is one of the reason why libstdc++ is not built in AVR tool chain. But if you look at the file <GCC Source Dir>/libstdc++-v3/configure.ac, you will find a test for 'with_newlib'. It says that if --with-newlib is given then we do not need to check for dlopen() support and  the link tests are avoided this way. I am not sure if there is any other way of avoiding these tests.


Thanks and Regards,
Praveen Kaushik