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

guido@python.org guido@python.org
Tue, 28 Mar 2000 14:39:17 -0500 (EST)

> It's NeXTStep 3.3.
> > 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.
> I can send a patch for importdl.c; the right thing to do for this would
> be to modify the Makefile to change the flags passed to the compiler to
> include -ObjC, but I don't know how to do that.  My solution was to
> change a #define in the source to turn off the ability to import
> Objective-C modules, which is obviously far from optimal --- thus my
> failure to include a patch for this in the first email.
> In posixmodule.c, which needs fsync() declared, I'm not sure where to
> declare it.  I can certainly supply a patch that works for NeXTStep
> 3.3, but I don't understand the rat's-nest of #ifdefs there well enough
> to be sure it won't break compilation on some other platform, or even
> another version of NeXTStep --- thus my failure to include a patch for
> this in the first email.
> So I can send patches for both of these, but I am not sure if I should.

Maybe we should just drop it?  I don't think NextStep 3.3 has much
future or even much current use, does it?  it's only supported for
historic reasons.  If you get it to work, fine -- but I don't think
the general public would benefit much from adding NS 3.3 support...

Or am I wrong?

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