mode_t not appropriate for chmod in BCC

[ixokai]

BPO	417802
Nosy	@tim-one

^{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/tim-one'
closed_at = <Date 2001-04-30.22:18:47.000>
created_at = <Date 2001-04-21.05:49:54.000>
labels = ['build']
title = 'mode_t not appropriate for chmod in BCC'
updated_at = <Date 2001-04-30.22:18:47.000>
user = 'https://bugs.python.org/ixokai'

bugs.python.org fields:

activity = <Date 2001-04-30.22:18:47.000>
actor = 'tim.peters'
assignee = 'tim.peters'
closed = True
closed_date = None
closer = None
components = ['Build']
creation = <Date 2001-04-21.05:49:54.000>
creator = 'ixokai'
dependencies = []
files = []
hgrepos = []
issue_num = 417802
keywords = []
message_count = 4.0
messages = ['4419', '4420', '4421', '4422']
nosy_count = 2.0
nosy_names = ['tim.peters', 'ixokai']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue417802'
versions = []

[ixokai]

In reference to the 'chmod' definition in
posixmodule.c (~line 155). Under Borland
C++5.5, 'mode_t' is defined in sys/types.h as a short,
and yet io.h defines 'chmod' as taking char* and an
int, so the compiler gives an error of, "Type mismatch
in redeclaration of 'chmod'" here.

Since sys/types.h is going to redefine mode_t after
anything we put into pyport/config, the only way I can
see to fix this would be to put an #ifdef __BORLANDC__
in there.

Now, to go fix all the other errors BC is spitting out
in that file. <le sigh>

[ixokai]

Logged In: YES
user_id=200343

The below is Python 2.1final, btw. I keep forgetting to
include that.

[ixokai]

Logged In: YES
user_id=200343

I submitted a patch (bpo-418147) that corrects this and the
other problems w/ compiling Borland on Python.

[tim-one]

Logged In: YES
user_id=31435

Superceded by patch 418147.