>>> Completed installing anjuta-2.1.0_beta1 into /var/tmp/portage/dev-util/anjuta-2.1.0_beta1/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-util_-_anjuta-2.1.0_beta1-2622.log" unlink: /usr/lib/anjuta/libanjuta_clsGen.so unlink: /usr/lib/anjuta/libanjuta_clsGen.so.0 unlink: /usr/lib/anjuta/libanjuta_patch.so unlink: /usr/lib/anjuta/libanjuta_patch.so.0 unlink: /usr/lib/anjuta/libanjuta_sample1.so unlink: /usr/lib/anjuta/libanjuta_sample1.so.0 -------------------------------------------------------------------------------- Reproducible: Always
Created attachment 108786 [details] emerge --info output
Do you have a previous install of anjuta? (1.x series)
after first violation i did emerge -C anjuta && emerge anjuta and result is the same
hm .. that's strange ... i still have those broken links in /usr/lib/anjuta/ libanjuta_clsGen.so -> libanjuta_clsGen.so.0.0.0 libanjuta_clsGen.so.0 -> libanjuta_clsGen.so.0.0.0 llibanjuta_patch.so -> libanjuta_patch.so.0.0.0 libanjuta_patch.so.0 -> libanjuta_patch.so.0.0.0 libanjuta_sample1.so -> libanjuta_sample1.so.0.0.0 libanjuta_sample1.so.0 -> libanjuta_sample1.so.0.0.0 i suppose removing them will make all emerge fine ... anyway i can't see a reason such situation appeared
dev-util/anjuta-1.2.4-r1 was the last version i had installed before this
after manually removing /usr/lib/anjuta --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-util_-_anjuta-2.1.0_beta1-31658.log" unlink: /usr/lib/anjuta/* --------------------------------------------------------------------------------
Would you be able to provide the entire build log please?
Created attachment 108814 [details] build.log.gz
Thank you very much for your help and patience. Can you please sync in ~1 hour and try to emerge anjuta again? It should be fixed now.