"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre On Apr 11, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
We are about to write new tools, typically autom4te, on top of
which autoheader, autoconf etc. will be rewritten. I'm fed up with
addressing portability issues on the
Alexandre Oliva wrote:
On Apr 12, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
aux means nothing and is not portable. auxdir is puke puke puke
Agreed. I still like AC_CONFIG_SUPDIR better than
AC_CONFIG_CONFIGDIR or AC_CONFIG_CFGDIR.
I do too. Akim has already given examples of
"Earnie" == Earnie Boyd [EMAIL PROTECTED] writes:
Earnie Alexandre Oliva wrote:
On Apr 12, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
aux means nothing and is not portable. auxdir is puke puke puke
Agreed. I still like AC_CONFIG_SUPDIR better than
AC_CONFIG_CONFIGDIR or
Akim Demaille wrote:
"Earnie" == Earnie Boyd [EMAIL PROTECTED] writes:
Earnie Alexandre Oliva wrote:
On Apr 12, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
aux means nothing and is not portable. auxdir is puke puke puke
Agreed. I still like AC_CONFIG_SUPDIR better than
Akim Demaille wrote:
"Earnie" == Earnie Boyd [EMAIL PROTECTED] writes:
Earnie Alexandre Oliva wrote:
On Apr 12, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
aux means nothing and is not portable. auxdir is puke puke puke
Agreed. I still like AC_CONFIG_SUPDIR better than
On Apr 12, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
Are we talking about the same thing? I'm referring to where
mkinstalldirs, config.guess, etc. will be instead of the top level...
Yeah. What do mkinstalldirs, install-sh, missing, depcomp, ylwrap,
etc have to do with config? They're
Hi,
I have a program (http://www.locus.cz/locus/) I'd like to
autoconfiscate. Among other interesting complications, it has a couple
of parsers generated with bison flex. As far as I
understand autoconf+automake (I *think* I'm asking about autoconf,
but even about that I'm not sure), the
Vaclav Barta writes:
I can define YFLAGS = -d in my Makefile.am and it will work on my
machine. What I'd like to ask, is, of course: is this the right,
autoconf-sanctioned, portable thing to do? And even better - would it be
possible to fix autoconf to handle this possibility?
This is an
Long story, because I'm not actually sure how to even report this to
get it fixed.
Autoconf 2.1.3 as shipped by Apple in MacOS X seems to include macros
that do not test for malloc() properly, causing test failures.
[localhost:/usr/bin] stuckey% ./autoconf --version
Autoconf
This macro is documented in the manual but I can't seem to find it in the
source. Is it obsolete?
Steven
Alexandre == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre On Apr 11, 2001, Akim Demaille [EMAIL PROTECTED] wrote:
Given that we want to promote config/
Alexandre Who's we?
Well, I for one, and it was something that arose a certain of times.
I do believe Gary too is one of the
11 matches
Mail list logo