Hi Skip,
Third, after executing configure, cvs up reports several
unknown files:
? config.log
? Makefile
? config.status
? config.h
? libtool
? stamp-h1
? python/Makefile
? src/Makefile
? src/.deps
? test/Makefile
? test/.deps
None
Hi,
I'm fond of `make -s'. It doesn't work too well with the
automake-generated Makefile on
http://git.savannah.gnu.org/cgit/nmh.git/tree/Makefile.am that I
contribute to. In hand-written Makefiles in the past, I've checked
MAKEFLAGS against *s* to decide whether to echo, etc. IIRC.
I find
Hi,
In a subdirectory, a foo.y gets turned into a foo.c. Both thus
`#include "bar.h"' that sits alongside them. This all works fine. But
use a build directory, i.e. run configure from somewhere other than `.',
and foo.c fails to build because bar.h isn't found. (A similar problem
happens with
Hi again,
> It seems wrong for foo.y to have to `#include
> "path/from/root/to/bar.h" since that means it has to alter if they
> move around the hierarchy. Is there another way?
I can be more precise having dug into this project a bit.
Currently, it has
sbr_libmh_a_CPPFLAGS =
More noise...
> It works in this one case, but I know that doesn't necessarily mean
> it's right. :-)
I've found AM_CPPFLAGS in `info automake | less' and I think that's
answering it.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Mike,
> I like to run under strace to see why the test is failing. I can't
> seem to find where stderr is being redirected. I thought it was in
> tap-driver.sh so I patched it but still no strace output.
Have you tried strace(1)'s -o option so its output doesn't appear on
stderr and you
> On Oct 26, 2017 5:59 AM, "Ralph Corderoy" <ra...@inputplus.co.uk> wrote:
>
> Hi Mike,
>
> > I like to run under strace to see why the test is failing. I can't
> > seem to find where stderr is being redirected. I thought it was in
> > tap-driver
> Has anyone looked at this patch so far? Reviews are appreciated. As
> a downstream maintainer I keep getting questions when this is going to
> be fixed.
Also a problem with automake 1.15-2 on Arch Linux.
Annoying if one's attempting to get "silent" builds that produce no
output if all's well.
