View Single Post
Posts: 284 | Thanked: 320 times | Joined on May 2010 @ Peterborough, UK
#49
Hi Qole,

Many thanks for the image you created yesterday, it's much appreciated. However I do have a problem qchroot'ing it, I get the following:

Code:
Nokia-N900-02-8:/home/user/MyDocs# qchroot maemo-sdk-v1_2.img.ext2 /sdk
Mounting...
using image file: maemo-sdk-v1_2.img.ext2
fs type is ext2
Using ext2 file system
mounting maemo-sdk-v1_2.img.ext2 on loop
...maemo-sdk-v1_2.img.ext2 mounted on loop0
.
mount: mounting /dev on /sdk/dev failed: No such file or directory
..
mount: mounting none on /sdk/dev/pts failed: No such file or directory
mount: mounting /dev/shm on /sdk/dev/shm failed: No such file or directory
...
....
mount: mounting /var/run/dbus on /sdk/var/run/dbus failed: No such file or directory
mount: mounting /var/lib/dbus on /sdk/var/lib/dbus failed: No such file or directory
mount: mounting /var/run/pulse on /sdk/var/run/pulse failed: No such file or directory
Everything set up, running chroot...
[root@maemo5_v1_2: /]
This then results in ./configure failing as so:

Code:
./configure: line 1: /dev/null: No such file or directory
./configure: line 74: /dev/null: No such file or directory
./configure: line 1: /dev/null: No such file or directory
./configure: line 83: /dev/null: No such file or directory
./configure: line 124: /dev/null: No such file or directory
./configure: line 136: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: line 242: /dev/null: No such file or directory
./configure: This script requires a shell more modern than all
./configure: the shells that I found on your system.
./configure: Please tell bug-autoconf@gnu.org and malattia@linux.it
./configure: about your system, including any error possibly output
./configure: before this message. Then install a modern shell, or
./configure: manually run the script under such a shell if you do
./configure: have one.
Anything I can do to fix this?