This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: configure oddity

On Feb 22, 2011, at 11:30 AM, Peter O'Gorman wrote:
> I had a quick look at this, installing m4-1.4.15 and then autoconf-2.64 (using your new m4) will give you these differences - not only on Mac OS X.
> 
> Rebuilding autoconf-2.64 with m4-1.4.13 works. I did not try m4-1.4.14.

Ah, that explains it then, autoconf smelled out gm4 (unknown to me) and used it, and it was m4-1.4.15.  It chose this over m4, which was 1.4.6.  The newer m4 came from macports.

So, do we document that one needs m4-1.4.13 or older?  Ick.  Add a PREREQ line to exclude the known buggy version?  I fixed mine by rebuilding autoconf with the old m4 in the path and this fixed it.

export M4=gm4-1.4.6 before running autoconf also fixes it as well.

Thanks.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]