autoconf's "mktime" test gets stuck, takes too much CPU

Bug #546966 reported by Ori Avtalion
This bug report is a duplicate of:  Bug #323528: mktime bug back with gcc 4.3.2. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autoconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: autoconf

Using autoconf2.59 2.59-1 on lucid amd64.

When running the ${ac_cv_func_working_mktime+set} test, the "conftest" tool starts taking up a lot of CPU and doesn't stop.

To test:
$ apt-get source gawk # for example. happens with other source packages such as "cabextract"
$ cd gawk-3.1.6.dfsg
$ ./configure

The bad test will kick in after printing "checking for working mktime..."

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.