I'm using a statically linked version of ash, which is simpler to build.
I'm also using pocket linux (aka busybox) plus genromfs for building it - rather
than messing about with ram disks...

Dave

On Tue, 21 Mar 2000, George France wrote:
> which version of BASH? I can send you a bash 2.2.03-4 bin if you would like?
> 
> --George
> 
> George France,      [EMAIL PROTECTED]
> Cambridge Research Laboratory, Compaq Computer Corporation
> One Kendall Square, Building 700     MS: CRL
> Cambridge, MA 02139 USA
> 
> 
> -----Original Message-----
> From: Steven J. Hill [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 20, 2000 4:02 PM
> To: [EMAIL PROTECTED]
> Subject: Some BASH shell help please...
> 
> 
> Greetings.
> 
> I attempted to cross-compile BASH on my i686 for ARM, but could not seem to
> get the steps right to do it. I have a complete tool chain that works, but
> the configure script seems to freak out a lot of places. Does anyone have a
> step by step list OR would someone just provide me a statically linked BASH
> binary for a 7xx seris ARM core. NO StrongARM binaries please. I am trying
> to test my serial console and am going to create a RAMdisk with BASH as my
> /sbin/init. I apologize if this was asked before, but I did not find much in
> the mailing list archives or I overlooked it. Thanks.
> 
> -Steve
> 
> -- 
>  Steven J. Hill - Embedded SW Engineer
>  Public Key: 'finger [EMAIL PROTECTED]'
>  FPR1: E124 6E1C AF8E 7802 A815
>  FPR2: 7D72 829C 3386 4C4A E17D
> 
> unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
> ++        Please use [EMAIL PROTECTED] for
> ++
> ++                        kernel-related discussions.
> ++
> 
> unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
> ++        Please use [EMAIL PROTECTED] for           ++
> ++                        kernel-related discussions.                      ++


unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for           ++
++                        kernel-related discussions.                      ++

Reply via email to