Re: [lfs-support] Broken link on "lfs-support Info Page"
On Mon, Jul 29, 2013 at 09:20:24PM +0100, Jeremy Henty wrote: > > The link "lfs-support Archives" > (http://linuxfromscratch.org/pipermail/lfs-support/) in "lfs-support > Info Page" (http://linuxfromscratch.org/mailman/listinfo/lfs-support/) > returns "Page not found!". > > Hang on, I guess that before I report this I should check the mailing > list archives ... **STACK LIMIT EXCEEDED** Not (yet) restored after the server migration. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Any reason to run "loadkeys" before building Linux?
On Mon, Jul 29, 2013 at 10:20:23PM +0200, Nio Wiklund wrote: > On 2013-07-29 22:10, Jeremy Henty wrote: > > > > My build scripts for Linux run > > > > loadkeys -v -m /lib/kbd/keymaps/i386/qwerty/uk.map.gz > \ > > drivers/char/defkeymap.c > > > > before running make. I am 99% sure that I copied that command from an > > old LFS, but the current version has no such instruction. Does anyone > > know why this changed? Does running "loadkeys" do anything useful > > these days? > > > > Regards, > > > > Jeremy Henty > > > I use it when running in text screens (when there is no graphical window > manager / desktop environment. > > Best regards > Nio In a normal LFS system, the LFS bootscripts will set up the keyboard (if you configured the console). Without that, ISTR that a system will come up (if you aren't using a login manager) with a USA keymap. I think the invocation during the kernel build was for when things went wrong (filesystem damage) or for using init=/bin/bash. I think using init=/bin/bash on a keyboard far distant from the american layout (e.g. QWERTZ or AZERTY) might be painful, but for normal recovery most people probably use a rescue CD or chroot from another install. I also have a vague memory that something in this area of the kernel might have changed - probably during the 2.6 timeframe - but I'm probably mistaken! For a GB keyboard, the US console keymap is not _too_ far off. I use my own uk variant (extra unicode, very different Compose - somewhat similar to en_GB Xorg for the accents - it's in ~/ken at lfs), and I don't remember if the default map has mappings for the pipe : I think it does, but not sure (AltGr something). # is of course on £, @ and " swap places. The \| key (to left of Z) is not operational in the US map - it's an extra key. Of course, mostly I live in Xorg and urxvt - I only really use the keyboard on my server occasionally - and *that* has an american keyboard, but with uk mappings (previous keyboard broke!) so the \| key is physically missing :) Can't check the map at the moment, I'm using my netbook which doesn't have my own keymap. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Error in Junit installation instructions?
On 29/07/13 15:25, Bruce Dubbs wrote: > > We need a url that can be used with wget. I couldn't find one at junit.org. Will this do the job? https://github.com/junit-team/junit/archive/r4.11.tar.gz David -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Any reason to run "loadkeys" before building Linux?
On 2013-07-29 22:10, Jeremy Henty wrote: > > My build scripts for Linux run > > loadkeys -v -m /lib/kbd/keymaps/i386/qwerty/uk.map.gz > \ > drivers/char/defkeymap.c > > before running make. I am 99% sure that I copied that command from an > old LFS, but the current version has no such instruction. Does anyone > know why this changed? Does running "loadkeys" do anything useful > these days? > > Regards, > > Jeremy Henty > I use it when running in text screens (when there is no graphical window manager / desktop environment. Best regards Nio -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Broken link on "lfs-support Info Page"
The link "lfs-support Archives" (http://linuxfromscratch.org/pipermail/lfs-support/) in "lfs-support Info Page" (http://linuxfromscratch.org/mailman/listinfo/lfs-support/) returns "Page not found!". Hang on, I guess that before I report this I should check the mailing list archives ... **STACK LIMIT EXCEEDED** -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Any reason to run "loadkeys" before building Linux?
My build scripts for Linux run loadkeys -v -m /lib/kbd/keymaps/i386/qwerty/uk.map.gz > \ drivers/char/defkeymap.c before running make. I am 99% sure that I copied that command from an old LFS, but the current version has no such instruction. Does anyone know why this changed? Does running "loadkeys" do anything useful these days? Regards, Jeremy Henty -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] make: gcc: Command not found - chap. 6.7.1
>root:/sources/linux-3.10.2# make mrproper >>make: gcc: Command not found > >When you encounter issues like these, don't rely on ldd. > > >Rely on readelf. > > >readelf -e /tools/bin/gcc | grep interpreter > > >or any other binary. > > >Especially when cross compiling, ldd isn't valid. Learn to use readelf. > > >If you know what the output should be when looking for the interpreter, you'll >be better off. > > >Usually if your interpreter is wrong with gcc or binutils after chroot, it >means that gcc source and/or build directories were not removed before the >next build. Dear William, ok, thank you also for your information! New manpage(s) to read.^^ Thanks, Seba -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] make: gcc: Command not found - chap. 6.7.1
On Jul 28, 2013, at 11:58 AM, Unix User wrote: root:/sources/linux-3.10.2# make mrproper make: gcc: Command not found When you encounter issues like these, don't rely on ldd. Rely on readelf. readelf -e /tools/bin/gcc | grep interpreter or any other binary. Especially when cross compiling, ldd isn't valid. Learn to use readelf. If you know what the output should be when looking for the interpreter, you'll be better off. Usually if your interpreter is wrong with gcc or binutils after chroot, it means that gcc source and/or build directories were not removed before the next build. Sincerely, WIlliam Harrington-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
