4 | | No. On Tiger, where some GNU Emacs builds took many hours' time, I created the patch – and port had no problem to apply it with those {{{..}} in the path! But the usual /usr/bin/make (3.80) failed at start, upon invocation, with that {{{virtual memory exhausted}}} report. Look at this: http://stackoverflow.com/questions/20286653/make-error-virtual-memory-exhausted-stop! And http://stackoverflow.com/questions/10903367/virtual-memory-exhausted-error. Gmake (4.1) managed to start, and failed later. Anyway, I can retry this in a few days (right now my PowerBook G4 is running Leopard). And also can try your steps. |
| 4 | No. On Tiger, where some GNU Emacs builds took many hours' time, I created the patch – and port had no problem to apply it with those {{{..}}} in the path! But the usual /usr/bin/make (3.80) failed at start, upon invocation, with that {{{virtual memory exhausted}}} report. Look at this: http://stackoverflow.com/questions/20286653/make-error-virtual-memory-exhausted-stop! And http://stackoverflow.com/questions/10903367/virtual-memory-exhausted-error. Gmake (4.1) managed to start, and failed later. Anyway, I can retry this in a few days (right now my PowerBook G4 is running Leopard). And also can try your steps. |