Re: [lfs-support] Rather a lot of glibc check errors
On Sat, 16 Jun 2018 23:03:05 +0800 Xi Ruoyao wrote: > On 2018-06-16 15:16 +0100, Ken Moffat wrote: > > > Interestingly gmp and mpfr both identify my machine as > > > "nano-pc-linux-gnu" rather than x86_64-pc-linux-gnu, so Bruce > > > is sort-of right when he calls it a different architecture. They both set > > > themselves up to run with -march=nano > > > -mtune=nano. What glibc thought it was building on, I have no idea, as I > > > couldn't find a config.guess script in the > > > package. > > > > > > > I'm surprised by nano-pc-linux-gnu. > > No surprise here. GMP's config.guess is special. It outputs > "ivybridge-pc-linux-gnu", > "skylake-pc-linux-gnu", "k8-pc-linux-gnu" etc. > > "uname -m" would still output "x86_64". > -- > Xi Ruoyao -- Update: in spite of the sheaf of math errors in glibc, I did finally arrive at a bootable system. I ran "make check" on every package (something I don't usually do these days) and, with one exception, saw nothing very unusual. Just the odd test failing that should have passed and the odd test passing that (according to the book) should have failed. The exception was when I was checking gettext and it kept crashing. The kernel log showed segfaults in glibc. I was low on power at the time; when I recharged fully and ran the tests again, everything went smoothly. So it seems there may be some instability in my glibc after all but it only manifests at low power. I can live with that. -- Hazel -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Booting LFS with systemd
On Fri, 29 Jun 2018 01:25:29 -0400 Michael Shell wrote: > On Thu, 28 Jun 2018 16:06:00 +0800 > Xi Ruoyao wrote: > > > Now I only use "initrd" directive to update CPU microcode and fix the > > buggy ACPI DSDT of my laptop (another sad story). > > > . > > And as there now seems to be several people who suffer with the >ACPI DSDT driver bug, you guys should make sure upstream is aware > of the problem, if they aren't already. > ... > > Cheers, > > Mike > > -- I did a git bisect on my system, but I couldn't make much sense of the result. The commit it finally settled on didn't seem to have anything to with acpi. [quote] Bisecting: 2 revisions left to test after this (roughly 1 step) [9af9b94068fb1ea3206a700fc222075966fbef14] x86/cpu/AMD: Handle SME reduction in physical address size Bisecting: 0 revisions left to test after this (roughly 1 step) [33c2b803edd13487518a2c7d5002d84d7e9c878f] x86/mm: Remove phys_to_virt() usage in ioremap() Bisecting: 0 revisions left to test after this (roughly 0 steps) [7744ccdbc16f0ac4adae21b3678af93775b3a386] x86/mm: Add Secure Memory Encryption (SME) support [unquote] I sent the result to the kernel acpi development list but never got an answer. If someone else on this list wants to try, I can send him my complete bisect logs. -- Hazel -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Please consider adding --with-gcc-arch=native in libffi configure
On Fri, 29 Jun 2018 20:32:37 -0400 Don Cross wrote: > I built LFS using jhalfs and the 8.2 version of the book on a machine with > an Intel G860 processor. The configure script for libffi guessed wrong > about the processor's capabilities, causing Python 3 to crash with an > invalid instruction exception. FWIW, I did file a bug report with libffi's developers: https://sourceware.org/ml/libffi-discuss/2018/msg00033.html Mailing list and contact info here: https://sourceware.org/libffi/ However, there hasn't been any reply, so far. At the very least, maybe there should be a warning message about this issue on the LFS libffi page, including noting that it will typically manifest as a python illegal instruction crash, which can happen when building meson. Cheers, Mike Shell -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Booting LFS with systemd
On 06/28/2018 09:54 PM, Thanos Baloukas wrote: On 28/06/2018 10:44 μμ, Frans de Boer wrote: On 06/28/2018 04:21 PM, Hazel Russman wrote: On Thu, 28 Jun 2018 16:06:00 +0800 Xi Ruoyao wrote: On 2018-06-28 01:08 -0400, Michael Shell wrote: On Wed, 27 Jun 2018 14:42:47 -0700 Paul Rogers wrote: If that's true, even with systemd, why is there any need to build an initramfs for a known system? I had used initramfs to setup a loopback device and boot the system in an image. But it seems grub can handle loopback device (though I've never tried). Just like you, I build everything I need into a custom kernel and avoid the need for an initramfs. One other reason people use initramfs is if they need udev services on boot, say, for a drive the kernel will not be able to find via a simple specification of root=/dev/X. I think people should not go through all the initramfs trouble just for LABEL= or UUID= functionality, but rather should just use PARTUUID= which the kernel natively understands. Agree. Now I only use "initrd" directive to update CPU microcode and fix the buggy ACPI DSDT of my laptop (another sad story). -- Xi Ruoyao School of Aerospace Science and Technology, Xidian University -- Nice to know someone else does this. I use an initrd on my main machine for precisely these two purposes. I had hoped that rewriting the acpi dsdt to remove some reported errors would allow me finally to boot the latest kernels, which are giving me panic in the acpi driver, but no such luck! Mind you, I'm not using systemd. Great, new development, now I can't even install systemd due to the next error: ... RuntimeError: File 'man/binfmt.d.5' could not be found FAILED: meson-install When looking for the missing file, I only found 'man/binfmt.d.xml'. I also refreshed the two systemd-238 packages to exclude a fallen bit, to no avail. Any suggestion where this might come from? Did you extract the man pages? tar -xf /path/to/systemd-man-pages-238.tar.xz Shoot, I had commented that out for another test :( Thnx. And the story continues. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
