Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

barracuda156

macrumors 68000
Sep 3, 2021
1,595
1,187
thanks! I fear I'm missing something - when I type the command 'diff -u configure.old configure' in the /opt/local/var/macports dir it can't find the file configure and looking around I can't see where that may be? sorry for the noob question - clearly learning how macports works as I go

That does not work this way.

You have to either manually edit the file, like:
sudo port -v patch m4 (so that all existing patches are applied and you do not get errors).
Then go to the folder where sources are extracted, edit what you need in BBEdit or whatever code editor you have (Xcode will also do, but you have to set writable preferences on the folder, otherwise it won’t let you change it), then do sudo port -v install m4.

Or make a patch, put in into m4/files directory (make it if there is none), add a line in the portfile so that the patch is used:
patchfiles-append PATCHNAME.

I think as a one-time solution manual editing is easier.

Or I can make a patch for you and edit the portfile, but you will need to either overwrite existing one with edited version or make a local repo (the latter option is a correct long-term solution for custom portfiles).
Some info is here: https://guide.macports.org/chunked/development.local-repositories.html
Also: https://forums.macrumors.com/thread...0-6-powerpc-10a190-and-10-6-8-rosetta.2332711
 
  • Like
Reactions: xantufrog

cellularmitosis

macrumors regular
Mar 6, 2010
143
238
thanks! I fear I'm missing something - when I type the command 'diff -u configure.old configure' in the /opt/local/var/macports dir it can't find the file configure and looking around I can't see where that may be? sorry for the noob question - clearly learning how macports works as I go
the configure.old filename is probably just a misnomer -- that's just the name of one of the files used to create the patch, it won't be present on your system.

you'll probably want to run 'patch < filename.patch
'

ignore me, I missed barracuda's post :)
 

xantufrog

macrumors regular
Original poster
Jul 7, 2023
130
132
That does not work this way.

You have to either manually edit the file, like:
sudo port -v patch m4 (so that all existing patches are applied and you do not get errors).
Then go to the folder where sources are extracted, edit what you need in BBEdit or whatever code editor you have (Xcode will also do, but you have to set writable preferences on the folder, otherwise it won’t let you change it), then do sudo port -v install m4.

Or make a patch, put in into m4/files directory (make it if there is none), add a line in the portfile so that the patch is used:
patchfiles-append PATCHNAME.

I think as a one-time solution manual editing is easier.

Or I can make a patch for you and edit the portfile, but you will need to either overwrite existing one with edited version or make a local repo (the latter option is a correct long-term solution for custom portfiles).
Some info is here: https://guide.macports.org/chunked/development.local-repositories.html
Also: https://forums.macrumors.com/thread...0-6-powerpc-10a190-and-10-6-8-rosetta.2332711
Awesome, thanks for walking me through it!
 
  • Like
Reactions: barracuda156

f54da

macrumors 6502
Dec 22, 2021
337
125
If you decide to write for the Python which came with the system, I have some links to the original docs on my Leopard Apple Developer Connection docs website: https://leopard-adc.pepas.com/

The Python docs are at the bottom in "Other Docs"
Thank you for this, I've been looking for an archive of the old apple developer documentation. Have you considered uploading this to the Internet Archive so it can be preserved better? Otherwise, would you be willing to upload a torrent of the entire directory?

Your mirror is even more recent than the one I'd been using up until now: https://web.archive.org/web/20160131002259/http://mirror.informatimago.com/next/developer.apple.com/

Btw I also see references to offline docsets downloaded via Xcode (https://gist.github.com/fzwo/01d62cebd21032683d87f51d094575d3 ); do you know if those are the same as what's on your page?
 
Last edited:

cellularmitosis

macrumors regular
Mar 6, 2010
143
238
Thank you for this, I've been looking for an archive of the old apple developer documentation. Have you considered uploading this to the Internet Archive so it can be preserved better? Otherwise, would you be willing to upload a torrent of the entire directory?

Your mirror is even more recent than the one I'd been using up until now: https://web.archive.org/web/20160131002259/http://mirror.informatimago.com/next/developer.apple.com/

Btw I also see references to offline docsets downloaded via Xcode (https://gist.github.com/fzwo/01d62cebd21032683d87f51d094575d3 ); do you know if those are the same as what's on your page?

Sure!

It is actually github pages serving this repo: https://github.com/cellularmitosis/ADC-reference-library-2009-july

(leopard-adc.pepas.com just points to cellularmitosis.github.io via DNS)

This repo was created by
The whole thing is only 18 commits if you want to just read through it.

I'm lucky github doesn't consider this abuse, the repo is something like 8 gigs.

I should add a link to the github repo from the website! If you are on a modern PC, reading through the sample source code directly in the browser is pretty convenient.

EDIT: forgot to answer your question! The easiest way to preserve it would be to just hit the fork button in github. That way, even if github deletes my account for some reason, you still have a fork of it.
 

f54da

macrumors 6502
Dec 22, 2021
337
125
Thanks, that's really neat that it's just on github (easy to download a zip), surprised google searches didn't turn this up earlier. For archiving I'd recommend just cloning a copy (or zip) as opposed to forking, github has been known to remove forks in the past when doing DMCA or abuse takedowns.

Any reason why you used the July 2009 version instead of the last one (Dec 2009)?

Btw I also went through the offline xcode docsets and they at least seem to contain many of the same documentation (I don't know if it's only a subset or if it's 1:1 though). The size discrepancy between the xcode docsets and your repo is a bit interesting but that might be due to the PDF files in the latter inflating the size.

Put together, I think the following will thus give you the most complete set of documentation up until Apple stopped writing detailed docs.

  • Your https://leopard-adc.pepas.com/ for core ADC material up to Leopard
  • XCode Docsets: Snow Leopard (Mac OS X 10.6 Core Library (v409.200.0)) and Legacy Reference (Mac OS X Legacy Library (v10.0.0)) gives you a snapshot of the ADC Conceptual+Reference+TN docs up to Snow Leopard
  • 10.9 Docset (gives you snapshot of Conceptual + Reference + TN docs up to 10.9)

Other odds and ends: The informatigo mirror, which contains misc material from 10.0-10.4 that the above don't seem to have (things such as info on 2-level namespacing). The actual server is now offline, but most of it is on the Wayback Machine. I actually have a copy of this entire site (it's about 5GB), I need to see if I can upload the directory to IA sometime.


If something is missing from the above, can try other resources at https://github.com/dgelessus/mac_file_format_docs
 

cellularmitosis

macrumors regular
Mar 6, 2010
143
238
Thanks, that's really neat that it's just on github (easy to download a zip), surprised google searches didn't turn this up earlier. For archiving I'd recommend just cloning a copy (or zip) as opposed to forking, github has been known to remove forks in the past when doing DMCA or abuse takedowns.

Any reason why you used the July 2009 version instead of the last one (Dec 2009)?

Btw I also went through the offline xcode docsets and they at least seem to contain many of the same documentation (I don't know if it's only a subset or if it's 1:1 though). The size discrepancy between the xcode docsets and your repo is a bit interesting but that might be due to the PDF files in the latter inflating the size.

Put together, I think the following will thus give you the most complete set of documentation up until Apple stopped writing detailed docs.

  • Your https://leopard-adc.pepas.com/ for core ADC material up to Leopard
  • XCode Docsets: Snow Leopard (Mac OS X 10.6 Core Library (v409.200.0)) and Legacy Reference (Mac OS X Legacy Library (v10.0.0)) gives you a snapshot of the ADC Conceptual+Reference+TN docs up to Snow Leopard
  • 10.9 Docset (gives you snapshot of Conceptual + Reference + TN docs up to 10.9)

Other odds and ends: The informatigo mirror, which contains misc material from 10.0-10.4 that the above don't seem to have (things such as info on 2-level namespacing). The actual server is now offline, but most of it is on the Wayback Machine. I actually have a copy of this entire site (it's about 5GB), I need to see if I can upload the directory to IA sometime.


If something is missing from the above, can try other resources at https://github.com/dgelessus/mac_file_format_docs

Ah thank so much for these additional links!

I went with July 2009 because it was the last useable month before they updated everything for Snow Leopard (I was specifically looking for the latest docs on Leopard, being a PowerPC fanboy). I think August was actually Leopard as well but there was some problem with it, I can't remember specifically what now.

Good point about DMCA's, etc. Apple could probably get the repo removed entirely. I'll upload a zip to IA.

I remember also looking at the docset which came with Xcode, but discovered the ADC DVD seemed to contain more stuff, I don't remember specifically whether it was sample code or articles, etc.

I also recently made an archive of all of the WWDC videos from 2000 through 2004 (the last year they gave out DVD's at WWDC), and I was absolutely dismayed that most of the videos from 2005 to around 2007 are now basically offline forever. Presumably someone at Apple has a copy of them, but they've removed them from the website and no one seems to have a copy of them. Infuriating.

I started uploading those to YouTube but I only got about 8 videos in before I got a copyright strike, lol. Bad idea.
 

cellularmitosis

macrumors regular
Mar 6, 2010
143
238
Ah, from my notes:

Code:
cell@indium$ cat adc.md
# ADC: Apple Developer Connection

Xcode comes with a bunch of documentation HTML pages, which include links to
download sample source code.  Unfortunately, at least for Tiger / Leopard,
all of these links appear to be down, and wayback doesn't have them.

Luckily, macintoshrepository.org has a collection of Apple Developer Connection
disk images, which appear to have the sample code.

However, this appears to have been a monthly mailing kind of thing, so now
it is a matter of downloading dozens of DVD images and sorting through all
of it.

- DLED ADC 2007 Sep DVD (tiger)
- DLED ADC 2007 Oct DVD (tiger)
- INPROG ADC 2007 Nov DVD (?)
- DLED ADC 2009 Jan DVD (leopard)
- DLED ADC 2009 Jul DVD (leopard)
- DLED ADC 2009 Aug DVD (leopard) (i/o errors, re-dl'ing from archive.org)
- DLED ADC 2009 Sep DVD (snow leopard)
- DLED ADC 2009 Dec DVD (snow leopard)

"DLED" indicated "downloaded", looks like I was still in the process of downloading Nov 2007 at the last edit of that note file.

Looks like there was some problem with the August archive file, and I think I decided that July was good enough -- they likely didn't change anything about their API's in the last month before releasing Snow Leopard.
 

xantufrog

macrumors regular
Original poster
Jul 7, 2023
130
132
That does not work this way.

You have to either manually edit the file, like:
sudo port -v patch m4 (so that all existing patches are applied and you do not get errors).
Then go to the folder where sources are extracted, edit what you need in BBEdit or whatever code editor you have (Xcode will also do, but you have to set writable preferences on the folder, otherwise it won’t let you change it), then do sudo port -v install m4.

Or make a patch, put in into m4/files directory (make it if there is none), add a line in the portfile so that the patch is used:
patchfiles-append PATCHNAME.

I think as a one-time solution manual editing is easier.

Or I can make a patch for you and edit the portfile, but you will need to either overwrite existing one with edited version or make a local repo (the latter option is a correct long-term solution for custom portfiles).
Some info is here: https://guide.macports.org/chunked/development.local-repositories.html
Also: https://forums.macrumors.com/thread...0-6-powerpc-10a190-and-10-6-8-rosetta.2332711
Am I right that the "patch" is just that one line in the configure file to essentially ignore an error check contingency:
from "if (! bug_possible)"
to "if (1)"?

This didn't fix the issue for me (was able to overwrite the file fine) but I feel like there's more to it and I'm (probably) being dense
 

barracuda156

macrumors 68000
Sep 3, 2021
1,595
1,187
Am I right that the "patch" is just that one line in the configure file to essentially ignore an error check contingency:
from "if (! bug_possible)"
to "if (1)"?

This didn't fix the issue for me (was able to overwrite the file fine) but I feel like there's more to it and I'm (probably) being dense

If you could share the build log, as well as exact change which was applied (if different from the patch in the thread), that would be helpful. Perhaps better directly on Trac, so that not only myself will be aware of the issue.
 
  • Like
Reactions: xantufrog

xantufrog

macrumors regular
Original poster
Jul 7, 2023
130
132
If you could share the build log, as well as exact change which was applied (if different from the patch in the thread), that would be helpful. Perhaps better directly on Trac, so that not only myself will be aware of the issue.
Here is the log and the config I attempted to use - replicated it on the ibook with a fresh macports setup so I think it's definitely something to do with my configuration being wrong (or the patch no longer being adequate). Thanks again for your guidance!
 

Attachments

  • m4error.zip
    269.6 KB · Views: 27
Last edited:

barracuda156

macrumors 68000
Sep 3, 2021
1,595
1,187
I got lapack and fftw built, but I'm running into trouble with numpy under python3.

Edit: I am also just now remembering that my python2 build was just an initial bare-bones effort. In particular, it doesn't have the SSL module, which as it turns out means you can't install pip :(

The python 3 package is currently much more fully fleshed out, but I'm not opposed to revisiting the python2 package.

By the way, I have fixed both numpy and scipy. Current versions should build with Pythons < 3.12 (and 3.12 too until switched to handicapped mesonbuild, which needs still to be fixed).
 
  • Love
Reactions: cellularmitosis
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.