Thread View: gnu.utils.bug
2 messages
2 total messages
Started by Dave Gymer
Sat, 23 Jan 1993 02:21
Autoconf 1.3 - M4 include directive
Author: Dave Gymer
Date: Sat, 23 Jan 1993 02:21
Date: Sat, 23 Jan 1993 02:21
15 lines
1036 bytes
1036 bytes
Was there any good reason for undefining the include M4 builtin? Groff 1.06 uses it, and I've been using it in my geeks package; I can't see what harm it could do, and it makes the configure.in file much neater. I'm know virtually nothing about M4, and don't want to, so my two basic questions are: 1) is there a good reason to disable include in Autoconf, and 2) if so, is there any other way round it? I've been thinking about trying Metaconfig for a while; it'd be a shame for something this trivial to be the ``straw that broke the camel's back''. Regards, -- Dave Gymer
Re: Autoconf 1.3 - M4 include directive
Author: David J. MacKenzie
Date: Tue, 26 Jan 1993 02:07
Date: Tue, 26 Jan 1993 02:07
19 lines
1352 bytes
1352 bytes
> Was there any good reason for undefining the include M4 builtin? Yes -- someone wanted to put some text like "-I/fubar/include" in configure.in, but GNU m4 was eating the word "include". > Groff 1.06 uses it, and I've been using it in my geeks package; I > can't see what harm it could do, and it makes the configure.in file > much neater. The aclocal.m4 files (autoconf looks for one in libdir and one in the current directory) should be a sufficient replacement, at least for what groff does. > I'm know virtually nothing about M4, and don't want to, so my two > basic questions are: 1) is there a good reason to disable include in > Autoconf, and 2) if so, is there any other way round it? If you really want to use include still, you can access it via the "builtin" macro.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads