Sys-kernel/linux-headers: 3.7 (virtual/os-headers) Reproducible: emerge -info =sys-devel/gcc-4.6.3 This issue has happened at least on three systems. If I try then 'emerge -v1 gcc' I get the same issue. The next 'emerge -vuDN world' does not want to reemerge gcc. Total: 6 packages (6 upgrades), Size of downloads: 0 ps uwax | grep emerge | grep -v grep sys-apps/portage-2.1.11.49 USE="doc (ipc) xattr -build -epydoc (-pypy2_0) -python2 -python3 (-selinux)" LINGUAS="ru -pl" 0 kB app-office/scribus-1.4.2-r2 USE="aspell cairo cups examples minimal pdf -debug -hunspell -templates" LINGUAS="de fr ru. If I remove /var/db/.pkg.portage_lockfile manually, 'emerge -pvuND world' shows, that further 6 packages should be emerged, but the two 'emerge -vuDN world' processes continue to emerge -pvuND world These are the packages that would be merged, in order:Ĭalculating dependencies * waiting for lock on /var/db/.pkg.portage_lockfile (the -c option only works if there is an ongoing compilation, see emerge -pvuND world I an other windows I see, that there are two sleeping emerge processes, but 'genlop -c' says that there is no running emerge ps waux | grep emerge | grep -v grep * You might want to review the GCC upgrade guide when moving between * then try running 'fix_libtool_files.sh' on the old gcc versions. * If you have issues with packages unable to locate libstdc++.la, * Switching native-compiler to x86_64-pc-linux-gnu-4.6.3. > Original instance of package unmerged safely. The reemerging of gcc hangs at the end with: I am running 'emerge -uvDN world' wants to reemerge gcc-4.6.3.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |