Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision 62a14db9f4f7b77bfc5663902f0d05f74901e950 authored by R. David Murray on 26 June 2010, 18:39:50 UTC, committed by R. David Murray on 26 June 2010, 18:39:50 UTC 
#9085: email versions have gotten out of sync, 2.7 is actually 4.0.3.
 
In 2.5 the email version was bumped to 4.0.2 just before release but
after the maintenance branch was set up.  The bump was not backported
to trunk, and 2.6 went out the door with a version number of 4.0.1.
I bumped this to 4.0.2 because of a behavior change, but that makes
it look the same as 2.5.  So bump it again to 4.0.3.
1 parent 04a3439
Raw File
Tip revision: 62a14db9f4f7b77bfc5663902f0d05f74901e950 authored by R. David Murray on 26 June 2010, 18:39:50 UTC
#9085: email versions have gotten out of sync, 2.7 is actually 4.0.3.
Tip revision: 62a14db
README.OpenBSD 

2005-01-08

If you are have a problem building on OpenBSD and see output like this
while running configure:

checking curses.h presence... yes
configure: WARNING: curses.h: present but cannot be compiled
configure: WARNING: curses.h: check for missing prerequisite headers?
configure: WARNING: curses.h: see the Autoconf documentation
configure: WARNING: curses.h: section "Present But Cannot Be Compiled"
configure: WARNING: curses.h: proceeding with the preprocessor's result
configure: WARNING: curses.h: in the future, the compiler will take precedence

there is likely a problem that will prevent building python.  
If you see the messages above and are able to completely build python,
please tell python-dev@python.org indicating your version of OpenBSD
and any other relevant system configuration.

The build error that occurs while making may look something like this:

    /usr/include/sys/event.h:53: error: syntax error before "u_int"
    /usr/include/sys/event.h:55: error: syntax error before "u_short"

To fix this problem, you will probably need update Python's configure
script to disable certain options.  Search for a line that looks like:

    OpenBSD/2.* | OpenBSD/3.@<:@012345678@:>@)

If your version is not in that list, e.g., 3.9, add the version
number.  In this case, you would just need to add a 9 after the 8.
If you modify configure.in, you will need to regenerate configure
with autoconf.

If your version is already in the list, this is not a known problem.
Please submit a bug report here:

    http://sourceforge.net/tracker/?group_id=5470&atid=105470
back to top