omnia neo wrote:
> Hi All,
>
> I am working on porting python on vxworks and hence was updating the PC
> \pyconfig.h file for configurng python. As I am reading the file and
> updating manually I come across lot many preprocessor directives which
> I dont understand e.g. HAV
Hi All,
I am working on porting python on vxworks and hence was updating the PC
\pyconfig.h file for configurng python. As I am reading the file and
updating manually I come across lot many preprocessor directives which
I dont understand e.g. HAVE_NICE etc. May be this is standard
nomenclature
Jeff Epler wrote:
> [sent to python-list and poster]
>
> Did you follow the direction that Python.h be included before any system
> header?
>
> This is mentioned at least in
> http://docs.python.org/ext/simpleExample.html
OK, I'll try to make it work this way. It's not totally trivial, b/c
[sent to python-list and poster]
Did you follow the direction that Python.h be included before any system
header?
This is mentioned at least in
http://docs.python.org/ext/simpleExample.html
It's a crummy thing for Python to insist on, but if you can re-organize
your headers to do this it sho
Magnus Lie Hetland wrote:
> It seems that in my Solaris installation,
> sysconfig.get_config_h_filename() returns './pyconfig.h', which is, of
> course, in most cases just wrong... :)
>
> Shouldn't this return an absolute path (in all cases)?
It should, and it do
It seems that in my Solaris installation,
sysconfig.get_config_h_filename() returns './pyconfig.h', which is, of
course, in most cases just wrong... :)
Shouldn't this return an absolute path (in all cases)? I've use an
absolute path in the --prefix of ./configure -- but I gue
The pyconfig.h file (/usr/include/python2.3/pyconfig.h) should begin
something like this
/* pyconfig.h. Generated by configure. */
/* pyconfig.h.in. Generated from configure.in by autoheader. */
and shouldn't cause problems.
If it starts in a wildly different way than that, then
I have installed Python-2.3.3 in the SUSE Linux 9.1 system and am
trying to rebuild an application rpm that was implemented in Python,
the defines in the pyconfig.h seem to be related to Microsoft 32-bit
and 64-bit environment, do I need these defines in the linux
environment? what is the purpose
Thanks. How do I verify what RPMs I need? I checked with rpm -qa |
python, it only showed the python package. After I included the
/usr/include/sys/io.h in the source package INCLUDE path, it seemed
like the compilation went into a include loop.
(/usr/include/sys/unisted.h:1:10 #include nested too
pythonnewbie wrote:
where I should find the correct "io.h" in this linux environment?
Should be in /usr/include/sys/io.h
You are probably missing some RPM that has various system header files.
--
Michael Hoffman
--
http://mail.python.org/mailman/listinfo/python-list
I am trying to rebuild a rpm that was implemented in the python
language. I installed the python package 2.3.3 from Suse 9.1 Linux CD.
I got the following error when rebuilding the rpm,
/usr/Python-2.3.3/Include/pyconfig.h:30:16: io.h: No such file or
directory
where I should find the correct
11 matches
Mail list logo
