Gentoo: Access Violation while compiling Autoconf-2.63
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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)
emerge -puND world
also can you post the log somewhere?
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 , 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).
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.
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.