Summary: | function stat_perms() returns error messages on ppc-macos | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mamoru KOMACHI (RETIRED) <usata> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ppc-macos |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 58823 | ||
Bug Blocks: | 73544 |
Assuming this works... it'll be in -r9 http://zarquon.twobit.net/gentoo/portage/ebuild.sh-macos-stat.diff Yes, it works. Thanks for the patch. I think this was fixed long ago.... Closing. |
I upgraded portage to 2.0.51-r8, and after that I get following errors during src_install(): >>> Install bash-completion-20041017-r3 into /var/tmp/portage/bash-completion-20041017-r3/image/ category app-shells /usr/lib/portage/bin/dodoc: NEWS does not exist. man: prepallstrip: strip: strip: * file /var/tmp/portage/bash-completion-20041017-r3/image// was installed with group portage! /usr/lib/portage/bin/ebuild.sh: line 1: stat: command not found /usr/lib/portage/bin/ebuild.sh: line 1: printf: 0x: invalid number chmod: invalid file mode: * file /var/tmp/portage/bash-completion-20041017-r3/image///etc was installed with group portage! /usr/lib/portage/bin/ebuild.sh: line 1: stat: command not found /usr/lib/portage/bin/ebuild.sh: line 1: printf: 0x: invalid number chmod: invalid file mode: ... This is because Mac OS X doesn't have stat command (FYI, FreeBSD doesn have stat but doesn's support -c option, used in stat_perms()), and so printf doesn't get correct permission. Since stat is included in coreutils, I suppose it will not be a problem after we manage to get coreutils work on Mac OS X.