Hi Robert,
* Robert Lowe wrote on Fri, Feb 10, 2006 at 05:36:23AM CET:
> Ralf Wildenhues wrote:
> >
> >Well, m4 macros have no way to guard against overwriting or anything.
> >So the only way to have "namespaces" (note the quotes) is to use some
> >sort of simple criterion for where the macro come
Noah Misch wrote:
On Wed, Feb 08, 2006 at 11:47:37PM -0600, Robert Lowe wrote:
Hi,
Until today I had never tried autoreconf. I have always used a simple
shell script like:
The script runs just fine, but autoreconf complained about my use of
AC_CREATE_STDINT_H, insisting that I use m4_pa
Ralf Wildenhues wrote:
Hi Ralf,
The script runs just fine, but autoreconf complained about my use of
AC_CREATE_STDINT_H, insisting that I use m4_pattern_allow, which I
did, and the problem vanished. But, would anyone explain what
happened and why? Does it perhaps have anything to do with th
On Wed, Feb 08, 2006 at 11:47:37PM -0600, Robert Lowe wrote:
> Hi,
>
> Until today I had never tried autoreconf. I have always used a simple
> shell script like:
> The script runs just fine, but autoreconf complained about my use of
> AC_CREATE_STDINT_H, insisting that I use m4_pattern_allow,
Hi Robert,
* Robert Lowe wrote on Thu, Feb 09, 2006 at 06:47:37AM CET:
>
> Until today I had never tried autoreconf. I have always used a simple
> shell script like:
*snip*
> The script runs just fine, but autoreconf complained about my use of
> AC_CREATE_STDINT_H, insisting that I use m4_patter
Hi,
Until today I had never tried autoreconf. I have always used a simple
shell script like:
#!/bin/sh
rm -f config.cache
rm -f acconfig.h
echo "- aclocal..."
aclocal -I m4
echo "- autoconf..."
autoconf
echo "- autoheader..."
autoheader
echo "- automake..."
#automake -a -v
automake -a
echo
