Commit 73f8ab2e authored by Neil Schemenauer's avatar Neil Schemenauer

- Edit the QNX instructions to refer to Makefile, not Modules/Makefile.

- Setup is now copied from Setup.dist by configure.
parent 66012fe8
...@@ -337,7 +337,7 @@ QNX: Chris Herborth (chrish@qnx.com) writes: ...@@ -337,7 +337,7 @@ QNX: Chris Herborth (chrish@qnx.com) writes:
I've only run small programs and the test cases), you're I've only run small programs and the test cases), you're
probably running out of stack; the default 32k could be a probably running out of stack; the default 32k could be a
little tight. To increase the stack size, edit the Makefile little tight. To increase the stack size, edit the Makefile
in the Modules directory to read: LDFLAGS = -N 48k to read: LDFLAGS = -N 48k
BeOS: Chris Herborth (chrish@qnx.com) writes: BeOS: Chris Herborth (chrish@qnx.com) writes:
See BeOS/README for notes about compiling/installing Python on See BeOS/README for notes about compiling/installing Python on
...@@ -694,7 +694,7 @@ directory and you want to build in /usr/tmp/python): ...@@ -694,7 +694,7 @@ directory and you want to build in /usr/tmp/python):
[...] [...]
$ $
Note that Modules/Makefile copies the original Setup file to the build Note that configure copies the original Setup file to the build
directory if it finds no Setup file there. This means that you can directory if it finds no Setup file there. This means that you can
edit the Setup file for each architecture independently. For this edit the Setup file for each architecture independently. For this
reason, subsequent changes to the original Setup file are not tracked reason, subsequent changes to the original Setup file are not tracked
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment