Re: [Mpg123-users] system call error
Brought to you by:
sobukus
From: Thomas O. <tho...@or...> - 2008-03-28 08:08:32
|
Am Thu, 27 Mar 2008 19:21:01 +0100 schrieb "Carlos kescuin" <ke...@gm...>: > No, this is another problem Hm... but I remember this one... did we talk on IRC or such? Anyhow, yes, these other two threads are different, sorry. "applet not found" indicates that you entered the command mpg123 and busybox was unable to either find a executable binary named mpg123 in the PATH or ... wait. No "or". As far as I can remember, busybox doesn't just assume a command may be a builtin applet. You have to either run "busybox $applet_name" or have a symlink /bin/$applet -> /bin/busybox ... that's how it was for my initramfs images at least. Anyway, busybox applets shouldn't be connected to system calls. System calls are requests to the kernel, without any busybox program/applet in between. mpg123 doesn't run any external commands. It executes, it may fork (with the -b parameter), it accesses files / audio device. I don't see where you can get that error from mpg123 behaviour... of course that doesn't outweight the fact that you are getting the error. Can you do a `strace mpg123` in the arm system (is strace there)? That would show what's going on behind the scenes. Apart from that, you may have better luck asking busybox folks... as it may be a specific thing about busybox, not mpg123. Alrighty then, Thomas. PS: You compiled other apps (like "Hello World!";-) and they ran fine? |