This causes the Symfony Process component's `sigchild` detection to
default to "no". From my inspection of the `debian/rules` file in for
latest PHP package, this happens to be the correct behavior for the
Process component to take, but this is simply out of dumb luck. What
happens when/if that
This affects whoever needs to detect the state of the interpreter their code is
running in, much like ini_get() is used to get ini settings.
In my case, I need to detect if PHP was compiled with --enable-sigchild so that
I know how to handle proc_close() calls.
--
You received this bug
For now, there is an inconvenient and inefficient workaround:
Execute process 'php-config --configure-options' and parse the output.
But that'll probably not work in Windows.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
For now, there is an inconvenient and inefficient workaround:
Execute process 'php-config --configure-options' and parse the output.
But that'll probably not work in Windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This affects whoever needs to detect the state of the interpreter their code is
running in, much like ini_get() is used to get ini settings.
In my case, I need to detect if PHP was compiled with --enable-sigchild so that
I know how to handle proc_close() calls.
--
You received this bug
I agree with those commenting in favor of including config info. I tried
reading through debian/rules, and it is still unclear to me what the
configuration of the compiled php is on my machine. For many users who
aren't super familiar with shell scripts, it is difficult to garner this
information
** Changed in: php5 (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
configure command line missing from phpinfo
To manage
I agree with those commenting in favor of including config info. I tried
reading through debian/rules, and it is still unclear to me what the
configuration of the compiled php is on my machine. For many users who
aren't super familiar with shell scripts, it is difficult to garner this
information
** Changed in: php5 (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
configure command line missing from phpinfo
To manage notifications
I think removing standard, expected information as to not confuse
users is a bad move; issues with ambiguity in the build options are
entirely separate from accurately displaying what they actually are.
Consider this use case: I need to build php with --debug and --disable-
zend-memory-manager to
(that should be --enable-debug)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
configure command line missing from phpinfo
To manage notifications about this bug go to:
I think removing standard, expected information as to not confuse
users is a bad move; issues with ambiguity in the build options are
entirely separate from accurately displaying what they actually are.
Consider this use case: I need to build php with --debug and --disable-
zend-memory-manager to
(that should be --enable-debug)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
configure command line missing from phpinfo
To manage notifications about this bug go to:
Simply saying peruse debian/rules doesn't help much.
It isn't clear at all. The debian/rules file is 761 lines long.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
Simply saying peruse debian/rules doesn't help much.
It isn't clear at all. The debian/rules file is 761 lines long.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516061
Title:
configure command
The removal of Configure Command from phpinfo was intentional, see
debian/patches/052-phpinfo_no_configure.patch
In short, it led to many (many!) bugs from users claiming that extension
X, Y, or Z wasn't built for PHP in Debian/Ubuntu, do to entirely
misinterpreting what the string actually
The removal of Configure Command from phpinfo was intentional, see
debian/patches/052-phpinfo_no_configure.patch
In short, it led to many (many!) bugs from users claiming that extension
X, Y, or Z wasn't built for PHP in Debian/Ubuntu, do to entirely
misinterpreting what the string actually
** Changed in: php5 (Ubuntu)
Importance: Undecided = Low
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
configure command line missing from phpinfo
https://bugs.launchpad.net/bugs/516061
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: php5 (Ubuntu)
Importance: Undecided = Low
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
configure command line missing from phpinfo
https://bugs.launchpad.net/bugs/516061
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Why is that important and should be fixed?
./configure line is different for each SAPI anyway.
--
configure command line missing from phpinfo
https://bugs.launchpad.net/bugs/516061
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
php -i and phpinfo() are commenly used to check for the exact configure
options passed to PHP ... so basically users expect this output to be
there.
Also, the official PHP documentation mentions it.
http://ca3.php.net/phpinfo contains in particular
INFO_GENERAL1The configuration
I can see several benefits to its presence in the output:
1) educational
2) as a starting point for a new PHP compilation ... basically get that line,
modify what you need and you'll be able to recompile PHP
Below a sample output from a CentOS 5 installation:
# php -i
phpinfo()
PHP Version =
Why is that important and should be fixed?
./configure line is different for each SAPI anyway.
--
configure command line missing from phpinfo
https://bugs.launchpad.net/bugs/516061
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
php -i and phpinfo() are commenly used to check for the exact configure
options passed to PHP ... so basically users expect this output to be
there.
Also, the official PHP documentation mentions it.
http://ca3.php.net/phpinfo contains in particular
INFO_GENERAL1The configuration
And what do you need it for?
As I said before, since every SAPI is compiled with different options
(modules are built only once), it's output is practically useless.
So what information do you expect to be there and you are missing right
now?
It probably an upstream build script failure, which
I can see several benefits to its presence in the output:
1) educational
2) as a starting point for a new PHP compilation ... basically get that line,
modify what you need and you'll be able to recompile PHP
Below a sample output from a CentOS 5 installation:
# php -i
phpinfo()
PHP Version =
26 matches
Mail list logo
