Summary: | Portage-2.0.51-r2 doesn't compile on MacOSX | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Roman Dilken <bugzilla> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | osx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC64 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roman Dilken
2004-10-22 00:00:31 UTC
Is the current portage sandbox supported at all under macos? No, the sandbox is not (yet) supported under Mac OS X. Please use FEATURES="-sandbox". Oh, it's funny. I didn't recognize it but after testing now I see that sandbox is automatically switched on although I switched it off in /etc/make.conf. Portage should not build sandbox on macos. That has nothing to do with enabling it. Did you somehow resolve the issue? There must be the useflag ppc-macos set. Why does still the useflag macos appear instead of the new useflag ppc-macos? the same thing happens with portage 2.0.51-r8 ACCEPT_KEYWORDS="ppc-macos" FEATURES="-sandbox cvs keepwork collision-protect" obviously it tries to build sandbox but can't any solution? `emerge --info` please? default-macos-{10.3,10.4} profiles are not supported any more. If you are using one of them, please switch to one of default-darwin/macos/{10.3,10.4}. Just pointing out... "ppc-macos" is not part of the list of USE flags in the `emerge --info` output provided. This being the case, the conditional being tested at line 71 of portage-2.0.51-r8.ebuild (in src_compile) will return false and thus execution will follow to the else clause and execute `make' in src/sandbox. For comparison purposes, my output from `emerge --info` does include "ppc-macos" in USE. I have no trouble merging portage .51-r8. |