Created attachment 675388 [details] build.log This was in stage 3 bootstrap. ---- >>> Completed installing dev-libs/libffi-3.3-r2 into /Users/sam/Gentoo/var/tmp/portage/dev-libs/libffi-3.3-r2/image * Final size of build directory: 6792 KiB (6.6 MiB) * Final size of installed tree: 760 KiB /Users/sam/Gentoo/var/tmp/portage/._portage_reinstall_.vnkwufdd/bin/ecompress: line 65: declare: -A: invalid option declare: usage: declare [-afFirtx] [-p] [name[=value] ...] * QA Notice: invalid reference to /usr/lib/libSystem.B.dylib in //Users/sam/Gentoo/usr/lib/libffi.7.dylib * ERROR: dev-libs/libffi-3.3-r2::gentoo_prefix failed: * invalid install_name found, your application or library will crash at runtime * * Call stack: * misc-functions.sh, line 1273: Called install_qa_check * misc-functions.sh, line 187: Called install_qa_check_macho * misc-functions.sh, line 378: Called die * The specific snippet of code: * has allow_broken_install_names ${FEATURES} || \ * die "invalid install_name found, your application or library will crash at runtime" * * If you need support, post the output of `emerge --info '=dev-libs/libffi-3.3-r2::gentoo_prefix'`, * the complete build log and the output of `emerge -pqv '=dev-libs/libffi-3.3-r2::gentoo_prefix'`. * The complete build log is located at '/Users/sam/Gentoo/var/tmp/portage/dev-libs/libffi-3.3-r2/temp/build.log'. * The ebuild environment file is located at '/Users/sam/Gentoo/var/tmp/portage/dev-libs/libffi-3.3-r2/temp/environment'. * Working directory: '/Users/sam/Gentoo/var/tmp/portage/dev-libs/libffi-3.3-r2/image' * S: '/Users/sam/Gentoo/var/tmp/portage/dev-libs/libffi-3.3-r2/work/libffi-3.3' ----
I guess this is right after pax-utils is installed, is it not?
(move forwards with FEATURES=allow_broken_install_names)
Created attachment 675394 [details] stage3.log.xz (In reply to Fabian Groffen from comment #1) > I guess this is right after pax-utils is installed, is it not? Yeah, scanmacho couldn't pick anything up because it wasn't installed beforehand. A few pkgs snuck in but then it died. (I don't know/think it's related, but outdated libtool not detecting 11.0 might be a recurring problem for us, by the way?)
https://gitweb.gentoo.org/proj/portage.git/commit/?h=prefix&id=c3a69ee41aa0dd40342e05c7e275f82f31744ae1
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=80d619334821e50f62f8ba7433687caafbef75df commit 80d619334821e50f62f8ba7433687caafbef75df Author: Fabian Groffen <grobian@gentoo.org> AuthorDate: 2020-11-28 20:06:30 +0000 Commit: Fabian Groffen <grobian@gentoo.org> CommitDate: 2020-11-28 20:06:30 +0000 sys-apps/portage-3.0.10.2: bump to fix library resolution on macOS Closes: https://bugs.gentoo.org/757240 Package-Manager: Portage-3.0.10-prefix, Repoman-3.0.2 Signed-off-by: Fabian Groffen <grobian@gentoo.org> sys-apps/portage/Manifest | 2 +- sys-apps/portage/{portage-3.0.10.1.ebuild => portage-3.0.10.2.ebuild} | 0 2 files changed, 1 insertion(+), 1 deletion(-)
