Re: [gentoo-user] can packages be rebuild in any order?
22 hrs later...all my packages are recompiled with the new USE and CFLAGS, it does feel faster... thanks for the tips.. On Sat, 2003-09-27 at 18:34, Jason Stubbs wrote: On Sunday 28 September 2003 02:56, HvR wrote: > > > I usually use "emerge -ep world" and put the list of packages (without > > > the version numbers) generated in a file called pkgs. I then use the > > > following when rebuilding: > > > > > > for i in `cat pkgs`; do emerge --one-shot $i && (grep -v $i pkgs > > > > pkgs2; mv pkgs2 pkgs) done > > > > > > That way you will have a list of any packages that fail to compile for > > > some reason and a way to restart if it needs to be stopped for any > > > reason. > > > > isnt there an order to the packages? like you have to build the glibc > > first? doesnt every program get linked with it? or gcc do make the > > rest go faster? if not your trick is great: on another machine i had > > to do everything from scratch 3 times since something would happen in > > the middle of it and i didnt know how far it got. There is an order to the packages but it is not vitally important on a running system. glibc for example responds to very few use flags: nls, pic & nptl. nls & pic won't affect how other packages are compiled and nptl will only affect very few. "emerge -ep" will put the packages in order based on dependencies anyway, so you won't have any problems (dep-related) if you recompile in the order it gives you. Jason -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] can packages be rebuild in any order?
On Sunday 28 September 2003 02:56, HvR wrote: > > > I usually use "emerge -ep world" and put the list of packages (without > > > the version numbers) generated in a file called pkgs. I then use the > > > following when rebuilding: > > > > > > for i in `cat pkgs`; do emerge --one-shot $i && (grep -v $i pkgs > > > > pkgs2; mv pkgs2 pkgs) done > > > > > > That way you will have a list of any packages that fail to compile for > > > some reason and a way to restart if it needs to be stopped for any > > > reason. > > > > isnt there an order to the packages? like you have to build the glibc > > first? doesnt every program get linked with it? or gcc do make the > > rest go faster? if not your trick is great: on another machine i had > > to do everything from scratch 3 times since something would happen in > > the middle of it and i didnt know how far it got. There is an order to the packages but it is not vitally important on a running system. glibc for example responds to very few use flags: nls, pic & nptl. nls & pic won't affect how other packages are compiled and nptl will only affect very few. "emerge -ep" will put the packages in order based on dependencies anyway, so you won't have any problems (dep-related) if you recompile in the order it gives you. Jason -- [EMAIL PROTECTED] mailing list
[gentoo-user] can packages be rebuild in any order?
I usually use "emerge -ep world" and put the list of packages (without the version numbers) generated in a file called pkgs. I then use the following when rebuilding: for i in `cat pkgs`; do emerge --one-shot $i && (grep -v $i pkgs > pkgs2; mv pkgs2 pkgs) done That way you will have a list of any packages that fail to compile for some reason and a way to restart if it needs to be stopped for any reason. isnt there an order to the packages? like you have to build the glibc first? doesnt every program get linked with it? or gcc do make the rest go faster? if not your trick is great: on another machine i had to do everything from scratch 3 times since something would happen in the middle of it and i didnt know how far it got.
