[Patches] Re: [Patch #101773] BeOS PPC lacks fseeko, but isn't MS Windows

[Donn Cave]

|   Mail regarding bugs is not attached to the bugs in any way
| (unfortunately); the SourceForge crew doesn't seem to want to add
| this.  ;(  The best way to comment on a bug is through the SF
| interface.

Bleah.

|> Here's my last message, have had no response.  I'm happy with anything
|> that allows this relatively obscure platform to get through the build
|> (this is the old Metrowerks + PowerPC BeOS platform, which is kind of
|> a thing of the past since no supported hardware has been made for years.)
|
|   Hmm... and it's running BeOS R5?  Or are these patches separate from
| the R5 patches?
|   If you could paste your mail into SourceForge for the comments, I'd
| really appreciate it!

OK, pasted.  Be has continued to support the platform for a limited time
as a legacy, so R5 works.  Actually I don't believe there's a single
thing in the patches I sent in Wednesday that has to do with R5, we
have the same issues on R4.5.2.

Most of the hassle is the Metrowerks compiler tools, on the PPC platform
but with some legacy there in how Be handles the Intel platform too, and
anyway some spillover of the PPC issues into the Python build and install
on Intel.  It hadn't been (Python 1.5) building on PPC, and it hadn't
been installing correctly on Intel either (dl_export.h in the wrong
directory, it should be in the includes)  ... despite all the junk in
configure to support it.

The "revise BeOS build" patches, need to be taken (or rejected) together,
or revised.  The rest can be taken separately.

	Donn Cave, donn@u.washington.edu