Mozilla SeaMonkey 2.53.17 download the new version for iphone

That's why I decided to exclude anything else from the port. The 'ONLY_FOR_ARCHS' thing: The upstream itself offers only amd64, so anything else isn't officially supported. But I always try to get them up & running, and I'm always in touch with the upstream (hoping that the releases aren't a big surprise, and the port is quickly updated). Here you can take a look my actal state on 2.53.17b1: īut I won't spent much time in those beta versions - far to much work has been done for nothing, as the releases differed. I get by with a little help from my friends. I couldn't put something like that together so I am pondering the responsibilities.īut as the Beatles said. Is this patch/method fragile or do you expect is will remain a static need for the port? So this was compilation failure at stage that needs gcc and you had to chase down what caused it? I see 'GCC' in name Just wondering how the software world works. This looks like a difference between LIBCPP on FreeBSD and Linux (except throw ios failure in end of patch) So as a porter not a programmer help me understand the patch here. What is: DISTVERSION= for the beta?Ģ.53.17b ? I see it called 2.53.17b1 by jmos ?ĭoes the memory patch still need applying?

Looking at Makefile for prior version I am removing the BUILD_DEPENDS line for python27. I don't like jails for doing stuff like this. The reason I want to start on aarch64 is we know amd64 beta builds already. Of course I need to build the beta on my own.īuild my own 'dedicated' FreeBSD git tree for the diff. I am building aarch64 box just for the cause.

Mozilla SeaMonkey 2.53.17 download the new version for iphone