root:/sources# export CLFS=/
root:/sources# echo ${CLFS}
/
root:/sources# mkdir -pv ${CLFS}/{dev,proc,sys}
mount -vt proc proc ${CLFS}/proc
This will hangup the system.
Weird though, because after reboot again I do df and see:
root:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 97G 1.5G 90G 2% /
shm 2.0G 0 2.0G 0% /dev/shm
Did I set CLFS wrongly?
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Koornstra,
Reinoud
Sent: Friday, April 03, 2009 12:09 PM
To: CLFS Support
Subject: [Clfs-support] environment settings
Hi Everyone,
I noticed that I didn't have anything set exept for the BUILD64 as user root
when booting after section 7.
When I do gcc -v I see:
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.3.3/configure --prefix=/tools --disable-multilib
--build=i486-cross-linux-gnu --host=x86_64-unknown-linux-gnu
--target=x86_64-unknown-linux-gnu --libexecdir=/tools/lib
--with-local-prefix=/tools --enable-long-long --enable-c99 --enable-shared
--enable-threads=posix --disable-nls --enable-__cxa_atexit
--enable-languages=c,c++ --disable-libstdcxx-pch
Thread model: posix
gcc version 4.3.3 (GCC for Cross-LFS 4.3.3.20090312)
Can I just set export CC=gcc ?
Same for
export CC="${CLFS_TARGET}-gcc"
export CXX="${CLFS_TARGET}-g++"
export AR="${CLFS_TARGET}-ar"
export AS="${CLFS_TARGET}-as"
export RANLIB="${CLFS_TARGET}-ranlib"
export LD="${CLFS_TARGET}-ld"
export STRIP="${CLFS_TARGET}-strip"
Or should I just do it exactly as above and set CLFS_TARGET first as
x86_64-unknown-linux-gnu ?
Kind Regards,
Reinoud.
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
