Denys Vlasenko wrote:
On Monday 16 March 2009 11:07, Sergio wrote:
Perhaps that fix wasn't included in the official release? The diff between
1.13.3 and "custom" ash.c reports many differencies.
I don't see it in 1.13.1:
# ./busybox ash
/.1/usr/srcdevel/bbox/fix/busybox-1.13.3 # while true
do
echo Kill me
sleep 1
done
Kill me
Kill me
^C
/.1/usr/srcdevel/bbox/fix/busybox-1.13.3 #
Same when it's run as a script:
# ./busybox ash z
Kill me
Kill me
^C
#
I tested busybox with my config on x86 PC and found no problem. My gcc is
4.2.4, libc is 2.7
Cross-compiling the same sources/config for PPC board, the Ctrl-C test
fails on the script test.
My .config for 1.13.3 is attached.
Your config is a lot different from mine, however on my x86 PC I can
compile (changing "i486-linux-uclibc-" to "") and run but the script
test fails!
I will focus on this because the only difference between the working build
and the bad one is the config used.
Compilation with your config on the server instead leads to different
errors (even without CONFIG_WERROR) depending on compilator and
architecture target (PPC/x86)
However, removing CONFIG_WERROR and CONFIG_INOTIFYD from your config I
compiled a static BB for PPC board but the script test fails.
I'm sorry if my initial support request is moving to some other possible
issues. My fault in using a custom "ash.c" initially, but now I'm working
with a 1.13.3 so I think there is something in official release.
Many thanks for your help!
Sergio
--
Free software is a matter of liberty, not price. To understand the concept,
you should think of free as in free speech, not as in free beer
- Richard Stallman
http://www.gnu.org/philosophy/free-sw.html
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
