View previous topic :: View next topic |
Author |
Message |
nemo_ Apprentice
Joined: 19 Sep 2002 Posts: 167 Location: Brussels, Belgium
|
Posted: Sun Sep 22, 2002 6:43 pm Post subject: emerge world keeps recompiling a lot of packages ?! |
|
|
Hi all,
I've ran into a wierd problem yesterday, I changed some USE flags and then recompiled many packages. Once the emerge world completed successfully, I checked emerge -p world and saw that all these very same packages were still marked to be recompiled ! (I assume that's what [ebuild R ] means).
So what should I do now ? I tried emerging portage again, then I did an emerge -e world - no changes, everything compiles, yet still those many packages marked for recompile right after that.
Did I screw up my USE flags or does anyone have an idea ? Maybe my emerge does not update the ebuild's status properly ?
This is running gentoo 1.2, here is my make.conf :
USE="mmx 3dnow opengl xv X gtk gnome sdl gif jpeg png gd avi mpeg osd oss dvd xmms oggvorbis encode pam ssl crypt imap mozilla spell truetype pdflib samba"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -O3 -pipe"
CXXFLAGS="-march=i686 -O3 -pipe"
FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
and finally the results of an emerge -p world right after running an emerge world (sorry for the long list) :
fat root # emerge -p world
These are the packages that I would merge, in order.
Calculating world dependencies ...done!
[ebuild R ] sys-apps/man-pages-1.52
[ebuild R ] sys-apps/util-linux-2.11u
[ebuild R ] sys-apps/grep-2.5-r1
[ebuild R ] sys-apps/reiserfsprogs-3.6.3
[ebuild R ] sys-libs/zlib-1.1.4
[ebuild R ] sys-libs/gdbm-1.8.0-r5
[ebuild R ] sys-apps/textutils-2.0.21
[ebuild R ] sys-apps/kbd-1.06-r1
[ebuild R ] sys-apps/netkit-base-0.17-r6
[ebuild R ] sys-devel/binutils-2.11.92.0.12.3-r2
[ebuild R ] sys-apps/fileutils-4.1.8-r2
[ebuild R ] dev-lang/python-2.2.1-r2
[ebuild R ] sys-devel/patch-2.5.4-r4
[ebuild R ] sys-devel/flex-2.5.4a-r4
[ebuild R ] net-misc/openssh-3.4_p1-r3
[ebuild R ] sys-devel/ld.so-1.9.11-r2
[ebuild R ] sys-libs/cracklib-2.7-r5
[ebuild R ] sys-libs/pwdb-0.61-r3
[ebuild R ] sys-apps/gawk-3.1.1
[ebuild R ] sys-apps/gzip-1.3.2
[ebuild R ] sys-devel/bin86-0.15.5
[ebuild R ] sys-apps/grub-0.90-r7
[ebuild R ] sys-apps/sed-3.02.80-r4
[ebuild R ] sys-apps/setserial-2.17-r2
[ebuild R ] sys-devel/make-3.79.1-r4
[ebuild R ] sys-apps/sh-utils-2.0.11-r5
[ebuild R ] sys-devel/bc-1.06-r3
[ebuild R ] sys-libs/db-3.2.9-r1
[ebuild R ] sys-apps/bzip2-1.0.2-r2
[ebuild R ] sys-devel/bison-1.35
[ebuild R ] sys-apps/texinfo-4.2-r5
[ebuild R ] sys-apps/man-1.5k
[ebuild R ] sys-apps/file-3.37
[ebuild R ] sys-apps/cpio-2.4.2-r4
[ebuild R ] sys-apps/bash-2.05a-r3
[ebuild R ] sys-apps/iptables-1.2.7a
[ebuild R ] sys-apps/psmisc-19-r3
[ebuild R ] sys-devel/gcc-2.95.3-r7
[ebuild R ] net-misc/dhcpcd-1.3.20_p0-r1
[ebuild R ] net-misc/rsync-2.5.5-r1
[ebuild R ] sys-apps/portage-2.0.37
[ebuild R ] sys-apps/shadow-4.0.3
[ebuild R ] sys-apps/procps-2.0.7-r6
[ebuild R ] sys-apps/tar-1.13.25-r2
[ebuild R ] sys-libs/readline-4.1-r4
[ebuild R ] net-ftp/ftp-0.17-r1
[ebuild R ] net-misc/netkit-telnetd-0.17-r3
[ebuild R ] gnome-base/gnome-2.0.2-r1
[ebuild R ] sys-devel/perl-5.6.1-r6
[ebuild R ] app-shells/sash-3.4-r5
[ebuild R ] sys-devel/automake-1.6.1-r6
[ebuild R ] sys-apps/pam-login-3.7
[ebuild R ] sys-apps/hdparm-5.2-r2
[ebuild R ] sys-apps/sharutils-4.2.1-r5
[ebuild R ] sys-apps/modutils-2.4.19
[ebuild R ] sys-libs/glibc-2.2.5-r6
[ebuild R ] sys-apps/groff-1.17.2-r2
[ebuild R ] sys-apps/findutils-4.1.7-r1
[ebuild R ] sys-apps/e2fsprogs-1.27
[ebuild R ] app-editors/nano-1.0.8-r1
[ebuild R ] sys-devel/m4-1.4p
[ebuild R ] media-video/nvidia-kernel-1.0.3123
[ebuild R ] net-misc/wget-1.8.2
[ebuild R ] sys-libs/pam-0.75-r7
[ebuild R ] sys-apps/which-2.14
[ebuild R ] sys-libs/slang-1.4.5-r2
[ebuild R ] sys-devel/libtool-1.4.1-r9
[ebuild U ] kde-base/kdelibs-3.0.3-r1
[ebuild R ] kde-base/kde-3.0.3
[ebuild R ] sys-apps/diffutils-2.7.7
[ebuild R ] sys-apps/devfsd-1.3.25
[ebuild R ] sys-devel/gettext-0.11.1
[ebuild R ] sys-apps/less-376
[ebuild R ] sys-apps/ed-0.2-r3
[ebuild R ] sys-apps/baselayout-1.8.3
[ebuild R ] sys-apps/raidtools-0.90-r2
[ebuild R ] sys-apps/net-tools-1.60-r4
[ebuild R ] sys-apps/debianutils-1.16
[ebuild R ] sys-devel/autoconf-2.53a
[ebuild R ] sys-apps/fbset-2.1 |
|
Back to top |
|
|
proxy Apprentice
Joined: 20 Apr 2002 Posts: 260 Location: Chantilly, VA
|
Posted: Sun Sep 22, 2002 7:27 pm Post subject: |
|
|
perhaps you really want to be using "emerge -pu world"?
proxy |
|
Back to top |
|
|
nemo_ Apprentice
Joined: 19 Sep 2002 Posts: 167 Location: Brussels, Belgium
|
Posted: Sun Sep 22, 2002 7:31 pm Post subject: |
|
|
indeed emerge -pu world gives no results as expected. But what do all these [ebuild R] mean in the emerge -p world output then ? In the past doing an emerge -p world would give no results when I had just updated my system. |
|
Back to top |
|
|
nempo Guru
Joined: 16 Apr 2002 Posts: 360 Location: Linkoping, Sweden
|
Posted: Sun Sep 22, 2002 7:40 pm Post subject: |
|
|
Its the action it will do if you issue the command without the '-p' flag. R means rebuild, U means update and Im sure there's one for Install but can't remember it atm.
If you do emerge gnome, it will install gnome and all its dependencies, if you do emerge world it will install everything that is listed in world ie. your entire system. But if you do emerge -u gnome it will see if there's a later version listed in your /usr/portage for gnome, then if you do emerge -u world similar things happen but for all installed packages.
Last edited by nempo on Sun Sep 22, 2002 7:45 pm; edited 1 time in total |
|
Back to top |
|
|
nemo_ Apprentice
Joined: 19 Sep 2002 Posts: 167 Location: Brussels, Belgium
|
Posted: Sun Sep 22, 2002 7:44 pm Post subject: |
|
|
nempo wrote: | Its the action it will do if you issue the command without the '-p' flag. R means rebuild, U means update and Im sure there's one for Install but can't remember it atm. |
I figured that out already (I guess N is for install new ?) but my question is : why does emerge -p world come up with the exact same output right after I ran the actual emerge world command ? In other words : I could keep on running emerge world again and again and the same stuff would rebuild again and again whereas in the past I ran emerge world once, then right after that a second emerge world would do nothing.
all the packages rebuild just fine - why are they still listed for rebuild once it's done then ? |
|
Back to top |
|
|
nempo Guru
Joined: 16 Apr 2002 Posts: 360 Location: Linkoping, Sweden
|
Posted: Sun Sep 22, 2002 7:46 pm Post subject: |
|
|
I just updated my answer, please reread =) |
|
Back to top |
|
|
nemo_ Apprentice
Joined: 19 Sep 2002 Posts: 167 Location: Brussels, Belgium
|
Posted: Sun Sep 22, 2002 8:06 pm Post subject: |
|
|
thanks for the update nempo - I guess I got a little confused.
However I thought emerge -e world was the command to rebuild _everything_. What's the difference with emerge world then ?
lap root # emerge -pe world | wc -l
224
lap root # emerge -p world | wc -l
97 |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Mon Sep 23, 2002 12:38 am Post subject: |
|
|
Which version of portage are you running? This thread might be relevant. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
nemo_ Apprentice
Joined: 19 Sep 2002 Posts: 167 Location: Brussels, Belgium
|
Posted: Mon Sep 23, 2002 1:38 am Post subject: |
|
|
kanuslupus wrote: | Which version of portage are you running? This thread might be relevant. |
exactly the same issue. thanks for pointing me to the right place. |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Mon Sep 23, 2002 2:17 am Post subject: |
|
|
OK, locking this one then. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
|