gtest.m4: configure fails when --enable-gtest is absent

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a configure.ac that uses GTEST_LIB_CHECK, and run autoreconf.
2. Run configure without specifying --enable-gtest or --disable-gtest.
3. Observe the result.

What is the expected output? What do you see instead?
Expected: configure should find the location of gtest-config automatically. 
Actual: It can't, resulting the following message:

configure: error: Unable to locate either a built or installed Google Test.
The specific location '' was provided for a built or installed
Google Test, but no 'gtest-config' script could be found at this location.

What version of the product are you using? On what operating system?
gtest-1.3.0, Fedora 11 (i386)

Please provide any additional information below.
With --enable-gtest, configure successfully runs.

Since default is enabled, the behaviour of configure script should not
change based on the presence of --enable-gtest (unless --disable-gtest is
specified).

Original issue reported on code.google.com by k...@ketan.jp on 22 Aug 2009 at 9:38

[GoogleCodeExporter]

Suggested fix.

Original comment by k...@ketan.jp on 22 Aug 2009 at 9:40

Attachments:

• gtest-m4.diff

[GoogleCodeExporter]

Chandler or Benoit, could you take a look when you have time?  Thanks.

Original comment by zhanyong...@gmail.com on 3 Sep 2009 at 6:43

• Changed state: Accepted
• Added labels: OpSys-Linux, Priority-Low, Usability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

We are switching away from autotools.

Original comment by w...@google.com on 23 Dec 2009 at 7:05

• Changed state: WontFix