> Am 29.01.2018 um 23:21 schrieb Paul Rogers: > > I suggest you do as Bruce wrote. > Accepted, Paul. The problem is, that I can only perform "lscpu" on the > desktop in March, as I am not at home.
That *will* make it more difficult. ;-) How much do you know about the innards of your desktop? Do you know what CPU is? > > > And so it's *not* "working perfectly". > > I do not want to become philosophical. But for me, a system is working, > well, perfectly, if it is doing all the jobs it was designed for. > Compiling new programs do not belong to the normal tasks of a user, ok ? In my experience, computer bugs are like cockroaches: if you see one there are often others one must hunt for and squash. It's unpleasant. > ... The consequence > would be a "LFS" advice, that you are supposed to build the same LFS/ > BLFS system on each machine you own. from the scratch. > Is this what you mean ? Not quite. What I mean is, if one wants to build a "transportable" system one must be aware of the details of what one is building on, and what one wants it to run on. The build must be done with intention. For example, I specifically want to build my LFS systems to be transportable to any compatible CPU I may put it on. I have been building all of my i686 base systems to run on an original Pentium Pro--even though I've never had one--because it is the "lowest common denominator". I like to build on my 12GB 4 Hyperthreading Cores i7-940. So I must pay attention to, not only GMP, but also cross-compiling everything in LFS Ch. 6 as well as BLFS using "--target", if for no other reason that it's easier to put it in my build scripts and be reasonably confident, than worry about and have to go hunting up any bug that might have resulted otherwise. It also means for each package I read the docs looking for compatibility issues and run "./configure --help|less" so often I've made a "chl" alias for it. I didn't in a (B)LFS-7.7 build a while back, had some strange behaviors not unlike what you are describing, so went back and did it all over again "correctly"--one of the advantages of making scripts for each package build. There *may* be some specific packages that I can't build for the LCD, but when it comes to LFS I really want all of *that* to work flawlessly, and I happily accept any performance hit of the limited instruction set. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
