Hush cant replace lash for my situation
Martinb_ARM_NOMMU_KISSDVD
martinb at zeelandnet.nl
Sun Jan 6 14:03:59 PST 2008
I did build the toolchain but i used a script, i will try to learn to build
my own uclibc but if i look at the buildscript and all the patches the
developers have used then i think i will never be able to do this (but i
will try, and will bug you on a new thread if im stuck)
I did remove the -DBB_NOMMU (dont remember why i ever put it ther in the
first place)
Did Comment out define debug_printf_exec and recompile
run it and type "ls". For me, it shows this:
===============================================
/hdd/shell # ls
parse_stream_outer: run_list
run_list entered
: run_list_real with 1 members
run_list_real start lvl 1
: rword=0 if_code=0 next_if_code=0 skip_more=12
: run_pipe_real with 1 members
run_pipe_real start: single_fg=1
: pipe member 'ls' '(null)'...
run_pipe_real return -1
: checkjobs returned 0
: setting last_return_code=0
: rword=0 if_code=0 next_if_code=0 skip_more=12
run_list_real lvl 1 return 0
run_list return 0
================================================
If i do the same on lash i get
================================================
/hdd/shell # ls
busybox hush lash msh stage2
================================================
i have a criple strace but im not sure if this wil give more help?
-----Oorspronkelijk bericht-----
Van: Denys Vlasenko [mailto:vda.linux at googlemail.com]
Verzonden: zondag 6 januari 2008 4:52
Aan: Martinb_ARM_NOMMU_KISSDVD
CC: busybox at busybox.net
Onderwerp: Re: Hush cant replace lash for my situation
(removed some)
..
On the more extended note, I think it makes sense for you to learn
how to build YOUR OWN uclibc and toolchain instead of using
pre-packaged one. This can help checking whether this is a bug
in older uclibc, etc.
Start from:
http://busybox.net/~vda/HOWTO_bbox_with_uclibc.txt
I will try to help you if you hit a problem;
this will also help making this HOWTO more solid.
If you will do it and need to ask questions,
start a new thread (do not reply to this message).
..
Let's try to figure out what's going on (where it hits the problem).
hush.c has the following at the top:
/* If you comment out one of these below, it will be #defined later
* to perform debug printfs to stderr: */
#define debug_printf(...) do {} while (0)
/* Finer-grained debug switches */
#define debug_printf_parse(...) do {} while (0)
#define debug_print_tree(a, b) do {} while (0)
#define debug_printf_exec(...) do {} while (0)
#define debug_printf_jobs(...) do {} while (0)
#define debug_printf_expand(...) do {} while (0)
#define debug_printf_clean(...) do {} while (0)
Comment out define debug_printf_exec:
//#define debug_printf_exec(...) do {} while (0)
and rebuild busybox.
Now run it and type "ls". For me, it shows this:
$ ls
parse_stream_outer: run_list
run_list entered
: run_list_real with 1 members
run_list_real start lvl 1
: rword=0 if_code=0 next_if_code=0 skip_more=12
: run_pipe_real with 1 members
run_pipe_real start: single_fg=1
: pipe member 'ls' '(null)'...
execing 'ls'
AUTHORS TODO_config_nommu console-tools
ipsvd runit
Config.in applets coreutils
libbb scripts
INSTALL arch debianutils
libpwdgrp selinux
LICENSE archival docs
loginutils shell
Makefile busybox e2fsprogs
miscutils sysklogd
Makefile.custom busybox_ldscript editors
modutils testsuite
Makefile.flags busybox_old examples
networking util-linux
Makefile.help busybox_unstripped findutils
procps
README busybox_unstripped.map include ps1
TODO busybox_unstripped.out init ps2
run_pipe_real return -1
: checkjobs returned 0
: setting last_return_code=0
: rword=0 if_code=0 next_if_code=0 skip_more=12
run_list_real lvl 1 return 0
run_list return 0
$
What do you see?
--
vda
More information about the busybox
mailing list