I think that may be the case. You’re also running Macports PPC binaries on Intel through Rosetta. I think a whole new toolkit would have to be compiled at the very least.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The Unofficial TenFourFox Development Toolkit
- Thread starter pipetogrep
- WikiPost WikiPost
- Start date
-
- Tags
- macports tenfourfox
- Sort by reaction score
- Status
@ActionRetro I wiped the macports-tiff prefix and reinstalled. I also made sure that the md5sum of what I uploaded to the garden matches my local build and it does. It is compiling on Leopard on a dual 1.8 GHz machine now. I’ll have results in about six hours.
Thank you!
Interestingly, I tried to compile on my PowerBook 1.5ghz and it compiled just fine overnight. So, something must be funky with my MDD's setup - even though both have the same version of XCode installed and both are running 10.5.8
I wonder what could be the difference?
Could you please run "echo $PATH" and tell me the result? Do you have TigerBrew installed as well? Which version of Xcode are you using? Which options did you choose when you installed Xcode?
Well, good news! I spent today hitting "y" every time the build failed to resume from the last point, and it did succeed in the end! I'm posting this from my own self-built TFF, which is awesome - thank you again for this script!
It is interesting that the build worked with no issues on my 1.5ghz 12" PowerBook, but had so many hiccups on my dual 2.0GHz MDD with 2gb RAM.
Below are the answers to your questions, in case it's helpful. Let me know if there's anything else I can provide or do to help. BTW, I'm going to talk about this in a video coming up, so hopefully if someone else sees these issues they will know there's a light at the end of the long compile time
Thank you again @pipetogrep ! I hope I can provide some help from my experience here
It is interesting that the build worked with no issues on my 1.5ghz 12" PowerBook, but had so many hiccups on my dual 2.0GHz MDD with 2gb RAM.
Below are the answers to your questions, in case it's helpful. Let me know if there's anything else I can provide or do to help. BTW, I'm going to talk about this in a video coming up, so hopefully if someone else sees these issues they will know there's a light at the end of the long compile time
- $PATH: /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
- Tigerbrew: Not installed on either MDD or PB 12"
- XCode: 3.1.4 on both MDD and PB 12", both are default installs from Macintosh Garden download #10 (https://macintoshgarden.org/apps/apple-xcode) - LMK if there's any more info I can provide about my installs.
Thank you again @pipetogrep ! I hope I can provide some help from my experience here
Odd. That all looks normal. The MDD is maxed out in RAM and the PowerBook has less than the MDD. How many times did you have to retry?
The main reason I added the retry is I was told having less than 4GB or RAM could cause issues but it sounds like your success/failure rate is consistent depending on the machine you are using.
At this point I do not know but I’m glad that it built! Maybe @wicknix or @alex_free might more insight on it. I wouldn’t have gotten any of this together without them.
Not gonna lie, I might **** kittens if I see the toolkit in a video so I’m looking forward to that. It took two weeks to cobble everything together and even longer to get it polished. Learning how make the installer, modifying the source code to work with a different prefix, finding and fixing logic errors (infinite loops in the build retry ?), but you know what goes into this kind of work. Every failed attempt took at least 3 hours. The point is, that would really be appreciated.
Anyways thanks again for your content, 68knews, and Frog Find! Please let me know if you have any other issues with the toolkit or ideas on how to make it better.
The main reason I added the retry is I was told having less than 4GB or RAM could cause issues but it sounds like your success/failure rate is consistent depending on the machine you are using.
At this point I do not know but I’m glad that it built! Maybe @wicknix or @alex_free might more insight on it. I wouldn’t have gotten any of this together without them.
Not gonna lie, I might **** kittens if I see the toolkit in a video so I’m looking forward to that. It took two weeks to cobble everything together and even longer to get it polished. Learning how make the installer, modifying the source code to work with a different prefix, finding and fixing logic errors (infinite loops in the build retry ?), but you know what goes into this kind of work. Every failed attempt took at least 3 hours. The point is, that would really be appreciated.
Anyways thanks again for your content, 68knews, and Frog Find! Please let me know if you have any other issues with the toolkit or ideas on how to make it better.
No idea why the dual failed. Faulty ram / ram slots maybe? The only reason a build could/would fail is if it runs out of ram, and osx by default has a very small swapfile. Otherwise i havent a clue.
Cheers
Cheers
@ActionRetro I think I'll include a flag that will do an optional auto-retry. It could do it something like 5 times before giving up.
Ok, so I ran it on a Mac Mini G4 (1.5GHz w/ 1GB RAM) after setting the
to always
, and then ran
for the 7450 and got:
Code:
yn_prompt
Code:
return 0
Code:
time /opt/macports-tff/bin/build_tenfourfox '/Users/reukiodo/TFF-build'
Code:
Exported to ~/Desktop/tenfourfox.app
/opt/macports-tff/bin
real 921m27.070s
user 521m54.379s
sys 65m0.441s
sh-3.2#
That is strange. I haven’t noticed that. It builds per the instructions on the TFF GitHub wiki so In not sure what would be different.
Thank you @pipetogrep for making this and putting forth the effort to keep PowerPC computers still useful in 2021. I ran it on my iBook G4 and it worked flawlessly!
It took about 2 days, but I wonder if that was due to it going to sleep every 15 minutes.
That sounds about right. You can prevent it from doing that in the energy saver settings.
I've deleted all the build data and am starting over with the automator script (as opposed to the command line) to see if that makes any difference. I dunno, but I guess I'll find out in another 15hrs.
I'm typing this on a TFF build I did on my powerbook overnight. Thanks to everyone who has contributed to this effort!
I guess my small contribution is to recommend that people turn off spotlight for the build folder. This seems to save a lot a CPU time.
Does anyone know if using newer versions of gcc to get LTO and PGO builds is a possibility?
I guess my small contribution is to recommend that people turn off spotlight for the build folder. This seems to save a lot a CPU time.
Does anyone know if using newer versions of gcc to get LTO and PGO builds is a possibility?