prefix-portage successfully bootstrapped * stage1 successfully finished * Bootstrapping Gentoo prefixed portage installation using * host: x86_64-apple-darwin16 * prefix: /Users/reciprocity/Gentoo * ready to bootstrap stage2_log USE=-acl -berkdb -fortran -gdbm -git -libcxx -nls -pcre -ssl -python bootstrap clang internal-glib -cxx PKG=sys-libs/ncurses !!! /Users/reciprocity/Gentoo/tmp/etc/portage/make.profile is not a symlink and will probably prevent most merges. !!! It should point into a profile within /Users/reciprocity/Gentoo/usr/portage/profiles/ !!! (You can safely ignore this message when syncing. It's harmless.) !!! Your current profile is invalid. If you have just changed your profile !!! configuration, you should revert back to the previous configuration. !!! Allowed actions are limited to --help, --info, --search, --sync, and !!! --version. Odd! Running /bin/bash ./bootstrap-prefix.sh "/Users/reciprocity/Gentoo" stage2 failed! :( Details might be found in the build log: (no build logs found?!?) I have no clue, really. Please find friendly folks in #gentoo-prefix on irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug at bugs.gentoo.org under Gentoo/Alt, Prefix Support. I am defeated. I am of no use here any more. Maybe you can find some clues in /Users/reciprocity/Gentoo/stage2.log
You can try this: $ emerge --sync after go stage2 $ ./bootstrap-prefix.sh $EPREFIX stage2
now I tested this. The cause of this error: if your environment is MacOS Sierra(10.12), There isn't no valid profile for 10.12 (/usr/portage/profiles/prefix/darwin/macos/10.12/x64/) in downloaded portage tree. so you can replace the profile with 10.11 profile. for this: $ rm $EPREFIX/etc/portage/make.profile $ ln -s $EPREFIX/usr/portage/profiles/prefix/darwin/macos/10.11/x64/ $EPREFIX/etc/portage/make.profile
I've committed those, I guess I didn't release a new snapshot. Bootstrapping using LATEST_TREE_YES=1 should get you past this point.
ok, stage2 should install a bash, thus overwriting the symlink (it uses -collision-protect) but that apparently doesn't happen/isn't enough.
I think this commit broke this, but I need to check https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=c81194a94820ab2edb8b16102416b7dbbec54c76
ignore my lst post, wrong bug.
This profile bug was fixed a while ago.
