On Sat, May 26, 2018 at 03:37:47PM -0700, Paul Rogers wrote: > Build script needed a finishing ldconfig--perhaps my problem with the > previous FF build?
Possibly - when I have built a newer rust and installed it in /opt I run ldconfig. > > I don't like rust! It seems very un-UNIXlike. > Does anybody from a 'nix background like it ? > I'm concerned. If one watches the console or logs/reads the build, some very > scarey things fly by, e.g.: > > Downloading cc v1.0.4 > Downloading libc v0.2.39 > Downloading atty v0.2.6 > Downloading ar v0.3.1 > Downloading curl v0.4.11 > Downloading term v0.4.6 > Downloading openssl v0.9.23 !!!!! > Downloading diff v0.1.11 > Downloading hamcrest v0.1.1 > Downloading pkg-conf v0.3.9 Ah! Now I understand your comment about gcc and glibc. It downloads a series of crates (source tarballs) When you have a graphical browser, https://crates.io/crates/cc etc will point you to the latest versions. No idea how to access details for the older set-in-stone versions which any particular release downloads, but the summaries should still be accurate. The openssl crate is now in the 0.10 series, it really has no relationship to real openssl versions ;) > > It's almost enough to put one off using Firefox if that's what it takes! > Indeed - the maintained graphical browsers which can be built on recent LFS systems seem to be limited to chromium, anything using *current* webkit, anything using qtwebengine (falkon, née QupZilla which have never opened ftp:// links), or firefox and seamonkey. After using firefox, I found seamonkey hard to get used to - but it seems to follow upstream mozilla changes: according to https://www.seamonkey-project.org/releases/seamonkey2.49.3/ that version matches changes in firefox-52.7.3 ESR and Thunderbird 52.7.0. None of them are small or lightweight builds if you include their dependencies. I suppose there is also Basilisk which I mentioned the other day, but I've no idea what the vulnerability testing happens on that, nor how soon its devs become aware of mozilla fixes (it is based on older mozilla). > > I like old and stable. Remember the definition: "update: to take out old > bugs and put in new ones." It ain't funny!!! > For graphical browsers (and some other packages), exploits tend to circulate as soon as the CVE details are published - if not before. It ain't ideal, it's just the way things are. ĸen -- War is Peace Freedom is Slavery Ignorance is Strength -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
