frank at langtind.org
Sat Mar 10 02:36:17 PST 2001
I had the same problem when I built the nightly build (a month ago). This
was before the problem with glibc was solved. During the build it
disappeared. I'm not sure why the error occur, but I don't think it's
harmful. Maybe it'll be gone when you compile the dynamic bash?
My advise is to build the whole system ignoring this error. If the message
is still present after the complete system is built, you could try to
recompile glibc and/or bash. I'm that will do.
On Fri, 9 Mar 2001, Jeremie Lasalle-ratelle wrote:
> On Friday 09 March 2001 00:19, you wrote:
> > maybe you can try run TERM=linux
> > Jeremie Lasalle-ratelle wrote:
> > > Does it matter if bash says : " invalid character -96 in exportstr for
> > > TERM"
> > >
> > > Should I copy a valid TERM file from my old system?
> > >
> > > --
> > > Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
> > > and put unsubscribe in the subject header of the message
> It happens when I first enter the chrooted environement, before installing
> GLIBC 2.2.1
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the lfs-dev