Hello,
Daniel Pocock writes:
> According to the "Warning" in this page[1], it is not permitted to use
> variables in _SOURCES. Is this deliberate or is it a bug?
>
> In our project, we started getting the warnings about subdir-objects and
> so we added[2]
>
> AM_INIT_AUTOMAKE([foreign subdir-
Daniel,
this is still a known bug in released versions of autotools, see
http://debbugs.gnu.org/13928
Best,
Bert
On Sun, Jun 12, 2016 at 9:22 AM, Daniel Pocock wrote:
>
>
> According to the "Warning" in this page[1], it is not permitted to use
> variables in _SOURCES. Is this deliberate or is
Hello,
In the Autoconf manual we read:
When you use the same text in a macro argument, you must therefore
have an extra quotation level (since one is stripped away by the macro
substitution). In general, then, it is a good idea to use double
quoting for all literal string arguments, either
> configure:
>
> ./configure ... \
>--with-python \
>PYCXX_SRCDIR=/usr/share/python2.7/CXX/Python2
>
>
> Makefile.am:
>
> nodist_libpyroute_la_SOURCES = $(PYCXX_SRCDIR)/cxxextensions.c
> nodist_libpyroute_la_SOURCES += $(PYCXX_SRCDIR)/cxx_extensions.cxx
> nodist_libpyroute_la_SOURCES += $(P
According to the "Warning" in this page[1], it is not permitted to use
variables in _SOURCES. Is this deliberate or is it a bug?
In our project, we started getting the warnings about subdir-objects and
so we added[2]
AM_INIT_AUTOMAKE([foreign subdir-objects])
However, since that time the bu
