Can I compile PHP to control the extended directory and extension files?

Environment: CentOS 7, PHP 5.4.16
Originally compiled PHP 7, encountered two problems, and then with PHP 5.4.16 verified, these two problems still exist.
The simplified compilation commands are:

./configure --prefix=/usr --enable-fpm --enable-mbstring=sharedmake && make install

1. Extension Files directory:
Is it possible to specify the directory of the extension files during the compilation process?
When installing PHP with Yum, the extended directory is:

/usr/lib64/php/modules

While compiling the installation, the extended directory is

/usr/lib/php/extensions/no-debug-non-zts-20100525

Try to --extension-dir do compile parameters, not supported.
Would you like to be able to control the extended directory when compiling the installation?

2.. a files in the compiled directory:
After compiling, entering the extension directory, you can see that, in addition to the generally needed. So files, each extension also has a. a file.
Like what:

Excuse me, what is this. a file for? Can I not generate this file by compiling parameters?
In addition: When the PHP compilation is completed, the extension is compiled separately, there will be no. a file.

Reply content:

Environment: CentOS 7, PHP 5.4.16
Originally compiled PHP 7, encountered two problems, and then with PHP 5.4.16 verified, these two problems still exist.
The simplified compilation commands are:

./configure --prefix=/usr --enable-fpm --enable-mbstring=sharedmake && make install

1. Extension Files directory:
Is it possible to specify the directory of the extension files during the compilation process?
When installing PHP with Yum, the extended directory is:

/usr/lib64/php/modules

While compiling the installation, the extended directory is

/usr/lib/php/extensions/no-debug-non-zts-20100525

Try to --extension-dir do compile parameters, not supported.
Would you like to be able to control the extended directory when compiling the installation?

2.. a files in the compiled directory:
After compiling, entering the extension directory, you can see that, in addition to the generally needed. So files, each extension also has a. a file.
Like what:

Excuse me, what is this. a file for? Can I not generate this file by compiling parameters?
In addition: When the PHP compilation is completed, the extension is compiled separately, there will be no. a file.

