I've included a patch here, but mostly just to
clarify my questions, so I thought it more
appropriate to post here than to
autoconf-patches.
What is the 'official' gnu position on automake,
and what's the relationship between autoconf
and the rest of the autotool chain? I find it
extremely annoy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 10/13/2008 5:55 AM:
> The existing text is correct (albeit a
> bit confusing in the automake-user's case where Makefile.in is generated,
> so the upstream Makefile.am needs the modification instead), so I'm quite
> sure what
You will remember the shell function portability issue in zsh...
Do you think that these functions:
ac_func_c_try_compile() {
rm -f conftest.$ac_objext
if { (ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo=
Eric Blake wrote:
According to William Pursell on 10/13/2008 1:06 AM:
Thirdly, is there any standard way to take a file
foo.c and generate an autoconfiscated tree structure?
Not that I know of. What tree structure are you proposing?
I suspect that would be a contentious issue. Personally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Pursell on 10/13/2008 1:06 AM:
Hello William, and thanks for the report.
> What is the 'official' gnu position on automake,
> and what's the relationship between autoconf
> and the rest of the autotool chain?
We encourage automa
Hi
I often use
./config.status --recheck
when I want to detect new installed tools; however, when I move
something to some other directory, I need to re-run ./configure
manually, otherwise make complains about some missing files (required by
a Makefile.in); this requires to re-run configure
* Paolo Bonzini wrote on Mon, Oct 13, 2008 at 11:59:22AM CEST:
> You will remember the shell function portability issue in zsh...
Yes; sigh.
> Do you think that these functions:
reindented to:
ac_func_c_try_compile()
{
rm -f conftest.$ac_objext
if
{
(ac_try="$ac_compile"
ca
On Monday 13 October 2008 13:56:21 Eric Blake wrote:
> > The existing text is correct (albeit a
> > bit confusing in the automake-user's case where Makefile.in is
> > generated, so the upstream Makefile.am needs the modification
> > instead), so I'm quite sure what wording to use here, whether or
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Lorenzo Bettini on 10/13/2008 11:02 AM:
> ./config.status --recheck
>
> when I want to detect new installed tools; however, when I move
> something to some other directory, I need to re-run ./configure
> manually, otherwise make complains
