Build failure on OpenBSD 4.4-current regarding lstat()

[vext01]

BPO	4639
Nosy	@loewis, @skrah
Superseder	bpo-7903: Configure script incorrect for reasonably recent OpenBSD

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/skrah'
closed_at = <Date 2010-04-12.09:53:11.456>
created_at = <Date 2008-12-12.14:11:18.322>
labels = ['build']
title = 'Build failure on OpenBSD 4.4-current regarding lstat()'
updated_at = <Date 2010-04-12.09:53:11.454>
user = 'https://bugs.python.org/vext01'

bugs.python.org fields:

activity = <Date 2010-04-12.09:53:11.454>
actor = 'skrah'
assignee = 'skrah'
closed = True
closed_date = <Date 2010-04-12.09:53:11.456>
closer = 'skrah'
components = ['Build']
creation = <Date 2008-12-12.14:11:18.322>
creator = 'vext01'
dependencies = []
files = []
hgrepos = []
issue_num = 4639
keywords = ['patch']
message_count = 4.0
messages = ['77667', '99376', '99377', '102935']
nosy_count = 3.0
nosy_names = ['loewis', 'vext01', 'skrah']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '7903'
type = 'compile error'
url = 'https://bugs.python.org/issue4639'
versions = ['Python 2.6']

[vext01]

Hi,

I just had to move the "extern lstat..." outside the "ifndef
HAVE_LSTAT" to get python 2.6.1 to build on OpenBSD 4.4-current/i386.

I'm not suggesting this is correct, but it fixes the build for my
platform at least.

--- Modules/posixmodule.c.orig     Fri Dec 12 11:08:54 2008
+++ Modules/posixmodule.c       Fri Dec 12 11:54:16 2008
@@ -208,10 +208,11 @@
 #ifdef HAVE_SYMLINK
 extern int symlink(const char *, const char *);
 #endif /* HAVE_SYMLINK */
+#endif /* !HAVE_UNISTD_H */
+
 #ifdef HAVE_LSTAT
 extern int lstat(const char *, struct stat *);
 #endif /* HAVE_LSTAT */
-#endif /* !HAVE_UNISTD_H */

#endif /* !_MSC_VER */

Im using gcc-4.2

Thanks

[loewis]

Can you please try the Python trunk (or release26-maint branch) and report whether the problem still occurs?

[skrah]

This is fixed in trunk by the configure.in patch. I've tested trunk on 4.4
and 4.7.

[skrah]

This has been fixed in bpo-7903.