Which happens because either: 1) perl wasn't rebuilt with "-build" useflag during the stage2, or 2) because there's some dependency missing somewhere that would have perl rebuilt before autoconf 3) ? I think perl should be rebuilt during stage2, perhaps the bootstrap.sh script needs an update? Thoughts anyone?
It's a lot safer to use dependencies than ad hoc bootstrap.sh magic. Maybe it will fix it if we bump the autoconf ebuild to EAPI 2 and change that dev-lang/perl in DEPEND to dev-lang/perl[-build].
I thought first of rebuilding perl on stage2 just because the build order changes with perl berkdb/gdbm useflags enabled (iirc sys-libs/db introduces a dep for autoconf there), which, if I'm not that much mistaken, shouldn't be enabled as part of the bootstrap process during a stage2 build. I'd even suggest a few other things to rebuild during a bootstrap, but they're specific to things that break during a CHOST change on fbsd only (ie: libtool). But yeah, it's feels better to have autoconf depend on what's really needed from perl.
Created attachment 263315 [details, diff] patch for catalyst ebuild
Created attachment 263317 [details, diff] patch for catalyst on x86-fbsd/amd64-fbsd This problem reproduced my environment. I applied the patch to catalyst and solved it.
The autoconf-2.67 ebuild and later versions already have EAPI 2, so you can easily change dev-lang/perl to dev-lang/perl[-build] in those versions.
(In reply to comment #5) > The autoconf-2.67 ebuild and later versions already have EAPI 2, so you can > easily change dev-lang/perl to dev-lang/perl[-build] in those versions. > Thank you for the reply. I think that autoconf is unrelated to a true solution. Gentoo/FreeBSD has two sed. One is sed of BSD. Another is gsed of GNU. As for these, operation is different. As a result, catalyst cannot appropriately substitute and causes this problem. Catalyst displayed the error of sed when BSD's sed was used, and build was added to the USE flag. The problem was not in any GNU sed. # cat /var/tmp/catalyst/tmp/default/stage3-amd64-bsdsed/etc/make.conf USE="mmx sse sse2" USE="${USE} build" # cat /var/tmp/catalyst/tmp/default/stage3-amd64-gnused/etc/make.conf USE="mmx sse sse2"
Created attachment 263425 [details] catalyst.log FYI, This log is a result of using sys-devel/autoconf-2.65-r1.
(In reply to comment #6) > Gentoo/FreeBSD has two sed. > One is sed of BSD. > Another is gsed of GNU. > > As for these, operation is different. > As a result, catalyst cannot appropriately substitute and causes this problem. > Catalyst displayed the error of sed when BSD's sed was used, and build was > added to the USE flag. You should file a new bug and assign it to catalyst@gentoo.org, since your issue is entirely different from the one that was originally reported in comment #0.
AFAIK, this bug has been fixed. If you have any trouble, please reopen it. closing.
