On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the dynamic
linker in /lib. Then verify you actually have all the right libraries
for Ncurses: ls -la
This is my first attempt to set up a LFS. I have used Version
SVN-20121122 for this. I have just finished the book with the given
instructions except following two.
1. Instead of preparing my LFS partition to be ext2 or ext3, I chose
it to be ext4.
2. I didnt install LFS grub, instead I
On Dec 1, 2012, at 6:06 AM, Sagar Padhye wrote:
The EXT4 is compiled as kernel module.
That is your problem. To mount the rootfs, the filesystem to mount
rootfs needs to be built in the kernel and not as a module.
Sincerely,
William Harrington--
--- Em sáb, 1/12/12, Sagar Padhye escreveu:
De: Sagar Padhye
Assunto: [lfs-support] Not able to boot LFS : ext4 partition
Para: lfs-support
Data: Sábado, 1 de Dezembro de 2012, 9:06
This is my first attempt to set up a
LFS. I have used Version
SVN-20121122 for this. I have just finished
On Dec 1, 2012, at 4:59 AM, Simon Geard wrote:
Basically, I'm hoping that someone more familiar than me with the
toolchain can tell me how a chapter 6 package (bash) might be linked
against a library not installed in chapter 6 (the non-wide version of
ncurses). The obvious answer is that it's
On Nov 30, 2012, at 5:37 AM, Simon Geard wrote:
/bin/bash: error while loading shared libraries: libncurses.so.5:
cannot
open shared object file: No such file or directory
Do you also get the same problem when running /bin/more /sbin/cfdisk
and /usr/bin/cal ?
Those are installed by
On 12/01/2012 06:30 PM, William Harrington wrote:
On Dec 1, 2012, at 6:06 AM, Sagar Padhye wrote:
The EXT4 is compiled as kernel module.
That is your problem. To mount the rootfs, the filesystem to mount
rootfs needs to be built in the kernel and not as a module.
Sincerely,
William
On Sat, Dec 01, 2012 at 11:59:07PM +1300, Simon Geard wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the dynamic
linker in /lib. Then verify you actually
On Sat, 01 Dec 2012 23:59:07 +1300
Simon Geard delga...@ihug.co.nz wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of course, this should say that it's looking for the
dynamic linker in /lib. Then verify
On Sat, 1 Dec 2012 16:19:38 +0100
Aleksandar Kuktin akuk...@gmail.com wrote:
On Sat, 01 Dec 2012 23:59:07 +1300
Simon Geard delga...@ihug.co.nz wrote:
On Fri, 2012-11-30 at 11:17 -0500, Chris Staub wrote:
First, check how Bash is linked: readelf -l /bin/bash | grep
interpret. Of
On Sat, 1 Dec 2012 16:24:08 +0100
Aleksandar Kuktin akuk...@gmail.com wrote:
I mean `ldd /path/to/bash/that/is/the/problem/bash'.
Also, there is an easy way to test if the problem is linking with a
library from /tools. Make a symlink.
ln -sv /usr /tools
Then try it again.
Or maybe
On Sat, 2012-12-01 at 16:19 +0100, Aleksandar Kuktin wrote:
Can you do `ldd /bin/bash'?
Oddly, no. I can't use ldd because that's a shell script depending
on /bin/sh working, but if I run:
/lib/ld-linux-x86-64.so.2 --list /bin/bash
...I get:
/bin/bash: error while loading shared libraries:
On Sat, 2012-12-01 at 07:27 -0600, William Harrington wrote:
On Nov 30, 2012, at 5:37 AM, Simon Geard wrote:
/bin/bash: error while loading shared libraries: libncurses.so.5:
cannot
open shared object file: No such file or directory
Do you also get the same problem when running
Hello all,
Just built two systems, one of HLFS-development and one LFS-7.2.
Not sure what I did wrong, but neither system would successfully mount
/dev/pts or /dev/shm on bootup - both were complaining about
nonexistant mount points. After searching the web for a few hours, I
came across
On 12/02/2012 01:02 AM, d...@fluidnetwork.com wrote:
Hello all,
Just built two systems, one of HLFS-development and one LFS-7.2.
Not sure what I did wrong, but neither system would successfully mount
/dev/pts or /dev/shm on bootup - both were complaining about
nonexistant mount points.
15 matches
Mail list logo
