> I just want to clear that there are two problems. > 1. check that every think is there what is need to compile bb > 2. what to do if something is found missing > > my idea is to have a script like But that has to be run to test. What if anything fails because a program got removed? That is, what happened.
Busybox build successfully several times. Than I started to remove some stuff from that system which I expected not to be used (and I really never used od visibly in over 20 years) ... and busybox continued to build without failure ... only after I moved the executable to the final location on the new maintenance/emergency/recovery system I noticed the segmentation fault as I requested a usage information ... so what has gone wrong? ... primarily I expected some damage of my new recovery system ... than the question was, if any modifications to busybox produced that error or if an update from 1.17.1 to 1.17.2 solve the problem ... but problem still remained ... and I wouldn't have recalled your script in that situation. In my eyes such a script isn't bad to test if it is principally possible to compile busybox in that environment ... but it isn't really required. I just expect a build to abort unsuccessful, if ANYTHING goes bad, that is not handled. Nothing more but not less. -- Harald _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
