Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 10049 - access violation at end of build of vim
Summary: access violation at end of build of vim
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Ryan Phillips (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-01 02:06 UTC by conteb
Modified: 2003-02-04 19:42 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
vim-core-6.1-r3.ebuild.diff (vim-core-6.1-r3.ebuild.diff,98 bytes, patch)
2002-11-11 02:30 UTC, Leonardo Boshell (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description conteb 2002-11-01 02:06:54 UTC
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
Comment 1 Ryan Phillips (RETIRED) gentoo-dev 2002-11-01 21:07:33 UTC
just for kicks, try setting the perms to 666 or 660 
Comment 2 conteb 2002-11-03 20:15:29 UTC
it didn't work for 660, but it did work when i set 666 on /dev/pty/s0.
Comment 3 Jochem Kossen 2002-11-04 04:42:08 UTC
i had this problem too, but only when using su or sudo. When logged in as root
from the console, the problem disappeared
Comment 4 Leonardo Boshell (RETIRED) gentoo-dev 2002-11-11 02:30:27 UTC
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.
Comment 5 Ryan Phillips (RETIRED) gentoo-dev 2002-12-16 15:15:59 UTC
committed
Comment 6 conteb 2003-01-24 15:45:41 UTC
Its back.

--------------------------- ACCESS VIOLATION SUMMARY 
---------------------------
LOG FILE = "/tmp/sandbox-vim-core-6.1-r4-4163.log"

chmod:     /dev/pty/s176
--------------------------------------------------------------------------------
Comment 7 Ryan Phillips (RETIRED) gentoo-dev 2003-01-24 16:22:46 UTC
should be fixed within the new ebuild