From: "Vladimir G. Ivanovic" <vgivanovic@comcast.net>
To: Gentoo AMD64 List <gentoo-amd64@lists.gentoo.org>
Subject: [gentoo-amd64] emerge of gcc-4.1.1-r2 fails because of file collisions
Date: Tue, 14 Nov 2006 15:55:55 -0800 [thread overview]
Message-ID: <1163548555.30482.42.camel@scarlatti.leonora.org> (raw)
I went to emerge the latest version of GCC, and all went well until it
came time to install the files. I have over 3000 collisions, so the
emerge failed.
I currently have gcc-4.1.1-r1 installed with USE="-altivec -bootstrap
-build doc fortran gcj gtk -hardened -ip28 -ip32r10k -mudflap -multilib
multislot -n32 -n64 nls -nocxx -objc -objc++ -objc-gc -test -vanilla".
No problems so far.
# qcheck sys-devel/gcc-4.1.1-r1 yields:
Checking sys-devel/gcc-4.1.1-r1 ...
MTIME: /usr/lib/classpath/libgjsmalsa.so.0
MD5-DIGEST: /usr/lib/classpath/libgjsmalsa.la
MD5-DIGEST: /usr/lib/classpath/libgjsmalsa.so.0.0.0
MTIME: /usr/lib/classpath/libgjsmalsa.so
MD5-DIGEST: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/32/libstdc
++.so.6.0.8
MD5-DIGEST: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/libgcj.so.7.0.0
MD5-DIGEST: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/libstdc
++.so.6.0.8
* 4167 out of 4174 files are good
Picking one of the files that collide at random:
existing file /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/grepjar is
not owned by this package
but
# qfile /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/grepjar
sys-devel/gcc (/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/grepjar)
and as a further check
# qlist sys-devel/gcc | fgrep "4.1.1/grepjar"
/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1/grepjar
Does anyone have an idea of what's going on? (and how I can fix it!)
Thanks.
--- Vladimir
--
Vladimir G. Ivanovic <vgivanovic@comcast.net>
--
gentoo-amd64@gentoo.org mailing list
reply other threads:[~2006-11-14 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1163548555.30482.42.camel@scarlatti.leonora.org \
--to=vgivanovic@comcast.net \
--cc=gentoo-amd64@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