In message <[EMAIL PROTECTED]>
Russ Allbery <[EMAIL PROTECTED]> wrote:
> Dan Kegel <[EMAIL PROTECTED]> writes:
>
> > Standard practice is probably to always write
>
> > #if HAVE_SYS_TYPES_H
> > #include
> > #endif
>
> There's no need to check for the existance of unless you're
> at
| > You want autoconf -f then.
| -f, --force consider all files obsolete
|
| We do a ./cvsclean right now for autoconf +2.50 which purges
| all generated data. I guess that is basically the same.
|
| > You know, you are typically the kind of people who has valid grieve
I am having problems
building Autoconf 2.54. Currently I have libtool 1.4.2, m4 1.4 and
automake 1.7 installed.
To build, I used the
commands:
./configure
--prefix=/export/local/gnu/autoconf
make
My results
are:
Making all in
bin
Making all in
tests
Making all in
.
making all in
You don't mention your platform, but there is a known incompatibility
of Autoconf 2.54 with traditional Unix make in that area. Please see:
http://mail.gnu.org/pipermail/autoconf-patches/2002-September/008689.html
http://mail.gnu.org/pipermail/autoconf-patches/2002-September/008692.html
This pr
Stewart Brodie <[EMAIL PROTECTED]> writes:
> I still tend to check for it on the basis that I check all other header
> files, so I might as well check that one. There are systems that do not
> have sys/types.h. That way, all header file checks are done the same
> way. That also means that I al
