Summary: | portage-2.2.00.13878 fails in make install | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Mike Sears <msears> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | OS X | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log
build log |
Description
Mike Sears
2009-08-04 14:54:46 UTC
what's your current portage version? emerge --version Portage 2.2.00.13878-prefix (prefix/darwin/macos/10.5/x86, gcc-4.2.1, unavailable, 9.7.1 i386) is the information in pym/portage/const_autotool.py correct? Yes: EPREFIX = "/Users/msears/Gentoo" SYSCONFDIR = "/Users/msears/Gentoo/etc" DATADIR = "/Users/msears/Gentoo/usr/share" PORTAGE_BASE = "/Users/msears/Gentoo/usr/lib/portage" portagegroup = "BRYNMAWR\domain users" portageuser = "msears" rootuser = "msears" rootuid = 273009453 rootgid = 1612776775 PORTAGE_BASH = "/Users/msears/Gentoo/bin/bash" PORTAGE_MV = "/Users/msears/Gentoo/bin/mv" can you attach the config.log file from var/tmp/portage/sys-apps/portage-2.2.00.13878/work please? Created attachment 200160 [details]
config.log
hmmmm, that's strange, but indeed wrong. is grep PORTAGE_GROUP $EPREFIX/etc/make.globals returning what you would expect? yes: PORTAGE_GROUP="BRYNMAWR\domain users" I'm starting to get lost yikes...not good can you also attach the logfile from /Users/msears/Gentoo/var/tmp/portage/sys-apps/portage-2.2.00.13878/temp/ Created attachment 200161 [details]
build log
can you bzgrep through the environment.bz2 file in that same dir for PORTAGE_GROUP please? grep PORTAGE_GROUP environment econf --with-portage-user="${PORTAGE_USER:-portage}" --with-portage-group="${PORTAGE_GROUP:-portage}" --with-root-user="${rootuser}" --with-offset-prefix="${EPREFIX}" --with-default-path="${defaultpath}" || die "econf failed"; does portage emerge when etc/make.globals is changed to PORTAGE_GROUP='BRYNMAWR\domain users' No, PORTAGE_GROUPS is (was) set to "BRYNMAWR\domain user" users that is so if you change from double quotes to single quotes it still fails? what if you change the single backslash into a double backslash? double backslash worked (single quotes made no difference) scratch that needed single quotes AND double backslash scratch that needed single quotes AND double backslash looks like I have a working portage/gentoo prefix now...Thanks!!! what is the final situation? you always need double backslashes? if you edit pym/portage/const_autotool.py and insert a double backslash there too, does portage still work? 1. Always need single quote, double backslashes in make.globals 2. Editing pym/portage/const_autotool.py has no effect (doesn't compile). I'm affraid this is still a problem? it apparently is *** This bug has been marked as a duplicate of bug 285720 *** |