php and LFS

Elan Ruusamäe glen at pld-linux.org
Wed May 14 20:47:42 CEST 2014


On 14.05.2014 21:20, Elan Ruusamäe wrote:
> On 14.05.2014 16:47, Jakub Bogusz wrote:
>> On Wed, May 14, 2014 at 02:43:23PM +0300, Elan Ruusamäe wrote:
>>> but, i do see -D_GNU_SOURCE -D_LARGEFILE64_SOURCE in build logs... 
>>> ideas?
>> _LARGEFILE64_SOURCE enables 64-bit file API, but with separate names.
>> To get them available under base names, _FILE_OFFSET_BITS=64 must be
>> used.
>
>
> is it safe to add it to CFLAGS?
>
> i found this ticket https://bugs.php.net/bug.php?id=45942
>
and this one
https://bugs.php.net/bug.php?id=45040

also the LFS flags found from log came from apr config:
/usr/bin/apr-1-config:CPPFLAGS="-DLINUX -D_REENTRANT -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE"

php itself has PHP_SYS_LFS macro in acinclude.m4, but it's never 
referenced in php-src
https://github.com/php/php-src/blob/php-5.5.12/acinclude.m4#L1568-L1612

the getconf class, that it would use are:

$ getconf LFS_CFLAGS
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
$  getconf LFS_LDFLAGS

$  getconf LFS_LIBS

$

if we rebuild with "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64", will that:
1) decrease performance of php as said in bug 45942
2) would require rebuild all php extensions? or funny things will happen?

-- 
glen



More information about the pld-devel-en mailing list