function names about apcu HOT 25 CLOSED

If you build with full compatibility (default), you should have both.

try

php --re apcu
php --re apc

from apcu.

I tried both: with and without but don't still get the error that it don't exist

from apcu.

http://test.goal.io/test.php

from apcu.

php --re apcu shows the apcu functions
php --re apc throws an exception: Exception: Extension apc does not exist

from apcu.

We also have the APCU_APC_FULL_BC constant in this release, if that's false there's no APC compat. If that's true and still no apc_* functions, that might be a bug.

from apcu.

I've tried it with just pressing "enter" two times as well as typing yes and no. but the constant seems to be false

• Constants [17] {
  Constant [ integer APC_LIST_ACTIVE ] { 1 }
  Constant [ integer APC_LIST_DELETED ] { 2 }
  Constant [ integer APC_ITER_KEY ] { 1 }
  Constant [ integer APC_ITER_VALUE ] { 2 }
  Constant [ integer APC_ITER_NUM_HITS ] { 4 }
  Constant [ integer APC_ITER_MTIME ] { 8 }
  Constant [ integer APC_ITER_CTIME ] { 16 }
  Constant [ integer APC_ITER_DTIME ] { 32 }
  Constant [ integer APC_ITER_ATIME ] { 64 }
  Constant [ integer APC_ITER_REFCOUNT ] { 128 }
  Constant [ integer APC_ITER_MEM_SIZE ] { 256 }
  Constant [ integer APC_ITER_TTL ] { 512 }
  Constant [ integer APC_ITER_NONE ] { 0 }
  Constant [ integer APC_ITER_ALL ] { 4294967295 }
  Constant [ integer APC_BIN_VERIFY_MD5 ] { 1 }
  Constant [ integer APC_BIN_VERIFY_CRC32 ] { 2 }
  Constant [ boolean APCU_APC_FULL_BC ] { }
  }

from apcu.

During the installation it's shown with the right flags:
running: /tmp/pear/temp/apcu/configure --enable-apc-bc=yes --enable-apcu-debug=no
Debugging is also enabled afterwards - which is obviously wrong

from apcu.

I'm not familiar with the build chain but it looks like that it is only checked for "--disable-apc-bc" (config.m4 line 10) and the available pecl option is "--enable-apc-bc". Can you please check that?

from apcu.

--disable-apc-bc=no, tried that? Or even just ommit it, looking at the flow in m4 that could work.

from apcu.

Something is seriously wrong:

./configure --enable-apcu --disable-apc-bc=no
configure: error: invalid feature name: apc-bc=no

./configure --enable-apcu --enable-apc-bc=yes
[...]
checking if APCu should provide APC full compatibility support... no

./configure --enable-apcu
[...]
checking if APCu should provide APC full compatibility support... yes

from apcu.

We didn't need back compatibility, so we built it like this

configure --enable-apcu --disable-apc-bc

As you can see, without any value for option. @stefankleff, have you tried to configure just like

configure --enable-apcu ?

Cause bc is enabled by default.

from apcu.

I've edited my previous post: Without the argument it works. But it's still impossible to get BC while installing the package with "pecl install apcu[-beta]"

from apcu.

Any chance to get "pecl install apcu" to install with BC?
Maybe just switch not working prompt off and leave it with the default, 'til an other solution is found.

from apcu.

You don't get configure options when you use pecl ??

When I run pecl install I do get configure options, and even if they are ignored the default behaviour is (and is displayed to be with pecl install) to use BC ...

from apcu.

yes, I got that option, but whatever I choose, BC is disabled :(
That's why I suggested not to prompt for these config, as long as it is not working.

from apcu.

@ralfbecker please pull and try again, the option name was changed to --enable-apc-bc and it disables only if set to 'no'. In any other case, including passing no value or ommiting that option, will enable BC.

from apcu.

Thankyou @weltling

Excellent ...

from apcu.

........ ROLF 😆

from apcu.

windows version to check, will do tomorrow )

from apcu.

@weltling Did you create a new pecl release, as I still get 4.0.1 and if I reinstall it, apc_fetch still fails:
[root@EGroupware html]# pecl install channel://pecl.php.net/apcu-4.0.1
downloading apcu-4.0.1.tgz ...
Starting to download apcu-4.0.1.tgz (105,861 bytes)
........................done: 105,861 bytes
46 source files, building
running: phpize
Configuring for:
PHP Api Version: 20100412
Zend Module Api No: 20100525
Zend Extension Api No: 220100525
Enable full APC compatibility [yes] :
Enable internal debugging in APCu [no] :
building in /var/tmp/pear-build-roothKUC2y/apcu-4.0.1
running: /var/tmp/apcu/configure --enable-apc-bc=yes --enable-apcu-debug=no

[root@EGroupware html]# php -r 'var_dump(function_exists("apc_fetch"));'
bool(false)
[root@EGroupware html]# php -r 'var_dump(function_exists("apcu_fetch"));'
bool(true)

INSTALL instructions only show how to use phpize but not build a new pecl package :(

from apcu.

git clone https://github.com/krakjoe/apcu
cd apcu
phpize
./configure --with-php-config=path-to-php-config
make
sudo make install

Try that, pecl release to come ... (after windows checkingz)

from apcu.

@ralfbecker no, this config will obviously be delivered in the next release. I meant git pull.

That said, you can test if pecl would work, for that go into source tree and

pecl package package.xml
pecl install apcu-4.0.1.tgz

Then the pecl will install the package just created.

Thanks

from apcu.

exactly, or like @krakjoe said

from apcu.

Ok, build pecl package from git pull and it works:

[root@EGroupware apcu]# pecl package package.xml
Package apcu-4.0.1.tgz done
[root@EGroupware apcu]# pecl uninstall apcu
uninstall ok: channel://pecl.php.net/apcu-4.0.1
[root@EGroupware apcu]# pecl install apcu-4.0.1.tgz
46 source files, building
running: phpize
Configuring for:
PHP Api Version: 20100412
Zend Module Api No: 20100525
Zend Extension Api No: 220100525
Enable full APC compatibility [yes] :
Enable internal debugging in APCu [no] :

[root@EGroupware apcu]# php -r 'var_dump(function_exists("apc_fetch"));'
bool(true)

Thanks :-)

from apcu.

@ralfbecker thanks for the effort :)

from apcu.