From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Gcc compiling, is this normal?
Date: Sun, 12 May 2013 16:16:16 -0500 [thread overview]
Message-ID: <519006A0.2080807@gmail.com> (raw)
Howdy,
I been noticing something weird when I upgrade gcc. Is this normal?
root@fireball / # genlop -c
Currently merging 2 out of 5
* sys-devel/gcc-4.4.7
current merge time: 6 seconds.
ETA: 24 minutes and 27 seconds.
Currently merging 3 out of 5
* net-misc/curl-7.30.0
current merge time: 7 seconds.
ETA: 18 minutes and 50 seconds.
Currently merging 2 out of 5
* sys-devel/gcc-4.4.7
current merge time: 7 seconds.
ETA: 21 minutes and 14 seconds.
root@fireball / #
I'm not worried about curl. It just happened to be there. This is the
list of packages it is supposed to update:
root@fireball / # emerge -uvaDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-devel/gcc-4.5.4:4.5 USE="gtk mudflap (multilib)
nls nptl openmp (-altivec) -cxx -doc (-fixed-point) -fortran -gcj
(-hardened) (-libssp) -lto -multislot -nopie -nossp -objc -objc++
-objc-gc {-test} -vanilla (-graphite%)" 0 kB
[ebuild R ] sys-devel/gcc-4.4.7:4.4 USE="gtk mudflap (multilib)
nls nptl openmp (-altivec) -cxx -doc (-fixed-point) -fortran -gcj
(-hardened) (-libssp) -multislot -nopie -nossp -objc -objc++ -objc-gc
{-test} -vanilla (-graphite%)" 0 kB
[ebuild U ] net-misc/curl-7.30.0 [7.29.0-r1] USE="ipv6 ssl threads
-adns -idn -kerberos -ldap -metalink -rtmp -ssh -static-libs {-test}"
CURL_SSL="openssl -axtls -cyassl -gnutls -nss -polarssl" 0 kB
[ebuild U ] app-misc/tmux-1.8 [1.6] USE="-vim-syntax" 0 kB
[ebuild U ~] kde-base/kdelibs-4.10.3-r2:4 [4.10.3:4] USE="3dnow alsa
bzip2 fam handbook jpeg2k lzma mmx nls opengl (policykit)
semantic-desktop spell sse sse2 ssl udev udisks upower zeroconf -acl
(-altivec) (-aqua) -debug -doc -kerberos -openexr {-test}" 0 kB
Total: 5 packages (3 upgrades, 2 reinstalls), Size of downloads: 0 kB
Would you like to merge these packages? [Yes/No] y
I noticed this one or twice before. It is compiling the same compiler
version twice when it should be upgrading/recompiling two *different*
versions. I read before that gcc compiles three times or something but
the thing is, it can compile for HOURS and never finish. Usually I stop
it and restart emerge and it compiles as it should, one for each version
and finishes as it should time wise. I once started the upgrade and
went to take a nap. I woke up around 5 or 6 hours later to find gcc
compiling twice on the same version. Even libreoffice only takes a hour
or so.
Anyone else see this before? Now to go stop this one and get it to
update right and not take all week.
Thanks.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next reply other threads:[~2013-05-12 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 21:16 Dale [this message]
2013-05-12 21:27 ` [gentoo-user] Gcc compiling, is this normal? Alan McKinnon
2013-05-12 21:37 ` David Relson
2013-05-13 6:45 ` Alan McKinnon
2013-05-12 21:53 ` Dale
2013-05-13 6:57 ` Alan McKinnon
2013-05-13 8:56 ` Dale
2013-05-13 10:04 ` J. Roeleveld
2013-05-13 10:30 ` Dale
2013-05-13 11:16 ` Dale
2013-05-13 11:21 ` J. Roeleveld
2013-05-13 11:31 ` Marc Joliet
2013-05-13 11:47 ` Dale
2013-05-13 11:43 ` Dale
2013-05-13 13:05 ` J. Roeleveld
2013-05-13 14:42 ` Peter Humphrey
2013-05-13 17:11 ` Dale
2013-05-13 22:08 ` Neil Bothwick
2013-05-13 22:22 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519006A0.2080807@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox