Gentoo: Access Violation while compiling Autoconf-2.63
 

Hi, this is my first time on the forums.

I recently installed KDE4.1 on my Gentoo workstation and since then I've been trying to get everything back together.

I was wondering if anyone could help me with this problem. I'm trying to compile autoconf so the rest of the updates will install:

jane clinton # emerge world

or

jane clinton # emerge autoconf

(autoconf-2.63 that is) and I keep getting this error:

And...

jane clinton # emerge --info

As far as I understanding, having a git repository in the root dir is a stupid idea but I might be mistaken.(I'm new:D)

I removed the /.git dir and then tried it, same thing happened.

I've been fighting and Googling this all day! I'm also pretty new to Linux and Gentoo and I've managed work out a lot of problems but this one has me beat. This is the first time I've posted a bug.

If you could help me out that would be great:)

Creating a git repo in the root directory, as you found out is a bad idea. git will treat / as being the root of the repo, when executed in any directory tree that doesn't have its own .git somewhere. this calls for breakage all over the place. I would try (very untested)
also can you post the log somewhere?
/var/log/sandbox/sandbox-1274.log

I have a question: are you using plain Gentoo or are you trying to install from a modified/non-supported ebuild from an overlay or Sabayon? The regular ebuild should just download a tarball for 2.63 (or whatever version), but yours seems to be using git for some odd purpose. So, if you use an unofficial ebuild, my advise is to stop doing so unless you have a good reason (that you can explain) to do so.

The standard one should work.

The access violation issues happen when emerge tries to write for any purpose outside the sandbox. A sandbox (for portage corcerns) is a temporal place where the package is installed. Once the package is installed, and emerge is sure that the package installs fine, then it writes to the real live system. This is done this way to prevent leftovers if something fails while installing.

EDITED: To check if the ebuild is overlayed or the official one, you can do "emerge -pv autoconf", at the end of the line it should show [0], if it shows another number, you can see which overlays it is on an index below on the same output. If the ebuild doesn't belong to an unofficial overlay, paste the log file on pastebin.com and direct us to it so we can review it. But, in that case, you should really be posting in bugs.gentoo.org where you will get far better support (I repeat: only if the ebuild is part of the official gentoo tree, which I doubt in this case).

Thanks for the replies so far.

comprookie2000:
The contents of the /var/log/sandbox/sandbox-1274.log log file are actually shown: open_wr: /.git/index.lock
I opened it in a text editor(nano) and it's the same thing.

Also, I already removed the /.git/index.lock tried emerge--didn't work...removed the /.git/ tried it and it still didn't work. I think it's looking for a file that isn't there, which confuses me. However, I'll try that etc-update(since there's quit a few configure files that need updating anyway) in the order you listed it.

i92guboj:
Thanks for the explanation, I'll keep it in mind. I'm going to try emerge -pv autoconf and and come back and post the results.

You can try putting FEATURES=-sandbox in /etc/make.conf. But I wouldn't leave it there for very long.

I wouldn't put it a all in make.conf. If you really need to bypass the protection -at your own risk, or course- use it in command line:

I tried that and it worked but I'm going to take it back out.

Thanks for the help and suggestions everyone:)