|
From: Heiko Z. <he...@zu...> - 2003-10-13 22:26:17
|
Heiko Zuerker wrote: >On 10/12/2003 08:03:29 PM Heiko Zuerker wrote: > > >>Heiko Zuerker wrote: >> >> >> >>>Bruce Smith wrote: >>> >>> >>> >>>>>The major change is that you can define dependencies (i.e. which >>>>>libs are required for this package). It uses the insserv utility and >>>>>will be the same as our init system. >>>>> >>>>> >>>>> >>>>Sounds scary. Give me a little notice before you check it in? >>>>(so I can run one last good compile, just in case ... ;-) >>>> >>>> >>>> >>>> >>>The new build system seems to work. I have to do a few more compiles >>>to make sure, but it looks like I can check it in later tonight. >>>So do you "cvs update -d -P" before I check my stuff in. ;-) >>> >>> >>Looks like our build system is a little bit too much for insserv. ;-) >>That means there will be some delays.... >> >> > >I found the problem, it was a small bug in insserv. > >All the changes are checked in! >You need to do a "make mrproper unpack" first, since the new build system >will not recognize the old flags. > >There's a new make command: "make prepare" >This will order the build scripts according to the specified dependencies >and creates all the symlinks. >You need to do a "make prepare" when you added new scripts. >Prepare will also be automatically invoked after a mrproper. > >The faciliities are specified in the file build/scripts/buildorder.conf . > > If you don't start with a fresh LFS system, then it is absolutely important that you delete /sbin/insserv inside the LFS system. cya Heiko |