| 1 |
I run catalyst -c myconf -f stage4.spec and let it run until all |
| 2 |
packgaes are built. I stop catalyst with Ctrl-C, remove the resume |
| 3 |
point file build_packages from the .autoresume-directory. |
| 4 |
|
| 5 |
I rerun catalyst-c myconf -f stage4.spec, and it is working here at |
| 6 |
the moment: |
| 7 |
|
| 8 |
emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps |
| 9 |
virtual/portage |
| 10 |
>>> Verifying ebuild manifests |
| 11 |
>>> Emerging (1 of 1) sys-apps/portage-2.1.6.11 |
| 12 |
>>> Installing sys-apps/portage-2.1.6.11 |
| 13 |
* GNU info directory index is up-to-date. |
| 14 |
Bringing system up to date using profile specific use flags |
| 15 |
emerge --quiet --usepkg --buildpkg --newuse -u system |
| 16 |
>>> Verifying ebuild manifests |
| 17 |
>>> Starting parallel fetch |
| 18 |
>>> Emerging (1 of 2) sys-apps/baselayout-1.12.11.1 |
| 19 |
>>> Installing sys-apps/baselayout-1.12.11.1 |
| 20 |
>>> Emerging (2 of 2) sys-devel/gcc-4.3.2-r3 |
| 21 |
|
| 22 |
How come? |
| 23 |
|
| 24 |
Can I avoid this? It takes a while. |
| 25 |
|
| 26 |
|
| 27 |
//Peter |
Archives