[pocket-linux] Chapter 3 : no shell : Reason

[Bettes]

Hi David,

Imagine I use the prebuilt i386 libraries.
Do I have also have to use them when I compile bash, or any other source ?
Or can I just compile as before?


On Monday 21 June 2004 22:38, David Horton wrote:
> Bettes wrote:
> > Just a summary of the shell problem.
> >
> > This problems happens when you compile with a recent distribution and
> > testing it on an old PC.
> >
> > I was using:
> > SuSE 8.2 on an Athlon 1Ghz, 256 MB RAM as development machine
> > P I 100Mhz, 32 MB RAM as test machine.
> >
> > The sympton is that all goes well till the moment you expect to see the
> > shell. But the shell never appears.
> >
> > Reason of the problem:
> > It has something to do with the used libraries of the development
> > machine. They seem not to work on the test machine.
> > However, If you try the floppies on your development machine they work as
> > expected.
> >
> > Solution:
> > Not found yet :-(
>
> I think the quickest solution is to use libraries that are known to be
> compatible with older systems.  For pre-built, i386 compatible libraries
> you can get glibc from my web site.
> [http://www.happy-monkey.net/architect/bin-pkgs/glibc-2.3.2.i386.tar.gz]
>     I also think the Slackware distro uses i486 compatible libraries.
>
> If you want to be bold you can build your own glibc from source.  It's
> not really any more difficult than building any other GNU software, it
> just takes a long time.  If you download Architect from SourceForge
> [http://sourceforge.net/projects/architect/] there is a shell script in
> the recipes directory called glibc-2.3.2 that will show the steps needed
> to build from source.
>
> Dave
>
> _______________________________________________
> Pocket-Linux mailing list
> Pocket-Linux at ufo.chicago.il.us
> http://ufo.chicago.il.us/cgi-bin/mailman/listinfo/pocket-linux