But this probably is not my real question. I saw the notice about libssl and decided it was time to update things.
Updated kernel and system userland (5.6 stable). Forgetting what I was doing. My mind was shot, should not have had the hood up in the condition I was in. Instead of doing a pkg_add -u, I did a cvs up in /usr/ports. Got some updates, remember firefox and some other stuff among them. Started to just do make in /usr/ports, and it started sequencing through the archivers, installing things like cabextract, which I'm pretty sure I don't need. Thought it was trying to install everything. I stopped that with a ctrl-c and scratched my head, did a make clean and a pkg_check. Then tried a pkg_add -u and nothing gets added. I'm a bit worried about not updating firefox (31.0 to 31.5, if I read the text flying by on the screen right) even though it isn't specifically mentioned on the errata page. (Is it perhaps listed in the patches?) So I tried doing make update in www/firefox-esr, and it finds lots of things to update, then dies on a full disk. 1.6G for just /usr/ports, 104% in use. make clean brings it down to 50% use, and I've located a ballooning build within gcc 4.8.3, which firefox 31.5 requires. (Why, I wouldn't care to guess.) I thought gmp was the culprit, but trying to trap the culprit by teeing the output of make, it seems to get past that through some gnat-bind stuff and cp ecj-4.5.jar (bleaugh) and then a perl script that apparently tries to fix up some #defines related to GLIBCXX_HAVE_GETS and then starts in on patching. And patch-boehm-gc-dyn_load_c did not apply cleanly. And about five not-patched-cleanly patches later it reports no room left on the device. (I'm thinking about wiping each directory under lang/gcc and trying a cvs get there, but du seems to say the ballooned file is elsewhere.) I have another 5.6 box that is currently building the userland, for reference, but while I'm waiting, I thought I'd ask about the ballooning build. And if anyone cares to help me untangle my thinking, ... Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future.
