[f2py] problem generating __doc__

[Peter-Jan Randewijk]

Dear Frédéric,

Thank-you for your answer.  You were more helpfull thant the f2py-users 
list.

I'm using openSUSE 10.3.  In "/usr/lib/python[2.5]/config/Makefile" it 
uses the options ... -Wall -D_FORTIFY_SOURCE=2 ..

Setting D_FORTIFY_SOURCE=1 solved the problem.  Thank-you very much.

Kind regards,

Peter-Jan

PS: My English is (or is it are) ;-)    not that great either.  But you 
(as in  the Franch) are excused for hosting a wonderful Ruby World Cup, 
or for us at least.


Op 2007/10/26 07:08, het Frédéric Dubois die volgende geskryf:
> Hello Peter-Jan,
> My problem was coming from the fact that when f2py try to compile 
> things, at the last stage it uses gcc with options
> defined by python. Depending on the linux distribution it may use the 
> -Wp,-D_FORTIFY_SOURCE=2  option
> (which concerns security)  which is incompatible with a correct  
> __doc__ generation. I found 3 solutions:
> 1 - modify the python options  in /usr/lib/python2.4/config/Makefile 
> if i remember well
> 2 - don't use Redhat/fedora/centos ... linux distribution which use 
> this option for security reason
> 3 - tell  to pearu that f2py should be compliant with this security 
> problems. Actually he didn't answer me.
>
> Sorry for my poor english.
> Regards
>
> Peter-Jan Randewijk a écrit :
>> Dear Frédéric,
>>
>> Have you had any luck with the empty __doc__ strings?
>>
>> Kind regards,
>>
>> Peter-Jan
>>
>> Op 2007/07/27 09:44, het Frédéric Dubois die volgende geskryf:
>>> concerning my problem with empty __doc__
>>> following step by step the f2py work and doing it by hand
>>> in fact it seems that the problem is coming from a gcc option: 
>>> -Wp,-D_FORTIFY_SOURCE=2
>>> any body knows what it means and where this option is defined ?
>>>
>>> regards
>>>
>>