Re: [Discuss-gnuradio] Problem in usable Python.h header file.

[Greg Troxel]

GNU Radio 3.0 works fine wtih Python 2.4.

  > Tarun Tiwari wrote:
  > I found my Python.h file is in /usr/local/include/python2.4 whereas .
  > /configure command alwasy look for /usr/linclude/python2.4

  > I used export PYTHONPATH=/usr/local/include/python2.4 but that is not
  > working. Can someone tell me where is the problem, and what do i need to
  > do
  > to resolve this issue?

PYTHONPATH is to tell python where to look, not to tell configure
where to find python.

You need to tell configure what directories to look in.  As an
example, on NetBSD, base system includes and libraries are in
/usr/include and /usr/lib, and packages built via pkgsrc are in
/usr/pkg/include and /usr/pkg/lib.  /usr/pkg isn't in the default
search path, so I use:

LDFLAGS="-L/usr/pkg/lib -R/usr/pkg/lib -L/usr/adroit/lib -R/usr/adroit/lib" 
CPPFLAGS="-I/usr/pkg/include -I/usr/adroit/include" ./configure 
--prefix=/usr/adroit $CONF_ARGS

to search additional prefixes when building GNU Radio from svn; in
general you need to pass such LDFLAGS/CPPFALGS to use packages in
places other than the default compiler search path.  (Note that
whether to use -R depends on your OS and the rules for finding shared
libraries at runtime - there's the -R approach, the
ld.so.conf/LD_LIBRARY_PATH approach, and the
bind-full-paths-in-binaries approach.  I have no idea which of these
approaches Mandriva uses.)

But, I'd say it's odd on a GNU/Linux system that python is in a place
that isn't in the default compiler search paths.  Did you build it by
hand?

pgpHwDqhxEfpS.pgp
Description: PGP signature