I am using lfs-6.1.1-4 and everything has gone extremely well until
about 6.17: mktemp-1.5. I then noticed that the arrow keys for use
with bash history were not working as expected; I could scroll
backwards without problem but scrolling forwards would not allow me to
get the whole way to the blank
Barrie Stott wrote:
1. Should I expect bash history to work without problem at this point?
I ask this because I already have an example where bash is not working
normally. Outside of lfs I can type the following and the bell rings:
echo $'\a'. I wanted to use this with lfs to tell me when some jo
Many thanks, Chris.
On Thu, Jun 01, 2006 at 10:50:29AM -0400, Chris Staub wrote:
> Actually that is exactly the way bash should work at that point.
That is what I wanted to know. I can now press on knowing nothing is
wrong rather than worry about a non-existent error.
> I don't
> really see the
-Original Message-
From: [EMAIL PROTECTED] on behalf of Kevin Alm
Sent: Thu 6/1/2006 4:50 PM
To: BLFS Support List
Subject: Re: A grubby question - the menu.lst statements
>Hmmm, well you learn something new every day. Never tried to use root
>(hdn,m) to select a kernel. To do that I've
Dan Nicholson wrote these words on 06/01/06 14:08 CST:
> On 6/1/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>> Notice below there are several libs Firefox "can't find". However,
>> it runs perfectly because it has internal knowledge of the whereabouts
>> of the libs.
>> [snip]
>
> Not exactly "i
On 6/1/06, Tasos Drosopoulos <[EMAIL PROTECTED]> wrote:
I'm currently building BLFS and have reached kdeadmin. Compilation stops
with the message that libGL.la is required.
Could you show the errors? It shouldn't be required, although I have
to be honest that I don't build KDE.
Mesa-6.5 (pe
On Thu, 2006-06-01 at 13:50 -0500, Randy McMurchy wrote:
> Notice below there are several libs Firefox "can't find". However,
> it runs perfectly because it has internal knowledge of the whereabouts
> of the libs.
Oof, what a terrible example I picked! That happens to work for me
because I inclu
Hello,
The first command in chapter 6.37.1 of lfs 6.1.1 is:
tar -xvf ../bash-doc-3.0.tar.gz &&
however the package i downloaded from a mirror ftp-server is named
"bash-doc-3.0.tar.bz2" and not "*.gz"
The command should thus be:
tar -xjvf ../bash-doc-3.0.tar.bz2 &&
Not a big issue, but maybe
Peter B. Steiger wrote:
On Thu, 2006-06-01 at 13:50 -0500, Randy McMurchy wrote:
Notice below there are several libs Firefox "can't find". However,
it runs perfectly because it has internal knowledge of the whereabouts
of the libs.
Oof, what a terrible example I picked! That happens to work
Michiel Faber wrote:
> Hello,
>
> The first command in chapter 6.37.1 of lfs 6.1.1 is:
>
> tar -xvf ../bash-doc-3.0.tar.gz &&
>
> however the package i downloaded from a mirror ftp-server is named
> "bash-doc-3.0.tar.bz2" and not "*.gz"
> The command should thus be:
>
> tar -xjvf ../bash-doc-3.0.ta
On 5/31/06, Ёshi <[EMAIL PROTECTED]> wrote:
hi, linux world! i find the bug in groff-1.18.1.1! I first began to
compile this package, than I found that
post-html.cc [src/devices/grohtml/] cannot compiled because of an
absolutely unimportant construct at the line of 263:
char_block::char_block(int
11 matches
Mail list logo
