the m4_included file in either case.
What's going on here?
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
. For example, mumble_LDADD = libiconv.la $(LDADD).
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
not to update aclocal.m4
when 'make' runs it.
On another note: the following also fails in configure.ac:
m4_ignore([m4_include([a_file_that_does_not_exist.m4])])
% autoreconf
aclocal: error: configure.ac:4: file `a_file_that_does_not_exist.m4' does not
exist
--
Nick Bowler, Elliptic
or defines
macros that aclocal needs to find.
Nevertheless, if both aclocal and automake agreed on when to update
aclocal.m4, then the workaround _would_ solve my specific problem.
Thanks for your time on this matter,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2010-11-04 20:47 +0100, Stefano Lattarini wrote:
On Thursday 28 October 2010, Stefano Lattarini wrote:
On Wednesday 27 October 2010, Nick Bowler wrote:
On 2010-10-23 15:23 +0200, Stefano Lattarini wrote:
So I think your first problem is just an aclocal limitation we should
resign
for each set of CPPFLAGS, then link both
into your final program or library.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
not that interesting to see GEN foo.bar five times in a row.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2010-12-20 17:39 -0800, Philip Prindeville wrote:
The odd thing is that even though it complains, it still generates the
correct Makefile in the first case:
SYMFILES = $(srcdir)/uni.h $(shell $(CC) $(CFLAGS) -E
$(srcdir)/header.c | $(AWK) -f $(srcdir)/script.awk)
Does automake need to
on systems
where the runtime linker loads indirect library dependencies
automatically (includes GNU/Linux, GNU, Solaris).
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
changes to Makefile.am.
* Modify gnulib so that it can be easily integrated into a
non-recursive automake setup. One could look to libltdl for
inspiration here.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2011-03-21 14:13 -0500, Paul Elliott wrote:
On Monday, March 21, 2011 12:51:11 pm Nick Bowler wrote:
Since Fedora has complete control over how packages are configured
and installed, they can afford to make the necessary arrangements
rendering the .la files unnecessary.
[...]
Well
On 2011-03-22 07:36 -0700, Ben Pfaff wrote:
Nick Bowler nbow...@elliptictech.com writes:
* Modify gnulib so that it can be easily integrated into a
non-recursive automake setup. One could look to libltdl for
inspiration here.
It doesn't have to be modified. An Automake
to be fixed? If the
latter, is the above workaround a good one?
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
Hi Ralf,
On 2011-04-02 10:42 +0200, Ralf Wildenhues wrote:
* Nick Bowler wrote on Fri, Apr 01, 2011 at 04:04:21PM CEST:
I'm working on a project which uses libltdl to load modules, and I've
set it up in a manner pretty similar to what's described in the libtool
manual (10.3 Linking
= foo.c bar.c.
See the automake manual, 14.2 Fine-grained Distribution Control.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
with commands entirely on one line. For instance
foo: ; echo hello $@
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
, the compiled object is what depends on the header, not
the source file itself.
So this would perhaps be better written as
foo_obj = foo.$(OBJEXT) # might need to be foo.lo if using libtool.
$(foo_obj): bar.h
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
, and they will
be left with a bitter impression.
Now, I'm not fundamentally opposed to the idea, but it has to be done
_right_.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2011-11-22 17:46 +0100, Stefano Lattarini wrote:
On Tuesday 22 November 2011, Nick Bowler wrote:
This especially includes users who
have no idea that there's a difference between GNU make and the version
of make that is already on their system.
Honestly, there are such users today? I
in the context of this discussion,
since Automake can do that conversion itself, since it makes you give it
the list of source files.
Yes, this is a bad example, because the above line is portable make!
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2011-11-22 20:33 +0100, Stefano Lattarini wrote:
On Tuesday 22 November 2011, Nick Bowler wrote:
On 2011-11-22 17:46 +0100, Stefano Lattarini wrote:
See also:
http://lists.gnu.org/archive/html/automake/2011-01/msg00091.html
Yes, it is sad that many package maintainers fail
on Autoconf.
Autoconf-generated configure scripts do not require a C compiler unless
you use a macro that requires a C compiler (e.g. the AC_PROG_CC family
or one of the AC_whatever_IFELSE macros with AC_LANG set to C).
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
to generate these headers.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
in this case, though. :)
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2012-01-20 20:35 +0100, Stefano Lattarini wrote:
Just a minor FYI and a minor question ...
On 01/19/2012 09:27 PM, Nick Bowler wrote:
[SNIP]
What automake does for source files it knows about is just include
$(DEPDIR)/srcfile.Po (apparently include is considered portable
make
Hi Stefano,
On 2012-01-20 20:36 +0100, Stefano Lattarini wrote:
On 01/19/2012 09:27 PM, Nick Bowler wrote:
[SNIP]
Interestingly, if you actually stick a line exactly like the above into
your Makefile.am, Automake will actually do The Right Thing™ and
creates the .Po stub as if you
On 2012-03-20 16:01 +0200, Andrew W. Nosenko wrote:
On Tue, Mar 20, 2012 at 15:47, Nick Bowler nbow...@elliptictech.com wrote:
[...]
SUFFIXES = .sh
.sh:
$(shbin_verbose) cp $ $@.tmp
$(AM_V_at) chmod +x $@.tmp
$(AM_V_at) mv -f $@.tmp $@
Why do not use
to achieve what you want.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
of Makefile.in?
Nevertheless, if you still need it at the beginning, the most obvious
way to do it is to directly add it to Makefile.in file after running
automake by postprocessing Automake's output.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
caused by Libtool, and therefore the correct place to add the call to
AM_PROG_AR is in libtool itself, rather than ad-hoc patching of each
package individually. You can silence the warnings (but not fix them)
by adding -Wno-extra-portability to AM_INIT_AUTOMAKE.
Cheers,
--
Nick Bowler, Elliptic
which versions of autoconf and automake you are using.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
(untested):
git_version.py: git_version.py.in git_version.sed
$(AM_V_GEN)sed -f git_version.sed $(srcdir)/git_version.py.in $@.tmp
$(AM_V_at)mv -f $@.tmp $@
which avoids updating the target file unless the first command succeeded.
Hope that helps,
--
Nick Bowler, Elliptic
On 2012-05-22 13:05 -0500, Adam Mercer wrote:
On Tue, May 22, 2012 at 12:06 PM, Nick Bowler nbow...@elliptictech.com
wrote:
Probably all you need to do is add these generated files to CLEANFILES,
e.g.,
CLEANFILES = git_version.py git_version.sed
so that make clean deletes them
anymore, so
delete the Automake bits related to it.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
a .foo file, then something
like
CLEANFILES = $(FOOFILES:.foo=.c) $(FOOFILES:.foo=.h)
is probably sufficient. For more involved cases, you might add a
--clean option to your tool which deletes any files that it generates,
and then call it from clean-local.
Hope that helps,
--
Nick Bowler
, then you can simply
run
automake --print-libdir
and it will print that location. You can use this to have a bootstrap
script which copies the files you need.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
to me.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
...
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
imply that b.o is somehow required to update a.o:
very unusual in a C program). Moreover, Automake already provides
prerequisites from object files to their C source files, so listing
the .c files here is redundant.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
to
help here. However, as I have never used it myself, I cannot vouch for
its efficacy.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
) and more conventional (for your
users) to just require that the necessary packages are already installed
if the user requests these optional features.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
or limitation in autoreconf, could you
provide a small example package which demonstrates the problem? I am
not aware of any problems like this related to AM_CONDITIONAL inside m4
macros.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
package with -Wno-portability.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
rules have an
ordering to them; the above approach does not (and, in fact, allows
the different rules to be run in parallel). So it may also be necessary
to add prerequisites between the individual rules-with-commands as well.
Cheers,
--
Nick Bowler, Elliptic Technologies (http
to look like the install tree, and your program can
find its data files automatically when run normally.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
#Program-and-Library-Variables
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
%20Lander%20Remastered/Extractor/Makefile.am
Broken link?
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 2013-06-06 17:58 -0700, Kip Warner wrote:
On Thu, 2013-06-06 at 10:37 -0400, Nick Bowler wrote:
Moreover, the link provided below is broken, so we cannot see the whole
Makefile.am.
Hey Nick. Sorry about that. Try this:
https://bazaar.launchpad.net/~avaneya/avaneya/trunk/view/head
will ordinarily need to do.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
try something like the AX_CC_FOR_BUILD[1] macro in the
autoconf archive to actually find a compiler for the build system.
[1]
http://git.savannah.gnu.org/cgit/autoconf-archive.git/tree/m4/ax_cc_for_build.m4?id=v2013.11.01
Cheers,
--
Nick Bowler, Elliptic Technologies (http
not need to set SUFFIXES for simple rules like this
.mpic.o:
...
which should work in GNU and non-GNU makes alike. Integrating with
libtool is left as an exercise to the reader.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
Scheme[1].
Something like this (untested):
foosubdir = $(pkgincludedir)/subdir
pkginclude_HEADERS = path/to/header1.h
foosub_HEADERS = path/to/header2.h
[1] https://gnu.org/software/automake/manual/automake.html#Uniform
Cheers,
--
Nick Bowler, Elliptic Technologies (http
so I don't see why
it could not be done at Automake-time.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
the m4_include macro name:
m4_define([readver], [getver([m4_include]($1), [\])])
You can trick aclocal really easily because it doesn't try to
understand m4 syntax at all. If this approach works for your
package, go for it.
Cheers,
--
Nick Bowler, Elliptic Technologies (http
distclean and
maintainer-clean, but not removed by mostlyclean or clean.
As you have observed, this does not appear to be explicitly
documented in the manual.
So typically, a generated file would be added to exactly one of the
*CLEANFILES variables.
Cheers,
--
Nick Bowler, Elliptic Technologies (http
, such as /var/tmp?
Setting TMPDIR environment variable might help.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
: the above
won't work if program_transform_name (which is set by the user) contains
nontrivial sed commands. For example, it will fail if it contains a
semicolon.
Something like this should be more robust (but untested):
transform = /myprog/q;$(program_transform_name)
Cheers,
--
Nick Bowler
On 2014-09-10 23:37 +0100, Pádraig Brady wrote:
On 09/10/2014 03:31 PM, Pádraig Brady wrote:
On 09/10/2014 03:08 PM, Nick Bowler wrote:
On 2014-09-10 10:22 +0100, Pádraig Brady wrote:
I was able to work around the issue here as there is only a single
item in libexec in my project which I
in
the future just because POSIX standardized ::= syntax.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
are
missing.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
.
The object filenames are reliable as long as you don't change any
settings (like subdir-objects, but also other things). So it is
safer to use mumble_OBJECTS in my opinion.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
, for example, added per-target CFLAGS or enabled
subdir-objects.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
a distcheck-hook to ensure that this actually happens.
For the second point, if you are not routinely testing VPATH builds
from your git tree at all, just be aware that distcheck may uncover bugs
related to this feature.
Hope that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
is
not distributed, so this dependency can never be satisfied in the
tarball.
Is there a solution for this in automake?
Yes, use a dist-hook.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
Makefile.am use
only
the plain $(var) form without the tricks?
The first form of expansion on that page, $(var:.a=.b), should be OK.
They are standard in POSIX and work on all make implementations that I
know of.
The version with % characters is not portable.
Hope that helps,
--
Nick Bowler
,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
of the binary, and everything will work correctly in
most cases.
You can also set foo_DEPENDENCIES and/or EXTRA_foo_DEPENDENCIES
manually in more complicated cases.
[1] §18.2 Handling new file extensions
https://gnu.org/software/automake/manual/automake.html#Suffixes
Cheers,
--
Nick Bowler
On 2014-11-12 21:58 +0200, fr33domlover wrote:
On 2014-11-12
Nick Bowler nbow...@elliptictech.com wrote:
What is probably happening is that in VPATH builds from your tarball,
your documentation is being rebuilt even though it was distributed.
This is leaving files behind in your build
and CXXFLAGS.
It is also basically guaranteed to fail on any compiler that is not
compatible with GCC.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
that helps,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
(not tested), because variables
defined on the make command line *are* exported into the environment.
You will still need the AC_SUBST to define COPYFILE_DISABLE in the
first place.
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
the
environment, while dmake, NetBSD make, and FreeBSD make do not.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
builds, outside of make distcheck, first do a
make distclean to delete all the build products, then cd into an empty
directory and run configure from there, e.g.,:
% make distclean
% mkdir build
% cd build
% ../configure
% make dist
Cheers,
--
Nick Bowler, Elliptic Technologies (http
/tap-driver.sh
AM_TAP_AWK is defined right there, in the example code. Its purpose is
to tell the tap-driver.sh program which AWK program to use.
[1]
https://gnu.org/software/automake/manual/automake.html#Use-TAP-with-the-Automake-test-harness
Cheers,
--
Nick Bowler, Elliptic Technologies
'
echo echo I am a test script test3.log test3.abc
+ echo 'echo I am a test script test3.log'
Do you see the problem now?
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
are mandatory).
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
' options are mandatory.
[1] https://gnu.org/software/gawk/manual/gawk.html#Getline
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
Automake includes
are expanded only once, when Automake is run.
The generated Makefile.in file (which gets processed by configure) does
not contain the include commands at all.
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
On 11/12/15, Will Estes wrote:
> On Thursday, 12 November 2015, 9:41 pm +, Gavin Smith
> wrote:
>> On 12 November 2015 at 19:19, Will Estes wrote:
>> > and Makefile.am:
>> >
>> > check_PROGRAMS = test
>> >
>> >
Hello,
On 2015-11-12, Will Estes wrote:
> The flex program includes a test suite to enable testing of the version of
> flex built in the flex tree. From a distributed tar ball (made with "make
> dist"), it is possible to build flex without needing to have flex already
>
On 10/31/15, Kim Walisch wrote:
> Hi,
>
> I have two open source projects (primesieve and primecount) which use
> the GNU build system. Both currently print a warning during make
> (tested on Ubuntu 15.10 and Fedora 22):
>
> ar: `u' modifier ignored since `D' is the default
On 11/3/15, Michael Felt wrote:
> I suppose in a GNU only world, this would be okay. However, my man page for
> ar still says:
>
>-u
> Copies only files that have been changed since they were last
> copied (see the -r flag discussed previously).
>
> while
Hi Andy,
(Note that your mailer seems to have completely mangled all whitespace,
particularly the newlines, in your make snippet. This makes it very
hard to read. I have tried to manually correct it in the quoted text).
On 2016-03-28, Andy Falanga (afalanga) wrote:
> My
On 2016-05-24, Wouter Verhelst wrote:
> I'm adding a systemd unit to my package. To that end, I'm checking if
> there is a pkg-config .pc file for systemd which sets a variable
> "systemdsystemunitdir", and am trying to install the systemd unit in
> that location.
[snip configure
Hello,
On 3/3/17, Paul Jakma wrote:
> Well, it's due to the distributed 'doc/quagga.info' being slightly older
> than the (built by automake) doc/defines.texi.
>
> Both are made by the 'make dist' and put in the dist tarball. Then
> distcheck unpacks that to a subdir, makes it
Hello,
On 7/12/17, Kip Warner wrote:
> My challenge is replicating their functionality for flexc++(1) and
> bisonc++(1) in the absense of macros to make their usage easier in
> Automake
[...]
> In trying to integrate the two tools into my build environment, I've
> attempted
On 2017-06-21, Anton Shepelev wrote:
> Contextual diff-files a very good means of collaborative development
> whenever they are used with source code, but I have a problem with
> .am files. If two patches should add new source files to the same
> directory, they will also
Hi Simon,
On 10/16/17, Simon Sobisch wrote:
[...]
> Running without `make -j` always work but using parallel builds sometime
> break with the mentioned error.
[...]
> ~~~
> gcc -O2 -pipe -finline-functions -fsigned-char -Wall -Wwrite-strings
> -Wmissing-prototypes
On 2017-09-05, Kip Warner wrote:
[...]
> Hey Thomas. Good question. It could well be that no hackery at all is
> required with this. Here is my Makefile.am:
>
> https://github.com/cartesiantheatre/narayan-designer/blob/master/Source/Makefile.am
>
> See
On 9/29/17, Sascha Manns wrote:
> Am Freitag, den 29.09.2017, 16:26 +0200 schrieb Sascha Manns:
>> i have a project what provides a file called "bzr.mk". This isnt
>> generated and should just installed in $(datadir)/bzrmk.
>> [...]
>> bzrmk_DATA = bzr.mk
>>
>> But while
Hi,
On 2017-08-21, Mike Fleetwood wrote:
> I'm working on adding installation of a polkit action file into
> GParted's build and install system, however the polkit daemon only
> recongises action files installed into the single location of
>
Hello,
On 8/24/17, Kip Warner wrote:
> I'd like to transform the following variable in my Makefile.am from...
>
> files_only = a.foo b.foo c.foo d.foo ...
>
> Into...
>
> files_with_path = dir/a.foo dir/b.foo dir/c.foo dir/d.foo ...
I'm not aware of any truly
Hi Jim,
On 2017-11-28 11:21 -0800, Jim Meyering wrote:
> Date: Thu, 20 Mar 2014 12:31:32 -0700
> Subject: [PATCH] "make dist" did not depend on $(BUILT_SOURCES)
>
> * lib/am/distdir.am (distdir-am): New intermediate target.
> Interpose this target between $(distdir) and its dependency
> on
On 2017-11-28 18:13 -0800, Jim Meyering wrote:
> On Tue, Nov 28, 2017 at 12:45 PM, Nick Bowler <nbow...@draconx.ca> wrote:
> > The Automake manual unequivocally states that BUILT_SOURCES files are
> > generated only when running 'make all', 'make check' or 'make
Hi,
On 2017-11-20, Thomas Martitz wrote:
> here's some quite annoying warning. I'm trying to define a variable
> TEST_LDFLAGS that multiple programs use. There is no program named TEST.
> The same works fine with TEST_CFLAGS (i.e. no warning is displayed).
>
> Here's the
Hi Ralph,
On 2017-11-20, Ralph Corderoy wrote:
>> 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
On 11/3/17, Jeffrey Walton wrote:
> On Thu, Nov 2, 2017 at 6:04 PM, Jeffrey Walton wrote:
>> I'm working on adding Autotools to a C++ library and test program. My
>> Automake.am has:
>>
>>
>> ...
>
> I believe I applied Nick and Mathieu correctly. The
Hello,
> EXTRA_libcryptopp_la_DEPENDENCIES listing the objects worked for Linux
> and OS X, but not Solaris. For Solaris I needed to drop the leading
> `EXTRA`, and use just `libcryptopp_la_DEPENDENCIES`.
Is that just because you happen to be running an antique version of
Automake on the Solaris
Hi Jeffrey,
On 11/2/17, Jeffrey Walton wrote:
> I'm working on adding Autotools to a C++ library and test program. My
> Automake.am has:
>
> lib_LTLIBRARIES = \
>libcryptopp.la
>
> libcryptopp_la_SOURCES = \
>cryptolib.cpp \
>cpu.cpp \
>integer.cpp \
>
>
1 - 100 of 240 matches
Mail list logo