Summary: | emerge hangs on configure "checking whether getcwd handles long file names properly..." | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Josh G <joshin> |
Component: | Sandbox | Assignee: | Sandbox Maintainers <sandbox> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | sam |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Other | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=447970 https://bugs.gentoo.org/show_bug.cgi?id=98419 https://bugs.gentoo.org/show_bug.cgi?id=261936 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Josh G
2006-10-03 11:44:56 UTC
Portage has no control over hanging configure scripts. You need to find out why that script is hanging (use strace or something). I think the issue is more that sandbox seems to have a longstanding and intermittent issue when gnu configure tests getcwd(). If you can suggest a way for me to test this, I'd be happy to do so. However with sandbox enabled it doesn't work and with it disabled it does. BTW, the failure results in a directory "confdir3" being created with an infinitely recursive (well until sandbox crashes) subdirectory called "confdir3" Again, how can I further test this? (In reply to comment #1) > Portage has no control over hanging configure scripts. Ignore me. I thought this was assigned to dev-portage. ;) i believe this should be fixed in sandbox git now http://git.overlays.gentoo.org/gitweb/?p=proj/sandbox.git;a=commitdiff;h=7b75eafeb73f70f56de1b90eb7a874fd21fd852f |