On Wed, Oct 28, 2015 at 09:37:03PM -0400, Michael Havens wrote:
> boy am I glad I saved my build scripts! I sure did forget to do that!
If you were not scripting, and you had run the command recently
enough to be in your history, either using 'history | less' or just
repeatedly using the cursor-up
boy am I glad I saved my build scripts! I sure did forget to do that!
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which
On Wed, Oct 28, 2015 at 08:47:16PM -0400, Michael Havens wrote:
> error:
> checking for Tcl private include files... configure: error: Cannot find
> private header tclInt.h in /mnt/lfs/sources/tcl8.6.4
> I looked in the files config.log and the words 'private' and 'header' and
> 'error' do not occ
error:
checking for Tcl private include files... configure: error: Cannot find
private header tclInt.h in /mnt/lfs/sources/tcl8.6.4
I looked in the files config.log and the words 'private' and 'header' and
'error' do not occur in it. Am I inspecting the proper file? I'm looking in:
expect5.45/conf
okay. I'm not sure but I think I created nano /root/.bash_profile .
Should I delete it or does it matter. I don't think it matters.
--
:-)~MIKE~(-:
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above informati
What in the world? I could swear I read that it wen into bash_profile!
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which
On 29/10/2015 12:11 πμ, Michael Havens wrote:
The $LFS is set. I'm trying to set another variable
sources=$LFS/sources. it refuses to stay set.
lfs@debian:~$ cat ~/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
export LFS=/mnt/lfs
export sources=$LFS/sources
lfs@deb
The $LFS is set. I'm trying to set another variable
sources=$LFS/sources. it refuses to stay set.
lfs@debian:~$ cat ~/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
export LFS=/mnt/lfs
export sources=$LFS/sources
lfs@debian:~$ exit
exit
root@debian:~# su - lfs
lfs@deb
Michael Havens wrote:
I want to make it easy to get to a certain directory.
Why doesn't it retain $LFS/sources ?
root@debian:~# cat /root/.bash_profile
export LFS=/mnt/lfs
export sources=$LFS/sources
root@debian:~# su - lfs
lfs@debian:~$ cat ~/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1=
I want to make it easy to get to a certain directory.
Why doesn't it retain $LFS/sources ?
root@debian:~# cat /root/.bash_profile
export LFS=/mnt/lfs
export sources=$LFS/sources
root@debian:~# su - lfs
lfs@debian:~$ cat ~/.bash_profile
exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash
exp
Craig Garner wrote:
On Wed, Oct 28, 2015 at 10:26 AM, Michael Havens wrote:
I wrote the script for 5.10 and ran it but messed something up. I fixed it
and ran it again to find I did something else wrong
One of the last lines said:
ln: failed to create symbolic link `/tools/bin/cc': File exist
On 28/10/2015 05:25 μμ, Michael Havens wrote:
On Wed, Oct 28, 2015 at 11:00 AM, Pierre Labastie
mailto:pierre.labas...@neuf.fr>> wrote:
Two solutions:
- Use ln -sf (force)
- remove the link command from your script...
Thank you Pierre force option it is.
As for my first run havin
Yes, you are correct when you mentioned I have done LFS before but never
successfully. The reason I gave up in the previous try is the computer I
was sshing with blew up and so I had to put make the LFS machine my main
computer.
--
:-)~MIKE~(-:
--
http://lists.linuxfromscratch.org/listinfo/lfs-s
On Wed, Oct 28, 2015 at 11:00 AM, Pierre Labastie
wrote:
>
> Two solutions:
> - Use ln -sf (force)
> - remove the link command from your script...
>
Thank you Pierre force option it is.
As for my first run having already created it not really. It ran for lie 10
seconds and then barfed up the rest
On Wed, Oct 28, 2015 at 10:26 AM, Michael Havens wrote:
> I wrote the script for 5.10 and ran it but messed something up. I fixed it
> and ran it again to find I did something else wrong
> One of the last lines said:
>
> ln: failed to create symbolic link `/tools/bin/cc': File exists
>
> Do I nee
On 28/10/2015 15:29, Michael Havens wrote:
I think I do.
--
:-)~MIKE~(-:
I think you don't ;-)
A symbolic link (symlink) like the one you are talking about is a small
file pointing to another file. It just contains the name of that file,
but otherwise has nothing to do with its target. Th
I think I do.
>
> --
:-)~MIKE~(-:
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why i
I wrote the script for 5.10 and ran it but messed something up. I fixed it
and ran it again to find I did something else wrong
One of the last lines said:
ln: failed to create symbolic link `/tools/bin/cc': File exists
Do I need to delete this file before running it again?
--
:-)~MIKE~(-:
--
ht
-Original Message-
From: Bruce Dubbs
To: LFS Support List
Sent: Tue, 27 Oct 2015 22:27
Subject: Re: [lfs-support] section 5.5
Michael Havens wrote:
>
> If possible, it'd be better to make a difference between the source
> files (configure, *.c, etc) and the source packages (usual
19 matches
Mail list logo
