Do I understand it correctly that one would have to create the
config.h.in template file manually? Hmmm.
May I put a pointer here to that alternative with a pkg-config.h
derived from standard config.h? It has served as a good basis for me.
http://www.gnu.org/software/ac-archive/Miscellaneous/a
Hi there,
I've only a simple question. I try to understand the functionality of
autoconf (maybe later on automake).
So I went to the online docs and started to read (Now I'm using the info
site, that's a bit quickier.).
So far, so good. There is a description of configure.in, how to create
it, of
Hello,
In fact, I'm also a newbie about autotools, but as far as I understand, the
Makefile.in is a simple standard makefile where variables @VAR_NAME@ are set
by the configure script. You need only one Makefile.in in case you have a
project that use several folders.
Best regards,
David Burg.
-
Hi,
during installation of the newer alpha versions of VIM 6 on an os/390 unix
machine, I noticed that autoconf 2.5 produced a configure script that would
not run under os/390 unix. Bram Moolenaar switched from autoconf 2.13 to
autoconf 2.5 from his VIM 6.0 alpha H to alpha I. Alpha I and beyond
Russ Allbery <[EMAIL PROTECTED]> writes:
> Mike Castle <[EMAIL PROTECTED]> writes:
>
> > Personally, I'd vote for getting rid of AC_C_BIGENDIAN. No need to in
> > supporting poor programming.
>
> I use it to allow more optimized versions of algorithms like MD5 where you
> can skip additional m
Akim Demaille <[EMAIL PROTECTED]> writes:
> | Recap of problem: configure script doesn't generate config.h on the
> | basis of results from tests. Removing config.cache and rerunning
> | configure yeilds a correct config.h.
> |
> | > What version of Autoconf?
> |
> | 2.13 and 2.50.
>
> Hm...
