kragen at pobox
Mar 17, 2000, 2:06 PM
Post #1 of 5
(94 views)
Permalink
|
|
build on NeXTStep (PR#240)
|
|
I'm building Python on NeXTStep; I've encountered three minor problems.
- importdl.c by default on NeXTStep allows linking with Objective-C
modules, which is cool. Unfortunately, properly supporting this
requires adding -ObjC to the cc command line in the Makefile.
- posixmodule.c doesn't #include anything that declares fsync() and
doesn't declare it itself, but tries to reference it. Adding a
declaration of fsync() fixes the problem.
- test_strftime and test_time fail.
test test_strftime failed -- Writing: 'Conflict for %j (julian day (001-366)):', expected: ''
I suspect this may be a platform bug. Here's some of the output,
which is 696 lines in full:
strftime test for Fri Mar 17 12:53:20 2000
Strftime test, platform: next3_3, Python version: 1.5.2
Conflict for %j (julian day (001-366)):
Expected 077, but got 076
Conflict for nonstandard '%c' format (near-asctime() format):
Expected Fri Mar 17 12:53:20 2000, but got Fri Mar 17 12:53:20 2000
Conflict for nonstandard '%x' format (%m/%d/%y %H:%M:%S):
Expected 03/17/00, but got Fri Mar 17 2000
Does not appear to support '%Z' format (time zone name)
Conflict for nonstandard '%D' format (mm/dd/yy):
Expected 03/17/00, but got ?
Conflict for nonstandard '%e' format (day of month as number, blank padded ( 0-31)):
Expected 17, but got ?
Conflict for nonstandard '%h' format (abbreviated month name):
Expected Mar, but got ?
Conflict for nonstandard '%k' format (hour, blank padded ( 0-23)):
Expected 12, but got ?
Conflict for nonstandard '%n' format (newline character):
Expected
, but got ?
Conflict for nonstandard '%r' format (%I:%M:%S %p):
Expected 12:53:20 PM, but got ?
Conflict for nonstandard '%R' format (%H:%M):
Expected 12:53, but got ?
Conflict for nonstandard '%s' format (seconds since the Epoch in UCT):
Expected 953326400, but got ?
Conflict for nonstandard '%t' format (tab character):
Expected , but got ?
Conflict for nonstandard '%T' format (%H:%M:%S):
Expected 12:53:20, but got ?
Conflict for nonstandard '%3y' format (year without century rendered using fieldwidth):
Expected 000, but got ?y
Conflict for %j (julian day (001-366)):
Expected 327, but got 326
Conflict for %W (week number of the year (Mon 1st)):
Expected 46, but got 47
Conflict for %j (julian day (001-366)):
Expected 328, but got 327
Conflict for %j (julian day (001-366)):
Expected 329, but got 328
Conflict for %j (julian day (001-366)):
Expected 330, but got 329
test test_time failed -- Writing: 'time.mktime(time.localtime(t)) <> t', expected: ''
(and that was all of the output from test_time. Presumably this is
related to the strftime bugs --- perhaps the mythical Y2K leap-year bug?)
I'm afraid I'm not sure what version of NeXTStep I'm on. 'arch'
reports 'hppa'; 'cc --version' reports '2.5.8'; 'uname -a' reports
'Command not found'.
I'm not trying to build a very sophisticated environment --- just the
defaults.
--
<kragen [at] pobox> Kragen Sitaker <http://www.pobox.com/~kragen/>
The Internet stock bubble didn't burst on 1999-11-08. Hurrah!
<URL:http://www.pobox.com/~kragen/bubble.html>
The power didn't go out on 2000-01-01 either. :)
|
