Created attachment 686922 [details] build.log, emerge --info, emerge -pqv, environment Failed during prepare phase: build.log: * Package: dev-php/theseer-Autoload-1.26.0 * Repository: gentoo * Maintainer: php-bugs@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox * Applying theseer-Autoload-1.26.0-autoload.php.patch ... [ ok ] Cannot load Xdebug - it was already loaded phpab 1.26.0 - Copyright (C) 2009 - 2021 by Arne Blankerts and Contributors Scanning directory src Autoload file src/autoload.php generated. /var/tmp/portage/dev-php/theseer-Autoload-1.26.0/temp/environment: line 481: 37 Segmentation fault (core dumped) ./phpab.php --output src/autoload.php --template "${FILESDIR}"/autoload.php.tpl --basedir src src * ERROR: dev-php/theseer-Autoload-1.26.0::gentoo failed (prepare phase): * (no error message) * * Call stack: * ebuild.sh, line 125: Called src_prepare * environment, line 489: Called die * The specific snippet of code: * ./phpab.php --output src/autoload.php --template "${FILESDIR}"/autoload.php.tpl --basedir src src || die * All required files are in the attachment. Thank you to solve this issue.
Do you have xdebug installed?
I mean dev-php/xdebug installed and threads USE on dev-lang/php? That is known to cause issues
(In reply to Brian Evans from comment #1) > Do you have xdebug installed? Yes, I do have XDebug installed on my machine. Does that mean that I must de-install XDebug to build theseer-Autoload successfuly? (or, maybe remove the threads USE flag on php?). Can I in that case reinstall XDebug after I built theseer-Autoload? Thank you for letting me informed. Kind regards. Jean-Claude
(In reply to Brian Evans from comment #2) > I mean dev-php/xdebug installed and threads USE on dev-lang/php? > > That is known to cause issues Effectively, I ran an emerge --unmerge xdebug, then I ran an emerge -qav theseer-Autoload (with success), and finally I ran an emerge -qav xdebug Then all is now ok. Thank you for the informations.
*** This bug has been marked as a duplicate of bug 759835 ***