A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-July/027045.html below:

[Python-Dev] HAVE_CONFIG_H

[Python-Dev] HAVE_CONFIG_HGuido van Rossum guido@python.org
Mon, 29 Jul 2002 16:06:57 -0400
> > I see no references to HAVE_CONFIG_H in the source code (except one
> > #undef in readline.c), yet we #define it on the command line.  Is that
> > still necessary?
> 
> What about these ?

> ./Mac/mwerks/old/mwerks_nsgusi_config.h:
> -- define HAVE_CONFIG_H
> ./Mac/mwerks/old/mwerks_tk_config.h:
> -- define HAVE_CONFIG_H
> ./Mac/mwerks/old/mwerks_shgusi_config.h:
> -- define HAVE_CONFIG_H

I don't have a directory Mac/mwerks/old/.  Maybe you created this
yourself?

> ./Modules/expat/xmlparse.c:
> -- #ifdef HAVE_CONFIG_H
> ./Modules/expat/xmltok.c:
> -- #ifdef HAVE_CONFIG_H
> ./Modules/expat/xmlrole.c:
> -- #ifdef HAVE_CONFIG_H

We don't pass HAVE_CONFIG_H to extension modules, only to the core
(stuff built directly by the Makefile, not by setup.py).  That's a
good thing too, becaus these include <config.h>, not "pyconfig.h".

--Guido van Rossum (home page: http://www.python.org/~guido/)



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4