_POSIX_C_SOURCE

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Madhur
    #1

    _POSIX_C_SOURCE

    Hi,

    I would like to know the difference between using the
    C_INCLUDE_PATH and using the -I option with compilers. How are they
    different?

    The problem which I am facing is that I am having a
    source base which uses python. I am currently enabling compile time
    option _POSIX_C_SOURCE in my Makefile. The compilaiton fails if i
    include -I option to /usr/include/python2.4

    /usr/include/python2.4/pyconfig-32.h:838:1: error: "_POSIX_C_SOURC E"
    redefined

    but if i do

    export C_INCLUDE_PATH=/usr/include/python2.4

    I do not face any compilation issues.

    I would like to know if there is anything i am missing on this.

    Regards,
    Madhur
    Tags: None
    • Nick Craig-Wood
      #2
      Re: _POSIX_C_SOURCE

      Madhur <madhurrajn@gma il.comwrote:
      I would like to know the difference between using the
      C_INCLUDE_PATH and using the -I option with compilers. How are they
      different?
      No idea on that - I always just use -I
      The problem which I am facing is that I am having a
      source base which uses python. I am currently enabling compile time
      option _POSIX_C_SOURCE in my Makefile. The compilaiton fails if i
      include -I option to /usr/include/python2.4
      >
      /usr/include/python2.4/pyconfig-32.h:838:1: error: "_POSIX_C_SOURC E"
      redefined
      >
      but if i do
      >
      export C_INCLUDE_PATH=/usr/include/python2.4
      >
      I do not face any compilation issues.
      >
      I would like to know if there is anything i am missing on this.
      Do it in your code with

      #define _POSIX_C_SOURCE

      instead of the Makefile, and do it after the #include "Python.h"

      --
      Nick Craig-Wood <nick@craig-wood.com-- http://www.craig-wood.com/nick

        Comment

        Previous template Next
        Working...