Red Hat Bugzilla – Bug 55924
autoconf produces invalid output with some input
Last modified: 2007-04-18 12:38:09 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.5) Gecko/20011014 Description of problem: autoconf generates invalid output (configure) from some valid input (configure.in). This started happening when autoconf was upgraded to autoconf-2.53. additionally, autoconf seems *much* slower and the following directory is left behind after autoconf completes... autom4te.cache Is this a release version of autoconf or what? hehehe Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.get ftp://qoop.org/ninja/sources/ninja-1.5.5.tar.gz 2.uncompress (gzip -cd ninja*gz | tar xf -) 3.cd ninja-*5.5 4.autoconf Actual Results: when running autoconf: fear:ninja-1.5.6> autoconf configure.in:1: error: possibly undefined macro: dnl when running produced configure: checking for sigaction... yes ./configure: line 6253: syntax error near unexpected token `else' ./configure: line 6253: `else' Expected Results: 1. autoconf completion without error 2. configure complete successfully Additional info: Also, shouldn't autoconf check for presence and THEN usability of include files? Doesn't usability require presence?! from ./configure output --- checking sys/select.h usability... yes checking sys/select.h presence... yes ---
"autoconf --version" kind of gives the game away! Yes, I can reproduce this with both autoconf-{2.50,2.52{,d,g}}. However it is not clear with current information whether the problem with your configure.in is an autoconf bug or not. autoconf-2.52 differs considerably from autoconf-2.13 (the previous release), and unfortunately some of the changes made break backwards compatibility, which is quite likely what you're experiencing. If you can pinpoint down the part of your configure.in that is causing the above error, then I will be able to help further. I asked on the autoconf list about the order the header usability and presence testing?
I'm not an autoconf expert, but I believe the problem is getting triggered somewhere in the signal checking... about line 428.. Is there some place where I can find out what is not backwards compatabile?? It seems like all the new software thats coming out is taking a step backwards instead of forwards... ncftp even got rid of the "bgget -R" command! man..
ninja-1.5.8.1 seems to be ok with autoconf-2.52 and 2.53. Did you find the problem or work around it?
yeah i did manage to fix it, but now it doesn't work with the old one, heheheh i'm not sure if its worth it to try to get it to work with both.. its stuff inherited from ircII anyway
you mean ninja now doesn't work with autoconf-2.13, right? Well, if it works with the current autoconf, I would be happy with that. :)