t understand the details, so I was not sure how to
eliminate the one that might cause this problem.
I would be very grateful for some hints that would allow me to
proceed hunting this bug. (Ralf?)
Happy piping,
Stepan
2009-11-04 Stepan Kasal
* tests/autotest.at (parallel au
Hello,
a correction to my previous mail: one of the exhibits shown was
slightly incorrect, see below.
the output of the commands
> mkdir micro
> cd micro
> autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg' \
> ../bin/autom4te -B ../lib --language=autotest \
> $sourc
ish8.1.8.3], [tixwish8.1.8.3],
> [AC_MSG_ERROR("FATAL: tixwish cannot be found")])
> ])
The third and fourth parameter of this macro is a _value_ which would
be assigned to the variable. You cannot put there shell code or
a m
if test "x$TIXWISH" = x; then
AC_MSG_ERROR([[tixwish cannot be found]])
fi
fi
Regards,
Stepan Kasal
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
autoconf manual. If any question remain, I'll try to answer them.)
> Stepan Kasal wrote:
> > AC_ARG_VAR([[TIXWISH]], [[The tixwish program.]])
> > AC_CHECK_PROG([[TIXWISH]], [[tixwish]], [[tixwish]])
> > if test "x$TIXWISH" = x; then
> > AC_CHECK_PROG([
_size in
[0-9]*) ;;
*) enable_border_size=3 ;;
esac
AC_DEFINE_UNQUOTED(DEFAULT_SZ, $enable_border_size,
[Default border size.])
Hope this helps,
Stepan Kasal
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
alled with the package
3) get the hardwired default
If the package would install a default config file, you'd almost never
get to 3), so there is no need to make it settable by ./configure.
Yours,
Stepan Kasal
___
Autoconf mailing list
[EMA
th-border,
[set default border size for negative plots (mm)])],
...
but, of course, the following would be a disaster:
AC_ARG_WITH(border,
[[AS_HELP_STRING(--with-border,
[set default border size for negative plots
Hello,
the text below seems to relly be a bug report with a proposed fix.
So I take the liberty to forward it to the bug report address.
Regards,
Stepan Kasal
- Forwarded message from "Gerrit P. Haase" -
Date: Mon, 25 Oct 2004 13:46:43 +0200
From: "Gerrit P.
there are problems with it.)
Thank you,
Stepan Kasal
# AC_HEADER_RESOLV
#
AN_HEADER(resolv.h, AC_HEADER_RESOLV)
AC_DEFUN(AC_HEADER_RESOLV,
[AC_CHECK_HEADERS(sys/types.h netinet/in.h arpa/nameser.h sys/socket.h)
AC_CACHE_CHECK(for resolv.h,
ac_cv_header_r
Hello,
On Mon, Oct 25, 2004 at 06:16:40PM +0200, Reini Urban wrote:
> I'd better fix it upstream so they'll get it without any notice.
even if it gets to autoconf and they upgrade, they sill have to put
AC_HEADER_RESOLV to their configure.ac (unless they use autoscan).
Stepan
_
Hi,
On Wed, Oct 27, 2004 at 04:04:08PM +0200, Stephane Bortzmeyer wrote:
> Sure. Now, which one? In my shell, I do not have LD_LIBRARY_PATH nor
> LDFLAGS, nor CC, nor CFLAGS...
you can always use env to save both environments and then interpolate
to find the guilty one...
HTH,
Hello,
On Wed, Nov 10, 2004 at 09:16:38AM -0800, Noah Misch wrote:
> I posted three patches to autoconf-patches on 10/24/2004. Would anyone commit
> them or provide some review?
>
> http://lists.gnu.org/archive/html/autoconf-patches/2004-10/
>
> Stepan Kasal also has five pa
Hi,
On Sun, Nov 21, 2004 at 12:23:13AM -0800, Noah Misch wrote:
> In general, always double-quote a macro argument that you wish to make a
> literal; that is, an argument in which m4 should not expand quotation or macro
> calls. Quote an argument only once to simply protect internal commas and
>
Hello,
On Mon, Nov 22, 2004 at 07:57:10AM -0800, Bruce Korb wrote:
> Stepan Kasal wrote:
> > (I'm writing a patch to the autoconf manual which would mention this.)
well, I was wrong. The patch is already submitted and I don't plan to
work on it any more.
You c
s, and try to find out some mailing lists in the ical
documentation, or try to find some list where OSX developers and users
help each other.
HTH,
Stepan Kasal
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
Hello Henrique,
On Wed, Dec 01, 2004 at 10:13:45AM -0200, Henrique de Moraes Holschuh wrote:
> "If you're doing that, you're weird. Go away".
>
> The translation for that would be: Why the heck are you keeping
> auto-generated files in a RCS system? Get them out of there, they do NOT
> belong i
Hi,
On Wed, Dec 01, 2004 at 11:24:33AM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 01 Dec 2004, Stepan Kasal wrote:
> > I learned from that text how can autotools and CVS/svn combined.
> > Though I personally obey the rule ``no generated files in the RCS'',
>
Hi,
On Wed, Dec 01, 2004 at 11:35:58PM +0100, Alexandre Duret-Lutz wrote:
> Speaking of manuals, the FAQ section of the Automake manual also
> have a node called "CVS" and listing pros, cons, and workarounds.
I have noticed a typo there, see the patch below.
As usual, thank you very much for nice
t find ethernet.h])
fi
Have a nice day,
Stepan Kasal
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
BJS=$LIB@&[EMAIL PROTECTED]
AC_CONFIG_COMMANDS_PRE([[LIB@&[EMAIL PROTECTED])
AC_OUTPUT
Have a nice day,
Stepan Kasal
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
igure. If you call
../pkg-1.2.3/configure
you get a relative path, at least on my host (bash on GNU/Linux), while by
/home/me/tests/pkg-1.2.3/configure
you end up with an absolute path.
Perhaps ths documentation should say that the path ``may be relative''.
version.c:version.in
or
CONFIG_COMMANDS= CONFIG_LINKS= CONFIG_FILES=version.c:version.in \
CONFIG_HEADERS= ./config.status
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
tml
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
aps we should solve actual problems, not replace all occurences of
``sed''.
Have a nice year,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
27;' shoudl be portable enough, because
the sed program is trivial and the input line is short.
But perhaps I'm wrong and it's simpler to replace all occurences of sed,
(taking care of the beginning of the configure script, of course).
Thank you very much for the analysis of this p
Hello,
on a second thought, I see an alternate approach:
> > Have you encountered any problem on a particular platform?
>
> Yes. When building kdevelop from kde-3.3.2 on Solaris 2.6, 7,
> substitions in Makefile.in's with long lines gets truncated resulting
> in a dead build.
Well, to encounter
Hi,
On Wed, Dec 29, 2004 at 04:28:47PM -0600, Bob Friesenhahn wrote:
> On Wed, 29 Dec 2004, Robin Rowe wrote:
>
> >Hi. Is there a good example of how to set up an autoconf project to build
> >for both 32-bit and 64-bit without the output files clobbering each other?
> >How do I get the binaries i
Hi,
On Wed, Dec 29, 2004 at 05:04:35PM -0600, Albert Chin wrote:
> Prepending /usr/xpg4/bin to $PATH is likely to open up more problems.
> It's not the default on Solaris. And, probably for good reason (i.e.
> default behaviour is not what a typical Solaris user might expect).
yes, the official e
Hello,
On Wed, Dec 29, 2004 at 06:15:40PM -0600, Albert Chin wrote:
> I've posted a patch to autoconf-patches. I've added your name to the
> changelog entry for proper credit.
I saw it. I think my name can be removed, I didn't helped you (much).
(Just in case you'd write a second version.)
Step
Hi,
On Thu, Dec 30, 2004 at 10:34:45PM -0800, Robin Rowe wrote:
> Thanks to Stephen and Bob for the tips!
>
> Is there a project anyone knows of using the autoconf VPATH approach that I
> could look to as an example?
perhaps the easiest way is to use automake. Many projects use it, and they
all
day,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
],
[AC_MSG_ERROR([*** openexr dev header half.h not found ***])])
There may be more problems, this is the first which I see.
Tell us whether this helped.
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
file name to AC_CONFIG_FILES, my autoconf 2.59 doesn't complain.
Which version do you use?
Of course, when I run the configure script and the .in file is not available
at the moment AC_OUTPUT is executed, configure fails.
HTH,
Stepan Kasal
__
hould do something so that
-lIlmImf doesn't get into LIBS, perhaps omit the AC_CHECK_LIB test, the
header may be taken as evidence that the library is installed.
I hope my advices will help, though I'm just guessing because I don't have
enough e
Hello,
On Sat, Jan 01, 2005 at 12:16:08AM -0800, Paul Eggert wrote:
> Stepan Kasal <[EMAIL PROTECTED]> writes:
>
> > If /usr/xpg4/bin is available, insert it to the path at the beginning
> > of the configure script, in order to get working sed and awk.
>
> I'
Hi,
On Fri, Dec 31, 2004 at 03:09:21PM -0800, J.T. Conklin wrote:
> While AC_CONFIG_PKGCONFIG_IN() is very appealing, writing a script
> that takes similar arguments and generates a *.pc.in file that can
if understand your situation correctly, you can still use
AC_CONFIG_PKGCONFIG_IN to get the *
Hi,
4 months ago, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> > The fact of the matter is that some/many libraries have header files
> > which are OS/CPU/compiler dependent and there has to be a way to
> > record/work-around these dependencies so that the library headers work
> > right. This way
_default_prefix;; \
*NONE) exec_prefix=$prefix;;esac; echo $bindir"`
AC_PROGRAM([MY_PROGR], [mypr], [no], [$bindir_path:$PATH])
Of course, many other solutions are possible, you can use sed, for example.
HTH,
Stepan Kasal
___
Autoc
C_MSG_RESULT
doesn't make much sense to me.
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
_dir", $3))
First, the `$3' argument is underquoted. It is a description, so it could
easily contain a comma. Second, I see no need for the `ifelse'.
So I propose the patch attached to this mail.
BTW: what does it mean that the macro is in the legacy section of the CVS?
Regards,
ames
correctly. So I suggest to correct the assignments too.
An updated patch is attached to this mail.
Have a nice day,
Stepan Kasal
my previous mail:
> This code contains the following:
>
>ifelse($3, ,
> AC_DEFINE_UNQUOTED($1, "$ac_define_dir&
Hi,
On Mon, Jan 10, 2005 at 04:32:51PM +0100, Andreas Schwab wrote:
> Stepan Kasal <[EMAIL PROTECTED]> writes:
>
> > + ac_define_dir=`eval echo "\"[$]$2\""`
> > + ac_define_dir=`eval echo "\"[$]ac_define_dir\""`
>
> In t
Hi,
I'd like to comment on my code:
> eval ac_define_dir="\"[$]$2\""
> eval ac_define_dir="\"[$]ac_define_dir\""
The same effect can be achieved by the following:
eval eval ac_define_dir="\"\\\"[$]$2\\\"\""
not speaking about the possibility to assign
exec_prefix=$prefix
instead of
)
to your configure.ac to get this file generated.
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
ontain "DELIM\n".
- post process the list by the following sed program (untested):
:loop
/DELIM$/b ok
N
b loop
s/[&,]/&/g
s/[EMAIL PROTECTED]@/s,@&,/
s/DELIM$/,;t t/
I think this solution is general enough for practical purposes, yet it
presents no slowdown of configu
Hi,
On Fri, Jan 14, 2005 at 04:49:54PM +0100, Peter Simons wrote:
> I have applied the last patch you sent to the macro and
...
> dnl @author Stepan Kasal <[EMAIL PROTECTED]>, ...
Thanks. Perhaps we should give credit to Andreas, too.
There is still one problem with the macro
27; .
(The main point is that we have to escape real backslashes somehow.)
The post-processing program would recognize lines starting with @,
and decode them, for example:
/^@/!b ok
s/^@//
:loop
N
/\\$/b loop
s/\\x/\\/g
:ok
s/[&,]/&/g
s/[EMAIL PROTECTED]@/s,@
Hi,
On Wed, Jan 19, 2005 at 08:16:51PM +0200, Eli Zaretskii wrote:
> > CVS Autoconf also tackled this issue, see
> > http://lists.gnu.org/archive/html/autoconf-patches/2004-12/msg00057.html
...
> Unless I'm missing something, the above message from autoconf-patches
> does not solve this problem, s
Hi,
I have an idea for another AS_EXECUTABLE_P improvement. The following
explanation is somewhat complicated, but I couldn't help.
On systems supporting `test -x', AS_EXECUTABLE_P is
{ test -f $1 && test -x $1; }dnl
Let me remind, that test -x alone wouldn't be enough, because
it would
Hi,
On Thu, Jan 20, 2005 at 04:42:24PM -0800, Paul Eggert wrote:
> > 2) The autoconf manual says you cannot use `test ! -d' with `if'.
>
> Where does it say that? I couldn't find it.
under the description of bultin `test',
line 11085 of doc/autoconf.texi, currently.
Stepan
__
Hi,
On Fri, Jan 21, 2005 at 04:21:44AM +0100, Ralf Corsepius wrote:
> How about portability of "test -d" being applied to "special
> files" (char/block device files, pipes/sockets, soft/hard links to
> directories/files etc.)?
so the question is:
If I change AS_EXECUTABLE_P the proposed way, it
Hi,
On Fri, Jan 21, 2005 at 11:54:45AM +0100, Ralf Wildenhues wrote:
> * Stepan Kasal wrote:
> > 2) The autoconf manual says you cannot use `test ! -d' with `if'.
...
> | You may use @samp{!} with @command{test}, but not with @command{if}:
> | @samp{test ! -r foo || exi
Hi,
On Fri, Jan 21, 2005 at 07:17:17AM -0700, Eric Blake wrote:
> Actually, `test -f foo' only fails on foo.exe on DJGPP (at least,
> according to claims - I don't have a DJGPP environment to test on) - it
> works on cygwin.
anyway, it seems that changing AS_EXECUTABLE_P from
test -f $1
Hello,
let me post a summary of the thread ``AS_EXECUTABLE_P again'' which
I started on the autoconf list:
I proposed to change the implementation of AS_EXECUTABLE_P on platforms
supporting `test -x' from
test -f $1 && test -x $1
to
test -x $1 && test ! -d $1
But Paul has pointed o
Hello,
On Sat, Jan 22, 2005 at 06:23:25PM +0200, Eli Zaretskii wrote:
> > I proposed to change the implementation of AS_EXECUTABLE_P on platforms
> > supporting `test -x' from
> >test -f $1 && test -x $1
> > to
> >test -x $1 && test ! -d $1
> >
> > But Paul has pointed out the cha
Hi,
On Sat, Jan 22, 2005 at 08:52:16PM +0200, Eli Zaretskii wrote:
> > If there was a named pipe /tmp/foo with an executable bit set, the test
> > could misclasify it as an executable file.
...
> FWIW, I don't regard this as ``misclasification'', since the named
> pipe does, indeed, have its execu
der, just after including config.h.
Or you can leave there your original code, it's not bad. Perhaps like
this:
case $enable_netcdf_4 in
yes) ac_use_netcdf4_num=1;;
*) ac_use_netcdf4_num=0;;
esac
AC_DEFINE_UNQUOTED([USE_NETCDF4], [$ac_use_netcdf4_num],
each script should be enough to do most of
the optimization.
So I'd like to say again a big *thank you* for your work. It's not bad,
as an Englishman would put it.
Are you willing to donate more work and incorporate my suggestions to your
patch?
Have a nice day,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
c])
(no space), so that m4 understands it as a parameter.
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
rst gcc command it creates the main.o file why
> not when using make ?
Please not that the first command is
/bin/sh ./depcomp ...
So the gcc ... are in fact parameters to the depcomp script.
Try running the whole
source='main.c' ... /bin/sh ./depcomp ...
Does it c
Hello Dan,
On Tue, Jan 25, 2005 at 01:15:22PM -0500, Dan Manthey wrote:
> On Tue, 25 Jan 2005, Stepan Kasal wrote:
> No single delimiter is guaranteed to be in none of the output variable
> values. However, since they are all finite, there is guaranteed to exist
> some string that i
/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
s/?/?q/g
...
- start a loop which processes the subst variables
I find this approach quite straightforward, and I don't see any need
for diversions.
I think it might be easier to count `sed commands' instead of
`substitutions' in this ca
Hi,
On Fri, Jan 28, 2005 at 10:30:27AM +0100, Ralf Wildenhues wrote:
> > > ... s/x\{23\}/yes/ ... is not portable
...
> I think it is safe to use [...]
so I was just wrong, sorry.
Stepan
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.o
Hi,
On Sun, Jan 30, 2005 at 04:15:52PM -0800, Bruce Korb wrote:
> On Sunday 30 January 2005 03:53 pm, Andreas Schwab wrote:
> > Sure it does. "--gnu" comes from AUTOMAKE_OPTIONS in Makefile.am or from
> > AM_INIT_AUTOMAKE, and "--add-missing" is added with "--install".
...
> I haven't tried the
Hi,
On Wed, Feb 02, 2005 at 02:57:48PM -0800, Uday Krishnan wrote:
> How do I gain read access to the autoconf source code.
see http://www.gnu.org/software/autoconf/
> thx, u.k.
u r welcome
s
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gn
it is possible that there is a common prerequisite of both macros; it'd
get expanded just before AC_MACRO_ONE, so it could be skipped and
AC_MACRO_TWO cound fail.
So you have to be very careful with macro calls which are not always
reached.
Have a nice day,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
ler output for both objects.
> I just don't want to miss any warnings or errors from the compiler.
You won't.
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
emain unset.
> AC_MSG_CHECKING([prefix for libraries and headers])
...
> AC_MSG_RESULT([yes])
I believe you are too verbose here. Determining the value of one variable,
moreless directly set by the user, doesn't qualify as a `check' in my eyes.
HTH,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
Hi,
> > I instead just ask `test ${#ac_delim} -gt 1000', which gives six
> > iterations with the current set up.
>
> ${#} isn't portable. I think this is:
> _len=`expr "${ac_delim}" : ".*"`
but this is ugly. Something like:
for f in 0 1 2 3 4 5 6; do
test $f = 6 && AC_MSG_ERROR(...)
Hi Dan,
nice piece of work, thank you.
On Mon, Feb 07, 2005 at 03:55:49PM -0500, Dan Manthey wrote:
> > 3) ad: the implementation of non-recursive substitution:
> >
> > All the hacks with |[EMAIL PROTECTED]@#| are too complicated and not
> > general enough.
> > There is a better solution.
> >
hat I had to change the value assigned to exec_prefix,
and I had to add one more `eval' on that account.
The reason is that in the generated Makefiles, you should see:
exec_prefix = ${prefix}
not the value of $prefix. This subtle difference enables the following:
Hi,
On Tue, Feb 08, 2005 at 12:44:46PM +0200, Philippe Trottier wrote:
> eval test -d `echo $libdir | sed 's,exec_prefix,prefix,'` &&
> eval LDFLAGS="-L`echo $libdir | sed 's,exec_prefix,prefix,'`
no big deal, what if I run
./configure --prefix=$HOME/myexec_prefix
?
Ste
Hi,
On Tue, Feb 08, 2005 at 01:52:49PM -0500, Dan Manthey wrote:
> This is probably just a consequence of being OCD enough to write
> autoconf code in the first place.
:-)
> On Tue, 8 Feb 2005, Stepan Kasal wrote:
> > I'm glad to generate hints. But I have stated several
Hi,
I apologize that I write in two pieces again.
You often use: m4_eval(_AC_SED_CMD_NUM+1)
Are you aware of m4_incr(_AC_SED_CMD_NUM) ?
I think it's more readable, but your preferences might differ.
Yours,
Stepan
___
Autoconf mailing list
Hin
On Tue, Feb 08, 2005 at 02:37:59PM -0500, Dan Manthey wrote:
> Does anyone have any feelings on this?
> +m4_define([AS_CASE_PATTERN],
> +[m4_if($#,0,[[$0]],$#,1,[[$1 ) ]],[[$1 | ]$0(m4_shift($@))])])
Wouldn't a simple
m4_define([AS_CASE], [$1)])
serve the same purpose?
Stepan
__
Hi,
On Sat, Feb 05, 2005 at 01:01:03AM +0100, Gregorio Guidi wrote:
> I think the 'standard' way to use AC_ARG_WITH (from the packager's point of
> view) in a case such as the acl one, should be like this:
> If the user gave --without-acl, disable acl support
this is usual practice, there is not
This second approach has bigger chance to break existing script; it might
be possible to introduce this kind of dependency with a new name, perhaps
AC_PREREQ, ``prerequired'' macros.
Both suggestions lead to multiple expansions of AC_TEST2, but I don't
think this is a big
Hi Paul.
On Thu, Feb 10, 2005 at 09:25:07AM -0800, Paul Eggert wrote:
> Why not implement this stuff using "make" rather than "sh"?
> "make" is designed for dependency handling; the shell isn't.
>
> (If that's too drastic for you, I suppose we could reimplement "make"
> in the shell. :-)
Sure,
Hi Dan,
On Fri, Feb 11, 2005 at 11:28:17AM -0500, Dan Manthey wrote:
> On Fri, 11 Feb 2005, Stepan Kasal wrote:
> > Sure, I like declarative languages. It might be even easier to use
> > then the macro language we use now.
> > [comments on make]
> Okay, was I the
is used.
I have just verified that the patch patch below doesn't break autoconf's
make check.
Paul, OK to commit this?
Stepan
2005-02-12 Stepan Kasal <[EMAIL PROTECTED]>
* lib/m4sugar/m4sh.m4 (AS_IF): Define by m4_defun, not m4_define.
This causes that any requ
Hi Paul,
On Sat, Feb 12, 2005 at 11:22:01PM -0800, Paul Eggert wrote:
> No, you'd invoke "make" just once (just as you invoke "configure" just
> once). "configure" would invoke "make" with an appropriate makefile.
> The makefile would do all the real work.
>
> Make (1) handles dependencies well,
aulting to yacc;
what alternatives to gperf do you want to check for.
About Automake: I guess that the generic support described in
(automake.info)Suffixes might be enough to handle gperf sources.
If I'm wrong, please describe a concrete problem in a posting to the
automake list.
Hi,
On Mon, Feb 14, 2005 at 10:25:56AM -0800, Paul Eggert wrote:
> Stepan Kasal <[EMAIL PROTECTED]> writes:
> > I think the solution which uses functions to implement dependencies is
> > much more practical.
>
> Fair enough. But why not support parallelism while you&#
Hi,
On Tue, Feb 15, 2005 at 03:03:10PM +0100, Gregorio Guidi wrote:
> > > Stepan Kasal <[EMAIL PROTECTED]> writes:
> > > > I think the solution which uses functions to implement dependencies is
> > > > much more practical.
>
> Wouldn't it be po
Hi,
I haven't read Dan's mail yet, but I want to reply to this:
On Tue, Feb 15, 2005 at 05:09:17PM -0800, Paul Eggert wrote:
> [...] I'm now seeing many cases where it takes longer to run
> "configure" than to run the following "make"! It's getting ridiculous.
no surprise. It takes much time
Hi,
On Wed, Feb 16, 2005 at 12:57:20PM -0500, Dan Manthey wrote:
> Well, trivially, it's possible to run an arbitrary number of tests
> together and see if _none_ of them fail: `cc foo.c bar.c' and then only
> run them separately if there is a failure. it might also be possible with
> some
Hello,
On Thu, Feb 17, 2005 at 11:28:08AM +0100, Gregorio Guidi wrote:
> > actually, I believe that both my proposals will get actually implemented.
> > But the AS_IF solution is already checked in to the autoconf CVS.
>
> If there will be another solution, I would prefer to avoid AS_IF.
we cann
Hi,
On Thu, Feb 17, 2005 at 06:18:14PM +0100, JRBCAST wrote:
> My question is: How can I set a default progra-prefix [...]
> ./configure --program-prefix=foopref_
case $program_prefix in
NONE) program_prefix=my_default_ ;;
esac
should do the trick.
Put it somewhere between AC_INIT and AC_OUTPUT
Hello Dan,
I'll try to answer; it's quite possible that Paul will correct me.
On Fri, Feb 18, 2005 at 11:55:27AM -0500, Dan Manthey wrote:
> checking for a type like uint_fast32_t... (This may take a while.)
> checking for blah...
> ...
> checking finished for a type like uint_fast32_t... found
Hi,
I read the macro _AS_ECHO_N_PREPARE:
m4_defun([_AS_ECHO_N_PREPARE],
[case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
*c*,-n*) ECHO_N= ECHO_C='
' ECHO_T=' ' ;;
*c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
*) ECHO_N= ECHO_C='\c' ECHO_T= ;;
esac
])
I have several
; case $LEX in
> :) AC_MSG_ERROR([No lex program found]);;
> esac
You also mentioned AC_PROG_YACC; the situation is a bit different there.
I suggest that you replace the call with:
AC_CHECK_PROGS(YACC, 'bison -y' byacc yacc, :)
and then you can again test for : to see whether yacc was fou
tus=1; break; fi
done
return $ch_status
}
Have a nice day,
Stepan Kasal
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
Hi,
On Fri, Feb 25, 2005 at 08:14:34AM +0100, Harald Dunkel wrote:
> If you put some other values here, then you get
>
> 0.007 > 0.42
yes, you are right. But it's easy to fix paul code:
# Example inputs
a=0.011
b=0.10
newline='
'
both=`echo "$a$newline$b" | sed 's/\.0*/./g'`
sorted=`
echo
Hello Pat,
On Fri, Feb 25, 2005 at 01:24:30AM +0100, Patrice Dumas wrote:
> configure: error: conditional "AMDEP" was never defined.
> Usually this means the macro was only invoked conditionally.
[...]
> By chance are you aware of a possible workaround?
a quick hack could be to place
AMDE
Hi,
On Thu, Feb 24, 2005 at 03:25:38PM -0800, Paul Eggert wrote:
> Dan Manthey <[EMAIL PROTECTED]> writes:
> > Of course, if we decide that functions "are portable", we can skip the
> > step of designing the hairy workaround.
>
> I think we can decide that for Autoconf version 3, but not for
> Au
Hi,
please forgive me that I reply to my own post.
I'd like to post a short summary:
Three possible fixes were proposed:
1) AC_DEFUN(AS_IF)
2) AC_REQUIRE could expand the macro to a section near the begining of
the script.
3) In "autoconf with functions", AC_REQUIRE could expand to code
Hi,
a quick comment.
On Thu, Feb 24, 2005 at 02:58:14PM -0500, Dan Manthey wrote:
> Actually, we've already got AS_IF [...] but using that may conflict
> with part of the proposal for conditional macros; don't know yet.
I don't think we should expect any conflicts. We should encouradge
wide us
Hi,
let me formulate a proposal. I try to be as specific as possible.
AC_MSG_NEED(PACKAGE, TEXT)
--
Prints a message and saves it for later usage.
Example: AC_MSG_NEED(foo, [grab the latest foo from foo.org])
prints:
Suggestion:
foo grab the latest foo f
Hi,
On Tue, Mar 01, 2005 at 02:16:53PM -0800, Paul Eggert wrote:
> Stepan Kasal <[EMAIL PROTECTED]> writes:
>
> > AC_MSG_NEED(PACKAGE, TEXT)
> > --
> > Prints a message and saves it for later usage.
>
> My main comment is that
1 - 100 of 415 matches
Mail list logo
