On Wed, 2012-03-21 at 21:54 +0200, Alexander Kapshuk wrote:
(6). While still in $LFS/sources/gcc-build, I ran ln -sv ../usr/bin/cpp
/lib; And this is where I found it confusing, ../usr/bin/cpp ==
$LFS/sources/usr/bin/cpp; but /usr/bin/cpp isn't found in $LFS/sources.
It's found is $LFS/usr
On Thu, Mar 22, 2012 at 8:51 AM, Simon Geard delga...@ihug.co.nz wrote:
On Wed, 2012-03-21 at 21:54 +0200, Alexander Kapshuk wrote:
(6). While still in $LFS/sources/gcc-build, I ran ln -sv ../usr/bin/cpp
/lib; And this is where I found it confusing, ../usr/bin/cpp ==
$LFS/sources/usr/bin
On Tue, 2012-03-20 at 16:50 +0200, Alexander Kapshuk wrote:
So in other words, 'ln -sv ../usr/bin/cpp /lib' and 'ln
-sv /usr/bin/cpp /lib' are equivalent?
Not quite, and the difference can be seen when you look at the link
*outside* the chroot environment (i.e where the filesystem is mounted
/sources/gcc-build, I ran ln -sv ../usr/bin/cpp
/lib; And this is where I found it confusing, ../usr/bin/cpp ==
$LFS/sources/usr/bin/cpp; but /usr/bin/cpp isn't found in $LFS/sources.
It's found is $LFS/usr/bin/cpp; I thought that ln was supposed to create
a link to an existing file whether using
On Wed, Mar 21, 2012 at 09:54:18PM +0200, Alexander Kapshuk wrote:
(6). While still in $LFS/sources/gcc-build, I ran ln -sv ../usr/bin/cpp
/lib; And this is where I found it confusing, ../usr/bin/cpp ==
$LFS/sources/usr/bin/cpp; but /usr/bin/cpp isn't found in $LFS/sources.
It's found
Got it. Thanks.
It's relative to /lib, not $LFS/sources/gcc-build as I had thought
initially.
I'll have another look at ln(1).
On 03/21/2012 10:25 PM, Ken Moffat wrote:
On Wed, Mar 21, 2012 at 09:54:18PM +0200, Alexander Kapshuk wrote:
(6). While still in $LFS/sources/gcc-build, I ran
While working on '6.17.1. Installation of GCC', I created and cd'd into
'/sources/gcc-build'. One of the instructions suggests creating this
symlink, 'ln -sv ../usr/bin/cpp /lib'. I assumed that I was supposed to run
the command line while still in '/sources/gcc-build'. If that is the case
On Tue, Mar 20, 2012 at 7:41 AM, Alexander Kapshuk
alexander.kaps...@gmail.com wrote:
While working on '6.17.1. Installation of GCC', I created and cd'd into
'/sources/gcc-build'. One of the instructions suggests creating this
symlink, 'ln -sv ../usr/bin/cpp /lib'. I assumed that I was supposed
creating this
symlink, 'ln -sv ../usr/bin/cpp /lib'. I assumed that I was supposed to
run
the command line while still in '/sources/gcc-build'. If that is the
case,
shouldn't the command line be 'ln -sv ../../usr/bin/cpp'?
When the ln command is given two paths, the current directory does
of the instructions suggests creating this
symlink, 'ln -sv ../usr/bin/cpp /lib'. I assumed that I was supposed to
run
the command line while still in '/sources/gcc-build'. If that is the
case,
shouldn't the command line be 'ln -sv ../../usr/bin/cpp'?
When the ln command is given two paths
On Tue, 20 Mar 2012 14:55:28 +
Alexander Kapshuk alexander.kaps...@gmail.com wrote:
So in other words, 'ln -sv ../usr/bin/cpp /lib' and 'ln -sv /usr/bin/cpp
/lib' are equivalent?
ln -sv ../usr/bin/cpp /lib is a relative symbolic link.
ln -sv /usr/bin/cpp /lib is an absolute symbolic link
Clemens Haupt wrote:
On Sunday 22 January 2006 12:30, you wrote:
man bash
Danke!
When the lfs partition is mounted, all ln -s are here again
Where is that stored?
Kind regards
Clemens
I don't know what you mean. Where is what stored?
--
http://linuxfromscratch.org/mailman/listinfo/lfs
On 6/28/05, Stephen Liu [EMAIL PROTECTED] wrote:
Hi Andrew,
snip
# chown lfs $LFS/sources
chown: cannot access `/sources': No such file or
directory
I'm held here again. Any advice?
When you su you load a new environment, and your $LFS variable is
lost, so the chown is attempting
Hi Steve,
Tks for your advice.
- snip -
When you su you load a new environment, and your
$LFS variable is
lost, so the chown is attempting to access /sources,
instead of
/mnt/lfs/sources.
do a export LFS=/mnt/lfs and run the chown again.
Continued proceeding as follows;
# export
On 6/28/05, Stephen Liu [EMAIL PROTECTED] wrote:
snip
bash: umash: command not found
lfs:~$
Up to here I have no idea whether I have committed any
mistake because no indication of success.
What is bash: umash: command not found? Is it a
WARNING?
You've made a typo - that should be
Hi Steve,
What is bash: umash: command not found? Is it a
WARNING?
You've made a typo - that should be umask, not
umash. When you run
the source command, bash is reporting that it
cannot find any
command called umash.
I re-checked the printout on Konsole;
...
.
-bash-3.00$
Hi Kevin,
Tks for your advice.
- snip -
Well, it is supposed to be umask not umash.
cat ~/.bashrc EOF
set +h
umask 022
LFS=/mnt/lfs
LC_ALL=POSIX
PATH=/tools/bin:/bin:/usr/bin
export LFS LC_ALL PATH
EOF
Ah, I realize that I made a typing mistake on umask
I did it again as follows;
Hi Kevin,
Tks for your advice.
- snip -
Well, it is supposed to be umask not umash.
cat ~/.bashrc EOF
set +h
umask 022
LFS=/mnt/lfs
LC_ALL=POSIX
PATH=/tools/bin:/bin:/usr/bin
export LFS LC_ALL PATH
EOF
Ah, I realize that I made a typing mistake on umask
I did
18 matches
Mail list logo
