Backport #6316
closedconfigure script fails to detect executables
Description
=begin
When running (({./configure})) on the git master branch, it fails to detect several executables which are present. See ((<Stack Overflow question and answer|URL:http://unix.stackexchange.com/questions/36688/why-doesnt-rubys-configure-script-detect-my-executables-and-header-files>)) for details.
The cause is essentially that (({AC_CHECK_PROG})) takes three arguments, but only two are provided.
=end
Files
Updated by shyouhei (Shyouhei Urabe) over 12 years ago
- Status changed from Open to Assigned
- Assignee set to nobu (Nobuyoshi Nakada)
Updated by nobu (Nobuyoshi Nakada) over 12 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r35387.
Victor, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
- configure.in (DOT, DOXYGEN): use AC_CHECK_PROGS instead of
AC_CHECK_PROG which needs the third argument. [ruby-core:44433]
[Bug #6316] - configure.in (PKG_CONFIG): fix condition to skip older version
of pkg-config. continue in backticks does not affect outside.
Updated by nobu (Nobuyoshi Nakada) over 12 years ago
- Tracker changed from Bug to Backport
- Project changed from Ruby master to Backport193
- Category deleted (
build) - Status changed from Closed to Open
Updated by nobu (Nobuyoshi Nakada) over 12 years ago
- Status changed from Open to Closed
This issue was solved with changeset r35388.
Victor, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
merge revision(s) 35387:
* configure.in (DOT, DOXYGEN): use AC_CHECK_PROGS instead of
AC_CHECK_PROG which needs the third argument. [ruby-core:44433]
[Bug #6316]
* configure.in (PKG_CONFIG): fix condition to skip older version
of pkg-config. continue in backticks does not affect outside.