Possible stupid question, but could someone explain, why required
macros (at least such my impression from reading the Autoconf info)
like AT_PACKAGE_NAME, AT_PACKAGE_VERSION, AT_PACKAGE_BUGREPORT are
required to be defined by user while they can be defaulted from the
AC_PACKAGE_NAME, AC_PACKAGE_VE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding bug-automake]
According to Andrew W. Nosenko on 3/3/2009 4:12 AM:
> Possible stupid question, but could someone explain, why required
> macros (at least such my impression from reading the Autoconf info)
> like AT_PACKAGE_NAME, AT_PACKAGE_VERS
On Tue, Mar 3, 2009 at 12:13 AM, Ralf Wildenhues wrote:
>
> > I don't see results from the "echo" in any of the resulting files. Thus I
> > have no way of knowing if the AS_IF should even work since I don't know
> the
> > value of MPI_LIBS.
>
> Ah, another specialty of Autotest. Shell code not en
Hello Alejandro,
* aaragon wrote on Tue, Mar 03, 2009 at 08:35:05AM CET:
>
> I don't understand much the m4 code. I can say
> that it stopped working after upgrading autotools. Part of the macro (the
> one that fails) is:
... unfortunately too little information to analyse it well. Please, I
as
* John Wohlbier wrote on Tue, Mar 03, 2009 at 05:13:17PM CET:
>
> I got the basic functionality to work with the following.
>
> m4_define([AT_MPIRUN_PROGRAM],
> [AT_BANNER([executing mpirun -n $2 $1])
> AT_SETUP([$1])
> AT_CHECK([test -n "$MPI_LIBS" || exit 77])
> AT_TESTED([$1])
> AT_CHECK([
On Tue, Mar 3, 2009 at 12:14 PM, Ralf Wildenhues wrote:
> * John Wohlbier wrote on Tue, Mar 03, 2009 at 05:13:17PM CET:
> >
> > I got the basic functionality to work with the following.
> >
> > m4_define([AT_MPIRUN_PROGRAM],
> > [AT_BANNER([executing mpirun -n $2 $1])
> > AT_SETUP([$1])
> > AT_C
* John Wohlbier wrote on Tue, Mar 03, 2009 at 09:09:09PM CET:
> That seems like a reasonable suggestion. What I have a hard time seeing
> though is how exactly I'd get that test to execute just once for serial, and
> a test writer specified number of times with different numbers of processors
> for
Ralf Wildenhues writes:
> That smells of M4 overquoting somewhere. Find out what changed, the
> Autoconf version, or any third-party macro code, or configure.ac. In
> case of doubt, please post a small example to reproduce the above
> together with a pointer to the exact DX_REQUIRE_PROG macro
>
Russ Allbery writes:
> Ralf Wildenhues writes:
>> That smells of M4 overquoting somewhere. Find out what changed, the
>> Autoconf version, or any third-party macro code, or configure.ac. In
>> case of doubt, please post a small example to reproduce the above
>> together with a pointer to the e
Hi Russ, thanks for the help. The file you're working with is quite old.
There is a much newer file in teh autoconf archive:
http://autoconf-archive.cryp.to/ax_prog_doxygen.html
I've been working with that version. I don't think the code has changed much
since 2004, so I'll try to manually apply
aaragon writes:
> Hi Russ, thanks for the help. The file you're working with is quite old.
> There is a much newer file in teh autoconf archive:
>
> http://autoconf-archive.cryp.to/ax_prog_doxygen.html
>
> I've been working with that version. I don't think the code has changed
> much since 2004,
I already sent an email to the creator of the macro, so let's see what he
replies. For the time being, if the fix you did works, I'll use it like
that. I wish there was a cleaner way to integrate doxygen with autotools,
I'm also afraid that it will break in the future again.
aa
Russ Allbery wro
Russ, what you did didn't fix it, just avoided the errors. However, there is
no doxygen file created after the configuration. Are you having the same
issue?
aa
Russ Allbery wrote:
>
> aaragon writes:
>
>> Hi Russ, thanks for the help. The file you're working with is quite old.
>> There is a
aaragon writes:
> Russ, what you did didn't fix it, just avoided the errors. However,
> there is no doxygen file created after the configuration. Are you having
> the same issue?
No, I'm not. It works fine for me; all the Doxygen documentation is
generated.
--
Russ Allbery (r...@stanford.edu)
Alright, I made it work now. However, there are some things that are not
quite right. I had to change the
DX_DOT_FEATURE(ON|OFF) because that keyword doesn't exist (instead I saw he
defines DX_FEATURE_dot(ON|OFF)). Even with this the pdf files don't have the
graph diagrams so I don't know what's
aaragon writes:
> Alright, I made it work now. However, there are some things that are not
> quite right. I had to change the DX_DOT_FEATURE(ON|OFF) because that
> keyword doesn't exist (instead I saw he defines
> DX_FEATURE_dot(ON|OFF)). Even with this the pdf files don't have the
> graph diagra
Well, I fixed the log file. For some reason it doesn't work when I put it in
the doc/ directory. If I leave it in the same directory the Doxyfile is,
then it works. Now it seems that the dot problem I have is related to the
system:
aara...@vpn3-14635:~$> dot
dyld: lazy symbol binding failed: Symb
17 matches
Mail list logo
