| Summary: | SWIG emerge access violation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Cyrus Hall <hallc> |
| Component: | [OLD] Library | Assignee: | dotnet project <dotnet> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | vapier |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Cyrus Hall
2004-04-20 14:37:30 UTC
I have exactly the same problem. I'm guessing the problem originates with SWIG, but I'm haven't dug very deeply yet. I noticed that the access violation happened while make seemed to be working on Guile stuff, so I tried emerging SWIG with "USE=-guile". Sure enough, it completed this time. However, it still installed some Guile shared objects. Even more bizarrely, I emerged SWIG again, this time with "USE=guile" and it worked just fine. Now, I can't reproduce the access violation and I'm not even sure the USE flag is what made it work. I also don't have any idea what "wapi" is, since it doesn't seem to be mentioned on the SWIG site. I did find some mentions of it on PHP related lists, so perhaps it's a PHP issue, not related to Guile. I have no way of testing it now. I just emerged swig-1.3.21 with the guile use flag set and everything worked fine. maybe it was a local env issue? Hard to fix if it can't be reproduced anymore though. I'll close as CANTFIX for now. Go ahead and reopen if it happens again. This is certainly still an open issue as far as I'm concerned. I'm having the exact same issue I was before. I've rsync'ed once a day since I filed the bug report and made sure to get a fresh copy of the file each time I try and -u world, but each time this issue happens, always at the exact same place. I'm not really sure how to debug this issue. If any one has any suggestions I'd be more than willing to do some investigation and report back. I think this is actually caused by recent changes to mono, which swig will auto-detect regardless of any USE flags. The .wapi directory is tied somehow to newer versions of mono, and I think other packages may be suffering similar problems, as the installer is attempting to create and use this directory in the calling user's home dir, but emerge (perhaps rightfully) won't let it.
I managed to have this problem go away by adding the following two flags to the ./configure line in the emerge file itself:
./configure \
--without-csharp-compiler --without-cil-interpreter \
but this is obviously not a permanent solution.
I'm using a fresh portage from last night, with mono just upgraded (to 0.91) previously.
maybe the dotnet folks have some ideas. hey,
just finally noticed this bug when i found the same swig problem. i haven't looked closely at what it's actually doing, but this error is 100% indicative of the "mcs" compiler getting invoked, and it attempted to open some files in the shared ~/.wapi directory. This can be prevented by inheriting from the mono eclass, which at this point does only one thing, changing the shared dir to ${T}.
This does in fact solve the problem. It's not my ebuild at all, but if lanius/herd would like, i'll add that and commit the changes.
adding 'inherit mono' to the top of the ebuild fixed it for me SOLD to the highest bidder |
