The program builds properly, until i get this: --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-vim-core-6.1-r2-24189.log" chmod: /dev/pty/s0 -------------------------------------------------------------------------------- my ptys (at compile time) were: root@lain src # ls -als /dev/pty/s* 0 crw--w---- 1 conteb root 3, 0 Nov 1 02:59 /dev/pty/s0 0 crw--w---- 1 conteb root 3, 1 Nov 1 02:54 /dev/pty/s1
just for kicks, try setting the perms to 666 or 660
it didn't work for 660, but it did work when i set 666 on /dev/pty/s0.
i had this problem too, but only when using su or sudo. When logged in as root from the console, the problem disappeared
Created attachment 5569 [details, diff] vim-core-6.1-r3.ebuild.diff Ryan, I'm receiving access violations too with vim-core-6.1-r3. However, I don't believe chmod'ing /dev/pty files manually is the right solution... I've been using vim in Gentoo since my first system install and I've never messed with permissions of my /dev files. Anyway, I noticed that in previous ebuilds, the following line was taking care of the sandbox violations: addwrite /dev/pty/* And it was replaced with something that doesn't work for me anymore. After a little testing, I end up with this modified ebuild (path attached) which allows me to emerge vim-core again without having to worry about file permissions. If you have another solution, please let me know. Thanks.
committed
Its back. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-vim-core-6.1-r4-4163.log" chmod: /dev/pty/s176 --------------------------------------------------------------------------------
should be fixed within the new ebuild