* ERROR: dev-php5/pecl-mcve-7.0.3-r1 failed: * Unable to configure code to compile * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 3420: Called php-ext-source-r2_src_configure * environment, line 3130: Called die * The specific snippet of code: * ./configure --with-php-config=${PHPCONFIG} ${my_conf} || die "Unable to configure code to compile"; * * If you need support, post the output of 'emerge --info =dev-php5/pecl-mcve-7.0.3-r1', * the complete build log and the output of 'emerge -pqv =dev-php5/pecl-mcve-7.0.3-r1'. * The complete build log is located at '/var/tmp/portage/dev-php5/pecl-mcve-7.0.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-php5/pecl-mcve-7.0.3-r1/temp/environment'. * S: '/var/tmp/portage/dev-php5/pecl-mcve-7.0.3-r1/work/php5.2'
Created attachment 254947 [details] build.log
Created attachment 254949 [details] emerge -pqv =dev-php5/pecl-mcve-7.0.3-r1 >> pqv.txt
Created attachment 254951 [details] emerge --info =dev-php5/pecl-mcve-7.0.3-r1 >> info.txt
Created attachment 254953 [details] php -i
(In reply to comment #4) > Created an attachment (id=254953) [details] > php -i > The package still tries to use PHP 5.2 where the system is upgraded to PHP 5.3.
I'm guessing you either didn't set PHP_TARGETS properly or didn't "eselect php set" properly
(In reply to comment #3) > Created an attachment (id=254951) [details] > emerge --info =dev-php5/pecl-mcve-7.0.3-r1 >> info.txt > You have the following in your emerge --info, so you are trying to build the extension with support for php5-2 only: dev-php5/pecl-mcve-7.0.3-r1 was built with the following: USE="" PHP_TARGETS="php5-2 -php5-3" If you do not have PHP_TARGETS set, you may want to run an emerge --sync to get the latest profile changes.
(In reply to comment #7) > (In reply to comment #3) > > Created an attachment (id=254951) [details] [details] > > emerge --info =dev-php5/pecl-mcve-7.0.3-r1 >> info.txt > > > > > You have the following in your emerge --info, so you are trying to build the > extension with support for php5-2 only: > > dev-php5/pecl-mcve-7.0.3-r1 was built with the following: > USE="" PHP_TARGETS="php5-2 -php5-3" > > If you do not have PHP_TARGETS set, you may want to run an emerge --sync to get > the latest profile changes. > After modification it turns out that now on my system PHP_TARGETS is set to 5.3 and when I try to emerge php the package pecl-mcve doesnt pull in as a dependency.No idea if I have specifically done this, or somewhere else. But still I cant compile the package in this bug.Now it fails on a different package. emerge -pv dev-php5/pecl-mcve: [ebuild N ] net-libs/libmonetra-5.2 0 kB [ebuild N ] dev-php5/pecl-mcve-7.0.3-r1 PHP_TARGETS="php5-3 -php5-2" 0 kB Fails on 1st package: checking for correct ltmain.sh version... grep: character class syntax is [[:space:]], not [:space:] no *** Gentoo sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.20, ltmain.sh = ) *** Please run: libtoolize --copy --force if appropriate, please contact the maintainer of this package (or your distribution) for help. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/net-libs/libmonetra-5.2/work/libmonetra-5.2/config.log * ERROR: net-libs/libmonetra-5.2 failed: * econf failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 169: Called _eapi0_src_compile * ebuild.sh, line 621: Called econf * ebuild.sh, line 555: Called die * The specific snippet of code: * die "econf failed" * * If you need support, post the output of 'emerge --info =net-libs/libmonetra-5.2', * the complete build log and the output of 'emerge -pqv =net-libs/libmonetra-5.2'. * The complete build log is located at '/var/tmp/portage/net-libs/libmonetra-5.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-libs/libmonetra-5.2/temp/environment'. * S: '/var/tmp/portage/net-libs/libmonetra-5.2/work/libmonetra-5.2'
You should file a separate bug about this. It is not related to pecl-mvce.
(In reply to comment #9) > You should file a separate bug about this. It is not related to pecl-mvce. > Never mind, its probably difficult to continue.If you think as a Developer the bug can not be re-produce then close the report. I am saying this as I have changed gcc recently, so technically I cant re-produce most of the effects of this bug.But I am just a normal user, not a real dev to make decisions on the report. Many thanks for the support. Cheers
(In reply to comment #10) > Many thanks for the support. No, thank you. Please continue to open reports if you think there are problems. Cheers.
