Paul Watson wrote:
> I also note that compiles occurring after the complaint about not
> finding Tcl/Tk do not appear to get the OPT= setting I specified on the
> 'make' command line. It starts with compilation of structmodule.c and
> includes the _codecs_??.c files. Does this have any signifi
Martin v. Löwis wrote:
> Paul Watson wrote:
>
>> It appears that _ALL_SOURCE gets defined in the
>> /usr/include/standards.h file. If we could #define _ANSI_C_SOURCE or
>> _POSIX_SOURCE, it appears that it would eleminate _ALL_SOURCE.
>
>
> Ah, ok - this should be easy enough. Python would no
Paul Watson wrote:
> It appears that _ALL_SOURCE gets defined in the /usr/include/standards.h
> file. If we could #define _ANSI_C_SOURCE or _POSIX_SOURCE, it appears
> that it would eleminate _ALL_SOURCE.
Ah, ok - this should be easy enough. Python would normally define
_POSIX_SOURCE (through _
Martin v. Löwis wrote:
> Paul Watson wrote:
>
>> Can we #undef _ALL_SOURCE for _codecs_cn.c compilation?
>
>
> Where does _ALL_SOURCE come from? Why is it defined?
> What is its effect on hz?
>
> Regards,
> Martin
Martin v. Löwis wrote:
> Paul Watson wrote:
>
>> Can we #undef _ALL_SOURCE fo
Paul Watson wrote:
> Can we #undef _ALL_SOURCE for _codecs_cn.c compilation?
Where does _ALL_SOURCE come from? Why is it defined?
What is its effect on hz?
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
Paul Watson wrote:
> This is on AIX 4.3.3
>
> $ grep -i _hz $(find . -name m_param.h)
> #define _HZ 100/* ticks per second of the clock*/
> #define __hzHZ /* Berkeley uses lower case hz */
> #define HZ _HZ
> #define hz __hz
I expected to see something li
Martin v. Löwis wrote:
> Paul Watson wrote:
>
>> Any ideas why ./Modules/cjkcodecs/_codecs_cn.c fails to compile? It
>> appears that the CODEC_STATELESS macro is concatenating 'hz' with a
>> number and text.
>
>
> More likely, hz is already defined to be 100, then forming 100_encode.
>
> It
Martin v. Löwis wrote:
> Paul Watson wrote:
>
>> Any ideas why ./Modules/cjkcodecs/_codecs_cn.c fails to compile? It
>> appears that the CODEC_STATELESS macro is concatenating 'hz' with a
>> number and text.
>
>
> More likely, hz is already defined to be 100, then forming 100_encode.
>
> It
Paul Watson wrote:
> Any ideas why ./Modules/cjkcodecs/_codecs_cn.c fails to compile? It
> appears that the CODEC_STATELESS macro is concatenating 'hz' with a
> number and text.
More likely, hz is already defined to be 100, then forming 100_encode.
It would be best if you could find out what A
Any ideas why ./Modules/cjkcodecs/_codecs_cn.c fails to compile? It
appears that the CODEC_STATELESS macro is concatenating 'hz' with a
number and text.
building '_codecs_cn' extension
cc -DNDEBUG -O -I. -I/home/pwatson/src/python/Python-2.4.2/./Include
-I/home/pwatson/src/python/Python-2.4.2
10 matches
Mail list logo
