[Python-bugs-list] build on NeXTStep (PR#240)

[guido@python.org]

> 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:
[...]
> (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,

Can you send us some patches?  We don't have a NextStep system around
to test any of this, and your description of the problem doesn't help
me to create fixes that will certainly work for you.

There's probably not much you can do about the strftime problem --
just don't use time.strftime()! :-)

Please read python.org/patches for info on how to submit patches.
Thanks for contributing!

--Guido van Rossum (home page: http://www.python.org/~guido/)