tenfourfox: I want to bring back PPC port, anyone eager to do i386?

[barracuda156]

Ken, I have your old i386 portfile for Tenfourfox, updated it today with current TFF versions and amended settings to build for PPC. It seems to work, compilation running (takes forever, since I am away from Quad and building on Dual 2.3 with no SSD and 1/3 of the RAM). But I expect it either to be successful or fixable with moderate efforts.

While it is likely rather straightforward to change build arch to i386 (basically updating your patches, if the source code changed, and reproducing i386 section as it was), it is not feasible for me to test i386 builds.

I hope no one gonna object against having TFF as PPC-only (after all, it is developed primarily for PPC), but if you or someone is interested to take care of Intel part, we can make it as dual-arch.

[kencu (Ken)]

Because it takes so long to build, in the end I just had a running clone of the repo, all built. Then I would pull Cameron's changes, the build system could figure out what needed to be rebuilt, and it would take 1/100th the time to build that way.

So I personally gave up (more or less) on the MacPorts' Portfile build, as that was always a "from scratch" build, there are no buildbots for Tiger, where I was building it, etc.

I also didn't get much enthusiasm for it, when I suggested it as a port 4 or 5 years back, and rightly enough, I guess.

Best of luck!

[barracuda156]

Replying to kencu:

Because it takes so long to build, in the end I just had a running clone of the repo, all built. Then I would pull Cameron's changes, the build system could figure out what needed to be rebuilt, and it would take 1/100th the time to build that way.

So I personally gave up (more or less) on the MacPorts' Portfile build, as that was always a "from scratch" build, there are no buildbots for Tiger, where I was building it, etc.

I also didn't get much enthusiasm for it, when I suggested it as a port 4 or 5 years back, and rightly enough, I guess.

Okay, I understood. Then I gonna propose it as PPC-only.

Latest-commit version has built perfectly fine on 10A190 (against 10.4 SDK) and works normally, I will build it on 10.5.8 next, adding stip, if everything is smooth, gonna make a PR. (I believe officially supported OSs won’t have problems, if even unsupported worked.)

It is really unfortunate that ppc64 is not supported with TFF, that would be a much better browser for Leopard :(

We have nothing that can be built for 64-bit, right? WebKit2 is broken, Chromium-legacy is Intel-only.

Best of luck!

Thank you! And thanks for the portfile, it is really helpful.

[barracuda156]

Replying to kencu:

Do you think TFF can be made to use Macports versions of icu, brotli etc.? It builds a bunch of stuff which we have already, it would save substantial amount of time not to build everything again (and also we have newer versions of those).

[kencu (Ken)]

I think it is possible, but the code and vintage of the codebase may make it difficult to find versions that interact well with TFF and also build on the desired systems.

I considered it myself at one point, so might be worth a bit of work to factor it out like that.

[barracuda156]

Replying to kencu:

I think it is possible, but the code and vintage of the codebase may make it difficult to find versions that interact well with TFF and also build on the desired systems.

I considered it myself at one point, so might be worth a bit of work to factor it out like that.

Thank you, I will look into that.

I have rebuilt TFF now with strip option on (using strip7 from your portfile – only master site URLs had to be changed). On the Quad it is pretty fast, less than 3 hrs.

Looks like I have also fixed i2pd – some settings in portfile need fine-tuning, but it finally not just builds and starts, but connects too.

What I want in result is having TFF with i2p and tor support. So far looks pretty feasible.