home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!cs.huji.ac.il!amoss
- From: amoss@cs.huji.ac.il (Amos Shapira)
- Newsgroups: gnu.utils.bug
- Subject: Autoconfig's lack of configurability
- Date: 22 Jan 1993 21:13:39 -0500
- Organization: GNUs Not Usenet
- Lines: 29
- Sender: daemon@cis.ohio-state.edu
- Approved: bug-gnu-utils@prep.ai.mit.edu
- Distribution: gnu
- Message-ID: <9301220959.AA01508@falafel.cs.huji.ac.il>
-
- Hello,
-
- I've just looked into Autoconfig 1.3 and am a bit puzzled by the lack of
- configurability in a software which deals with flexibility of configurations
- of other software packages (got that? :).
-
- I'm raising this point because I can't install GNU m4 as 'm4' since it will
- break software which expect the regular behaviour. I must therefore install
- it under 'gm4', but then autoconfig won't find it. I can manually change it
- but this is not the 'right' way to go, IMHO.
-
- >From the little I know about autoconfig I think the following lines should be
- added when generating the 'bootstrap' configure script (why isn't autoconfig's
- own config.in supplied, just for educational purposes? Or am I overlooking
- something?)
-
- AC_DEFINE(m4)
- AC_PROGRAMS_CHECK(m4, gm4, m4)
-
- And change autoconf.sh to read
-
- @m4@ $MACROFILES $infile > $tmpout
-
- Hope this suggestion is accepted, and thanks very much for this wonderfull
- package.
-
- --Amos Shapira, CS System Group, Hebrew University, Jerusalem, Israel
- amoss@cs.huji.ac.il
-
-