|
1 |
|
2 2005-01-08 |
|
3 |
|
4 If you are have a problem building on OpenBSD and see output like this |
|
5 while running configure: |
|
6 |
|
7 checking curses.h presence... yes |
|
8 configure: WARNING: curses.h: present but cannot be compiled |
|
9 configure: WARNING: curses.h: check for missing prerequisite headers? |
|
10 configure: WARNING: curses.h: see the Autoconf documentation |
|
11 configure: WARNING: curses.h: section "Present But Cannot Be Compiled" |
|
12 configure: WARNING: curses.h: proceeding with the preprocessor's result |
|
13 configure: WARNING: curses.h: in the future, the compiler will take precedence |
|
14 |
|
15 there is likely a problem that will prevent building python. |
|
16 If you see the messages above and are able to completely build python, |
|
17 please tell python-dev@python.org indicating your version of OpenBSD |
|
18 and any other relevant system configuration. |
|
19 |
|
20 The build error that occurs while making may look something like this: |
|
21 |
|
22 /usr/include/sys/event.h:53: error: syntax error before "u_int" |
|
23 /usr/include/sys/event.h:55: error: syntax error before "u_short" |
|
24 |
|
25 To fix this problem, you will probably need update Python's configure |
|
26 script to disable certain options. Search for a line that looks like: |
|
27 |
|
28 OpenBSD/2.* | OpenBSD/3.@<:@012345678@:>@) |
|
29 |
|
30 If your version is not in that list, e.g., 3.9, add the version |
|
31 number. In this case, you would just need to add a 9 after the 8. |
|
32 If you modify configure.in, you will need to regenerate configure |
|
33 with autoconf. |
|
34 |
|
35 If your version is already in the list, this is not a known problem. |
|
36 Please submit a bug report here: |
|
37 |
|
38 http://sourceforge.net/tracker/?group_id=5470&atid=105470 |