s is completely different from gnu-m4, it is less likely
that autoconf will depend on `undocumented features' of gnu-m4 in the
future.
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don&
lf.
I'll just argue if I feel the FSF is picking on us... :)
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
such an interesting test application when you're enhancing m4...
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
On Thu, Mar 15, 2001 at 04:10:25PM +0100, Akim Demaille wrote:
>
> If people think this is a useful addition, why not, but I tend to
> think the current text is already clear enough. And a system specific
> section seems not too good an idea to me.
No, this is definitely a useful addition. Note
On Thu, Mar 15, 2001 at 07:13:24PM +0100, Akim Demaille wrote:
> >>>>> "Bruno" == Bruno Haible <[EMAIL PROTECTED]> writes:
> Bruno> Marc Espie writes:
> >> which would tend to indicate to me that even knowledgeable people
> >> don
On Thu, Mar 15, 2001 at 07:23:15PM +0100, Akim Demaille wrote:
> >>>>> "Marc" == Marc Espie <[EMAIL PROTECTED]> writes:
>
> Bruno> Also, on HP-UX my first attempt was "cc", my second was "cc
> Bruno> -Aa", my third was "
I wrote:
> Marc> I don't have any objection to guessing at -I/usr/local/include
> Marc> and -L/usr/local/lib on BSDs...
Actually, I have one reservation. This MUST be overridable by the
person running configure.
In the first place, we do want to be able to build the system without
getting influ
On Fri, Mar 16, 2001 at 01:16:10AM -0500, Greg A. Woods wrote:
>
> Strictly speaking such systems as the *BSD ports/pkgsrc should not be
> running the configure but should instead have pre-canned configurations
> ready to use.
>
> Configure is just too damn smart for any package building system,
>@node Why GNU m4
>@section Why Require GNU M4?
>
>@display
>Why does Autoconf require @sc{gnu} M4?
>@end display
>
>Many M4 implementations have hard-coded limitations on the size and
>number of macros that Autoconf exceeds. They also lack several
>builtin macros that it would be difficult to ge