What happened to __FUNCTION__ in 3.4 ??

[David Daney]

Daniel Jacobowitz wrote:

>On Sun, Apr 04, 2004 at 05:25:49PM -0700, David Daney wrote:
>  
>
>>It seems that the psuedo preprocessor macro __FUNCTION__, is no longer a 
>>string literal in 3.4.
>>
>>This behavior is breaking my builds of glibc.
>>
>>I see two options:
>>
>>1) Hack up glibc so that it works again.
>>
>>2) Somehow change gcc's behavior.
>>
>>What should I do?
>>    
>>
>
>Try a more recent version of glibc?  Search the mailing list archives
>for more information?
>  
>
2.2.5

>"__FUNCTION__ glibc literal" gives me:
>  http://sources.redhat.com/ml/libc-hacker/2001-12/msg00036.html
>
>I don't know if that's relevant, since you didn't say what version of
>glibc you were trying to build, or for what target.
>
>  
>
Sorry, in my first look at the glibc CVS I missed where the problem had 
been fixed.  The answer does seem to be to upgrade to a more recent version.