ash not working in statically compiled busybox on amd64

Andree Leidenfrost aleidenf at bigpond.net.au
Tue May 16 21:26:11 UTC 2006


Hi Mike,

Thanks for your reply!

On Tue, 2006-05-16 at 13:05 -0400, Mike Frysinger wrote:
> On Tuesday 16 May 2006 08:49, Andree Leidenfrost wrote:
> > I am getting the following error message when trying to run ash from a
> > statically compiled busybox 1.1.2 on amd64:
> >
> > andree at aurich64:~$ ./ash
> >
> >
> > BusyBox v1.1.2 (2006.05.16-11:40+0000) Built-in shell (ash)
> > Enter 'help' for a list of built-in commands.
> >
> > ./ash: Cannot set tty process group (Operation not permitted)
> 
> weird ... building statically on my amd64 and it works ok ...
> -mike

Silly, I know, but just to make sure, we are talking the OS, not just
the hardware.

Also, did you try what I did, i.e. use a pristine tarball and just turn
on static compile and choose ash as default shell? Because I found other
configurations that work as well, the one I mentioned is just the
simplest example for it not working. (I should probably have said that
in the first place.)

Regards,
Andree
-- 
Andree Leidenfrost
Sydney - Australia

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.busybox.net/pipermail/busybox/attachments/20060517/16320e13/attachment-0002.pgp 


More information about the busybox mailing list