[SciPy-user] some more cvs compile troubles.. config.h

Pearu Peterson pearu at cens.ioc.ee
Tue Mar 18 02:36:56 EST 2003


On Mon, 17 Mar 2003, Kasper Souren wrote:

> "python setup.py build" ends here on my Gentoo system:
> 
> gcc -DNDEBUG -fPIC -I/home/guaka/cvs/scipy/Lib/xplt/src/gist 
> -I/home/guaka/cvs/scipy/Lib/xplt/src/play 
> -I/home/guaka/cvs/scipy/Lib/xplt/src/play/unix -I/usr/include/python2.2 -c 
> /home/guaka/cvs/scipy/Lib/xplt/src/play/unix/dir.c -o 
> build/temp.linux-i686-2.2/dir.o 
> -DGISTPATH="/usr/lib/python2.2/site-packages/scipy/xplt/gistdata"
> In file included from /home/guaka/cvs/scipy/Lib/xplt/src/play/unix/dir.c:16:
> /home/guaka/cvs/scipy/Lib/xplt/src/play/unix/config.h:1: parse error before 
> '<<' token
> 
> Putting "//" in of line 1 of config.h fixed it.

To state the obvious, this config.h issue must be fixed by removing
system dependent config.h from CVS because whenever user system updates
config.h, it will be in conflict with the CVS version of config.h; and
further execution of `cvs update` will break the local config.h by
inserting to it diffs of conflicting files.

However, it is not clear where should config.h be created. The first
approach of creating it in the source tree (as it is done now) makes it
impossible to use the same scipy CVS tree for building xplt on different
platforms, unless an user knows to remove the following files
  xplt/pygist/Make.cfg
  xplt/src/play/unix/config.h
whenever switching platforms.

(Temporary) solution proposal:
First, remove config.h from CVS. Second, in local CVS tree remove 
    Lib/xplt/pygist/Make.cfg
    Lib/xplt/src/play/unix/config.h
Final note: when setup_xplt.py is called, these files are
regenerated; whenever switching platforms, remember to remove the two
files again.

Until config.h is removed from CVS, use the following instructions
after each action that changes config.h file:
- `cvs update` or "switching platforms"
- remove file
   Lib/xplt/pygist/Make.cfg
- build/install scipy

PS: the above applies only to unix systems, of course.

Pearu




More information about the SciPy-User mailing list