|On May 25, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
|> # AC_LANG_BOLL_COMPILE_TRY(PROLOGUE, EXPRESSION)
| s/BOLL/BOOL/
Lps, thanks!
Is this a LK?
Akim Demaille <[EMAIL PROTECTED]> wrote
25 May 2000 18:26:51 +0200:
Is it really important for you to be able to use variables?
Yes. We symlink a number of source files to the build directory. The
number of files may vary for different targets. The source file name
varies depending on wh
On May 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> |On May 25, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> |> # AC_LANG_BOLL_COMPILE_TRY(PROLOGUE, EXPRESSION)
> | s/BOLL/BOOL/
> Lps, thanks!
> Is this a LK?
I cluldn't find a patch anywhere. Was that supplsed
jk: dju Y dfgg qwer tyu]
Akim> jk: dju Y dfgg qwer tyu]
Llps, slrry, I meant
Nl, but I wioo send lne!
Here is my proposal.
Index: ChangeLog
===
RCS file: /cvs/autoconf/ChangeLog,v
retrieving revision 1.652
diff -u -r1.652 ChangeLog
--- ChangeLog 2000/05/26 09:42:13 1.652
+++ ChangeLog 2000/05/26 10:15:47
@@ -1,3 +1,20 @@
+200
On May 26, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> + Find a means to extract integers from the compiler.
> + Use this technology to compute `sizeof' even when cross-compiling.
> + Ideas and initial suggestion by Kaveh Ghazi.
> + Binary search by Bruno Haible.
Ok
--
Ale
> I've been all through all the info docs that came with autoconf but I
> can't seem to find this one. How do I make my header files install in:
> $prefix/include/ppd instead of just $prefix/include
If "ppd" is the name of your package, then the standard way to do it is to
list the headers under
In the spirit of the Linux 2.4 TODO list, I thought I'd raise the question
of what is required before the next autoconf release. We all know that
there have been a significant number of fixes and enhancements in the CVS
sources that many projects would like to benefit from. What needs to be
done
First of all (answering a question in the Autoconf TODO), yes, this macro
needs to be renamed. There are to date three C "standards", only counting
those by ISO/ANSI. And there are also several ways of interpreting what
"standard C" refers to:
1) the compiler understands "standard" syntax, e.g.,
Okay, so there is a TODO list in the CVS archive that lists some items
"required for 2.15." However...
Is this list up-to-date? For one thing, many of the items listed there
don't seem critical enough to hold up a release, especially as many are in
autoconf 2.13 as well.
Incidentally, one of t
11 matches
Mail list logo
