On Sun, Mar 13, 2016 at 10:42:24AM -0700, Paul Rogers wrote: > > Hi- > > > > You may already know this, but in my experience FF needs a fair bit > > of free disk space for the final link, and gives weird errors when > > it doesn't have enough (ones other than the more helpful "no space > > left on device"). > > > > -Andrew Warshall > > Thank you for the reply. > > Yes, I know it's big. I upgraded my 7.2 system to FF-35.0.1, and the > build directory at the end was ~5GB--can't say what it peaked at during > the build, of course. So it was time to spend the morning swapping > systems to get it from a 10GB partition to a 20. There are now 9.6GB > free, prebuild. I found I had to upgrade NSS/NSPR & sqlite for FF-38.7. > > As you suggest, the error itself implies to me a missing internally > generated constant at link time, which suggests to me that it isn't > something missing in my external environment, especially since that > string was found in other binary files. Seems more like a Mozilla > error, but it's confusing that it'd be in 38.1, .6, & .7, all in an > ESR version! (OTOH, blowing your configure file is kinda bonehead.) > > I just don't know what to do if not try 37 or 39. Since I'm likely to > live with this system for a while (I'm not planning on jumping a couple > more versions of LFS as soon as I finish), the 38esr had attractions.
According to wikipedia (not necessarily the most reliable source, but it was the best I could find), the current ESR releases are 38.7.0 and 45.0 ESR (I'm not sure, but I suppose that is identical to 45.0). That implies 38.7.0 is the last 38 release. And the next ESR after 45 will be 52. I've dropped my systems older than LFS-7.6 (glibc - I know you worked around that using /tools - but also I was not looking forward to upgrading systems where the openssl version reached EOL), but I used to have several older releases and they mostly were able to build the current release without too much difficulty. From time to time I had to upgrade icu, libpng, python2 and I always upgrade sqlite / nspr / nss / cacerts / libvpx to current. There was one old system where I got weird gcc failures and I eventually let it go (too much trouble to try to fix it). But those were all x86_64 so I have no recent experience on i686. I have to admit that my i686 netbook is now running the binary 45.0 : building whichever version was current for BLFS-7.6 took a really long time, probably because it has so little RAM, and now its battery has almost expired, so building things there is minimal (but I still upgrade openssl, nspr, nss). I know that you think you are safe because of your firewalling, but almost every new version of firefox includes vulnerability fixes. See https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ and please note the definition of Critical: Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. For esr, the link is https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox-esr/ And yes, this rebuilding is a pain - it comes with being our own sysadmin. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
