Re: GNU Coding Standards, automake, and the recent xz-utils backdoor

On 1/4/24 06:00, Eric Gallager wrote: So, `aclocal` has a flag to control this behavior: specifically, its `--install` flag. Right now I don't see `aclocal` mentioned in the GNU Coding Standards at all. Should they be updated to include a recommendation as to whether it's better to put

bug#68860: race condition with make recheck

Hi automakers, I think I've found a race condition with 'make recheck' that results in a source file being compiled twice in parallel and resulting in a failure such as mv: cannot stat '.deps/foo.Tpo': No such file or directory In my trimmed down example my Makefile.am looks like:

bug#68808: subsecond mtime discovery code insufficient

On 30/1/24 22:46, Erik A Johnson wrote: (Why, then, does Apple continue to include 3.81 in the software 18 years later? Beyond me.) Probably because 3.81 was the last version released under GPLv2 or later and IIRC Apple avoids shipping things that are licensed with GPLv3. Cheers, Peter

bug#67894: automake-1.16i pretest available: please test

Hi Karl, On 27/12/23 08:38, Karl Berry wrote: I get one failure (t/nodef) Hi Peter - I hope this random timing bug is fixed now. It seems to work. 'make check -j16' goes through and since it seemed to be of a random nature previously I ran the individual test repeatedly and it passed

bug#67894: automake-1.16i pretest available: please test

Hi Karl, On 20/12/23 10:09, Karl Berry wrote: Could you try running the test on its own? make VERBOSE=1 check TESTS=t/nodef.sh keep_testdirs=yes I ran it ten times and it succeeded 70% of the runs, so seems quite random in line with being due to the timing issue. Peter

Re: if vs. ifdef in Makefile.am

On 2/3/23 16:07, ljh via Discussion list for automake wrote: Hi, It seems I can not use `--disable-assert` on Debian 11. You need to call macro AC_HEADER_ASSERT in your 'configure.ac' https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/autoconf.html#Particular-Headers

bug#33573: Patch to replace symlinks with files

Hi both, On 1/1/23 05:20, Bogdan wrote: Karl Berry , Sat Dec 31 2022 03:30:42 GMT+0100 (Central European Standard Time) Hi Bogdan, Someone reported a bug for this, so I simply gave it a try. Thank you! I didn't realize you were working on some of the old bugs. That is great! :) To

bug#17614: parallel compilation fails

Hi Mike, On 25/1/22 16:24, Mike Frysinger wrote: On 19 Jan 2022 18:32, Peter Johansson wrote: On 19/1/22 18:10, Mike Frysinger wrote: assuming it still fails with Automake 1.16 ... I'll test when I'm out of this semi-lockdown and have access to a computer with more CPUs. can you link

Re: adding a command line option for ACLOCAL_PATH-type search paths

Hi Karl, On 20/1/22 09:05, Karl Berry wrote: But if both are set, should the --aclocal-path argument replace $ACLOCAL_PATH, or augment it (earlier of course)? I'm not sure. FWIW, in autoconf the commandline -W takes precedence over environment variable WARNINGS

bug#17614: parallel compilation fails

Hi Mike, On 19/1/22 18:10, Mike Frysinger wrote: retitle 17614 parallel compilation fails: mv: yat/statistics/.deps/Percentiler.Tpo and yat/statistics/.deps/Percentiler.Tpo are the same file tag 17614 = moreinfo thankyou On Wed, 28 May 2014 14:52:21 +1000, Peter Johansson wrote: I have

bug#10828: [RFC] POSIX will say running "rm -f" with no argument is OK

Hi Mike, On 11/12/21 15:14, Mike Frysinger wrote: On 11 Dec 2021 09:33, Peter Johansson wrote: On 10/12/21 15:47, Mike Frysinger wrote: if it's dropped, i'm not sure how users are supposed to fix things. the error message says to install GNU coreutils, but if GNU coreutils uses automake

bug#10828: [RFC] POSIX will say running "rm -f" with no argument is OK

Hi Mike, On 10/12/21 15:47, Mike Frysinger wrote: if it's dropped, i'm not sure how users are supposed to fix things. the error message says to install GNU coreutils, but if GNU coreutils uses automake and presents the same error ... FWIW, automake is not needed to build and install GNU

Re: Automake for RISC-V

On 21/11/21 16:32, Billa Surendra wrote: Then how-to install automake in target image. Download the tarball from https://ftp.gnu.org/gnu/automake/ unpack and follow the instructions in INSTALL; typically somethings like ./configure make sudo make install Peter

Re: installing documentation one level higher

On 11/8/21 9:55 pm, Werner LEMBERG wrote: Folks, My current rule (in the top-level `Makefile.am`) is nobase_dist_doc_DATA = doc/bar.html \ doc/img/baz.png I think you wanna get rid of the 'nobase_' prefix (but haven't tested). If I do that, all files are

Re: installing documentation one level higher

On 11/8/21 9:55 pm, Werner LEMBERG wrote: Folks, My current rule (in the top-level `Makefile.am`) is nobase_dist_doc_DATA = doc/bar.html \ doc/img/baz.png I think you wanna get rid of the 'nobase_' prefix (but haven't tested). If I do that, all files are

Re: installing documentation one level higher

Hi Werner, On 8/8/21 5:49 am, Werner LEMBERG wrote: Folks, My current rule (in the top-level `Makefile.am`) is nobase_dist_doc_DATA = doc/bar.html \ doc/img/baz.png I think you wanna get rid of the 'nobase_' prefix (but haven't tested). Cheers, Peter

bug#49309: Feature Request: Automake script based tests to print the test name before running it

Hi Kasper, I leave to the maintainers to comment on the suggestion, but in the meantime... On 1/7/21 1:01 pm, Kasper k wrote: Hello automake devs, In script based testsuites

Re: How to prevent distribution of `texinfo.tex`

On 24/6/21 3:02 am, Werner LEMBERG wrote: As far as I know there is no way to disable this behaviour, although I agree the automagic file inclusion can be a bit funky. Yeah, it would be nice to have a means to control that. There is the dist hook, which can be used to remove files from the

Re: Constantly changing libtool

Hi Laurence, On 15/4/21 6:35 am, Bob Friesenhahn wrote: Most problems seem to stem from packages providing the generated files from Autoconf, Automake, and libtool so that end users don't need to have the tools available. It will be easier for people here to help if you provide a bit more

bug#47381: Atomic (fast) install

On 25/3/21 8:24 pm, Дилян Палаузов wrote: • Please adjust Automake on “make install” to do (per default or with an option) atomic install of files, even when libtool is involved: the file is moved to a temporary destination first, and then rename(2)d, or the source is moved to the destination,

Re: Is it possible to set the permission bits used by the default install target in a Makefile.am?

On 3/14/2019 3:24 AM, Nick Bowler wrote: Hello Craig, On 2019-03-13, Craig Sanders wrote: Is it possible to set the permission bits used by the default install target in a Makefile.am? To help try and illustrate what I mean, I present a code snippet from one of my Makefie.am files. Begin

Re: Parallel builds with some ordering constraints

Hi Kip and Nick, On 12/30/2018 12:03 PM, Kip Warner wrote: Almost! The problem is with the last rule you defined because a rule to generate test-stop.log would have already been generated by Automake and this would override it. I tested in my own source tree and confirmed that:

Re: automatically showing test-suite.log on failure?

Hi Karl, On 9/13/2018 7:53 AM, Karl Berry wrote: After make check runs, if there were any failures, I'm wishing for a way to have automake to automatically show the relevant test-suite.log. I might be missing something, but I get that behavior in my automatic builds by calling 'make check

bug#31157: Advice for help2man does not work for parallel builds

Hi Ruben and Mathieu, On 4/22/2018 1:13 AM, Mathieu Lirzin wrote: Hello Reuben, Reuben Thomas writes: In the manual, we are given the following pattern for using help2man without breaking make distcheck: foo.1: foo.c $(top_srcdir)/configure.ac $(MAKE) $(AM_MAKEFLAGS)

Re: Portable $addprefix

On 9/2/2017 1:27 PM, Quinn Grier wrote: You can fix this by generating the complete macro definitions before Automake runs and including them in Makefile.am. Another way to do this is to use macro `AX_AM_MACROS_STATIC' in Autoconf Macro Archive

Re: installing info files

Hi Patrick, On 6/3/2017 5:26 PM, Patrick Alken wrote: Hi Peter, Yes make distcheck is in fact failing (even with your modification). The error is: /bin/install -c -m 644 file.info /data/palken/package/package-1.0+/_inst/share/info /bin/install: cannot stat ‘file.info’: No such file or

Re: installing info files

Hi Patrick, On 5/21/2017 5:16 PM, Patrick Alken wrote: Hello, I have a .info file (not generated by texinfo) and would like it to be installed under 'make install'. I tried adding it like this: info_DATA = file.info but this gives the following error: doc/Makefile.am:7: error: 'infodir'

Re: Problem with VPATH builds and SCRIPTS primary

On 11/02/2016 08:06 PM, Raphaël Halimi wrote: Hi Peter, Thanks for your answer. Just to make sure I understand: CLEANFILES += data/.dirstamp data/.dirstamp: @$(MKDIR_P) data @: > $@ This creates a directory "data", and then a file ".dirstamp" in this directory by redirecting

Re: Problem with VPATH builds and SCRIPTS primary

Hi Raphael, I have the following in my Makefile.am CLEANFILES += data/.dirstamp data/.dirstamp: @$(MKDIR_P) data @: > $@ data/foo.txt: data/.dirstamp Cheers, Peter On 10/28/2016 05:46 AM, Raphaël Halimi wrote: Hi, I have a problem with parallel build trees (a.k.a. VPATH

bug#23521: XFAIL

On 05/19/2016 09:04 AM, Mathieu Lirzin wrote: Another common use for "expected failure" is to write tests to check >that error conditions arise as expected, for example, by checking that >a program raises an error when given invalid input. I agree that XFAIL can be ambiguous, however I think

Re: make distclean

Hi Jürgen, On 03/18/2016 01:28 AM, Juergen Sauermann wrote: Hi, I have received a bug-report saying that 'make distclean' fails for GNU APL. The error message is this: make[2]: Entering directory `/home/eedjsa/projects/juergen/apl-1.5/src' Makefile:837: .deps/apl-Archive.Po: No such file

Re: [libtool] make install fails after an incremental build after a prefix change?

Hi Kees-Jan, On 12/30/2015 05:52 AM, Kees-Jan Dijkzeul wrote: On Tue, Dec 29, 2015 at 8:46 PM, Bob Friesenhahn wrote: >Try adding 'make clean' to your build steps. > >The best thing to do is to build outside of the source tree and use a >separate build directory

bug#21956: subdir-objecs dies with "rm: cannot remove 'emxp_cm_bl': Is a directory", even git version

On 11/19/2015 06:19 PM, Joakim Tjernlund wrote: hmm, I see the problem. How do I change Makefile.am, with minimal effort as we have alot of them? Tried bin_PROGRAMS += emxp_hw_bl/emxp_hw_bl but that gives me: ne/emxp_ss/emxp_hw_bl/Makefile.inc:14: warning: variable 'emxp_hw_bl_SOURCES' is

bug#21956: subdir-objecs dies with "rm: cannot remove 'emxp_cm_bl': Is a directory", even git version

Hi Joakim, On 11/19/2015 11:15 AM, Joakim Tjernlund wrote: automake>= 1.13 (did not test lower than that) dies during make with: CCLD emxp_cm_bl_shell rm: cannot remove 'emxp_cm_bl': Is a directory Makefile:1070: recipe for target 'emxp_cm_bl' failed This happens if you have the same

Re: What is minimum set of Automake work files needed for distribution on github?

On 09/28/2015 08:20 PM, Robert Parker wrote: I need to meet the requirements of 2 sets of users, the ordinary user who is only interested `./configure; make; make install` and the power users who want to start with `autoreconf`. So far google search on the topic has only increased my

Re: GNU Standards

On 09/01/2015 08:14 AM, Andy Falanga (afalanga) wrote: Where can I get these standards? https://www.gnu.org/prep/standards/ Cheers, Peter

Re: _build/sub and distcheck

On 06/24/2015 10:20 PM, Harlan Stenn wrote: So I notice that in automake-1.15 the distcheck stuff is now begin built in _build/sub/. I am generating some files for our test framework that want to access stuff in srcdir. I have these .in files using @srcdir@, but with the change from _build

Re: How do you set VERBOSE for parallel testin

On 05/15/2015 12:24 AM, Arthur Schwarz wrote: And as a simple question, why are you using make -j8? Shouldn't this be part of the automake generated test code? The short answer is because I wanna use 8 cpus. There is no sensible way Automake can know how many cpus I wanna use. $ make check

Re: How do you set VERBOSE for parallel testin

On 05/15/2015 10:36 AM, Arthur Schwarz wrote: And, if I guess correctly, the user can write make check TESTSUITEFLAGS=-jN I've never seen TESTSUITEFLAG before, so I don't know. As a nit-noy, don't you mean processor and not cpu? And

Re: How do you set VERBOSE for parallel testin

On 05/14/2015 01:20 AM, Arthur Schwarz wrote: My question is is this the only way to use VERBOSE? The Automake Manual seems to say that VERBOSE is a variable, not a make argument. And, as a variable, if the user (you) can change it's value then the appropriate way to do it is either: env

Re: How do you set VERBOSE for parallel testin

' and to 'yes' and yes and just plain yes. The test-suite.log file does not output. Am I missing something? How is VERBOSE supposed to be turned on? Usually I run my tests with something like this: make check -j8 VERBOSE=1 hth, Peter -- Peter Johansson

Re: How do you echo a shell variable reference

are referred to with double dollar sign in a Makefile: echo exit $$status hth, -- Peter Johansson

Re: distcheck: permission denied for file created from .PHONY target

) so it's set as .PHONY target. I'd let it depend on 'configure' and then it's re-generated (at least) every time you bump your VERSION, which should happen every time you release. Cheers, Peter -- Peter Johansson

Re: make dist fails for EXTRA_DIST elements

Hi Andy, On 03/10/2015 08:23 AM, Andy Falanga (afalanga) wrote: I try taking out the *.cpp file and try again with the same error but with the *.h. If I take out the *.h file, all is well again and make dist is happy and fine. Why is it picky with files ending with *.cpp and *.h if these

Re: Part 2: Add Cleanfiles for User Defined Special Sources [Re: How to add new Makefile-Rules through Configure?]

-archive/ax_add_am_macro_static.html#ax_add_am_macro_static Cheers, -- Peter Johansson

Re: converting to subdir-objects

/1581 Cheers, Peter -- Peter Johansson

bug#19961: check-local is kind of like check-hook

*** @echo I want this to be called before the check @echo *** @echo *** Cheers, Peter -- Peter Johansson

Re: dist prerequisites

On 06/09/14 02:20, Jack Bates wrote: How do I make another target a prerequisite of the dist target? I want my man target to be a prerequisite of the dist target, so when I run $ make dist it calls my man target. EXTRA_DIST is not working directly, I suppose, but I would still try that path.

Re: Automake extension mechanism?

On 22/08/14 10:55, David Ventimiglia wrote: Hi, Does Automake provide any kind of extension mechanism so that one can produce, and possibly share, useful Makefile fragments? Hi David, What I've chosen to do is to write autoconf macros that generate these Automake fragments, so all I need

bug#18286: distcheck fails to detect missing files

in $(distdir) but instead create 'tmp_/$(distdir)', builddir 'tmp_/$(distdir)/$(builddir)', and installdir 'tmp_/$(distdir)/inst_' which would hide the development files from the distcheck. What do you think? Thanks, Peter -- Peter Johansson

Re: make install-dirPRIMARY

/automake.html#Extending Cheers, -- Peter Johansson

bug#17614: parallel compilation fails

like some kind of race problem, but I cannot see anything wrong in the Makefile. Is this a known problem? If not let me know what would be useful. The Makefile is generated with Automake 1.14 Thanks, Peter -- Peter Johansson

bug#17614: parallel compilation fails

On 05/28/2014 02:52 PM, Peter Johansson wrote: Hi, I have a project with a libtool archive built from many source files. When I build with 'make -j40' I get error message mv: `yat/statistics/.deps/Percentiler.Tpo' and `yat/statistics/.deps/Percentiler.Plo' are the same file make[1

Re: Influencing DEFAULT_INCLUDES

On 18/05/14 10:54, Bob Friesenhahn wrote: Is there a safe way to change DEFAULT_INCLUDES to only include what is needed? Hi Bob, Have you looked at automake option 'nostdinc'? Hope that solves it. Peter

Re: Recompiling a source multiple times

large. Thanks, — Pavan -- Peter Johansson

Re: Cannot locate /usr/share/aclocal/pkg.m4

, or is it to be downloaded from somewhere? Many many thanks in advance, - Gao Sounds like you need to set the search path; have a look at `dirlist' in the manual. If you provide more details on what error you experience, it's easier for people to help. Cheers, -- Peter Johansson

Re: generated version numbers

expensive, you could set environment variable AUTOHEADER with something like: AUTOHEADER=autoheader -f autoreconf -vi Changing the behaviour of autoheader, I suspect will be met by some significant resistance. Cheers, -- Peter Johansson

Re: generated version numbers

a late test that if aclocal.m4 is newer than config.h.in, we touch config.h.in . This way, if nothing is updated then nothing gets touched. But if aclocal.m4 gets updated we'll avoid this particular problem. -- Peter Johansson

bug#16623: PACKAGE vs PACKAGE_TARNAME

[adding bug-automake] Hi infirit, On 02/02/14 12:25, infirit wrote: Hi, So for a project we wanted to make the tarball different from from the package name. So we updated AC_INIT and added the tarname and indeed now the tarball generated changes. However, we noticed that now the $PACKAGE

bug#16057: Non-parallel test suite API changes in 1.13

On 12/06/2013 08:49 AM, Eric Blake wrote: Why not? 1.13 is almost one year old now... Believe it or not, some people still like to make their project work with out-of-the-box tools. +1 -- Peter Johansson

Re: generated files issues

On 09/25/2013 08:00 AM, Werner LEMBERG wrote: What's the recommended solution to such a problem, except adding dependencies for all .c files which directly or indirectly include `foo.h' (which is both inconvenient and error prone)? Hi Werner, I use line below in one of my project for similar

Re: [OMPI devel] GNU Automake 1.14 released

On 09/04/2013 09:10 AM, Miles Bader wrote: Jeff Squyres (jsquyres)jsquy...@cisco.com writes: We've been using sym links in the OMPI project for years in order to compile a series of .c files in 2 different ways. It's portable to all the places that we need/want it. Hmm, how about just cp

bug#14775: automake 1.13.3 warning about version mismatch

Hi, This is probably already fixed with the version scheme and everything, but wanted to report it just in case. I updated from from automake 1.13 to 1.13.3 and after having modified an Makefile.am, Automake complained about version mismatch. I suspect aclocal.m4 was created with aclocal

tests using multiple processes

Hi automakers. I have a test-suite (with automake parallel) in which some of the test cases run multithreaded applications and therefore use eg four CPUs. In order to avoid total overload I currently reduce number of jobs e.g. 'make -j2' rather than 'make -j8', which is sort of waste because

Re: Broken install-data-yes target

On 06/06/2013 07:37 AM, Kip Warner wrote: Hey list, My make install target for my autotool'd project's translations directory has a number of prerequisites. The one which seems to be causing trouble is the install-data-yes target. Yes, I am aware the path I am using contains spaces and yes I am

Re: install-strip variant that strips then installs?

On 05/08/2013 02:12 AM, Rhys Ulerich wrote: I gather that 'make install-strip' installs and then strips binaries. Is there some variant that reverses the order? If not, any recommendations for how to write one in an Automake-compliant manner? Hi Rhys, I'm tempted to believe the DESTDIR

Re: serial-tests option and backwards compatibility

On 2/7/13 7:58 PM, Stefano Lattarini wrote: On 02/05/2013 12:22 AM, Peter Johansson wrote: On 02/04/2013 11:31 PM, Stefano Lattarini wrote: When I did this, I should really have published a 1.11.x release offering this same option as well; that would have removed all confusion. Sigh

Re: bug#13524: Improving user experience for non-recursive builds

, 'AM_', comes to mind: {AM_RELDIR}. cheers, -- Peter Johansson

Re: serial-tests option and backwards compatibility

On 02/04/2013 11:31 PM, Stefano Lattarini wrote: On 02/04/2013 01:16 AM, Luke Mewburn wrote: [CUT] Especially when the time between previous major releases was 2.5 years. Examining the Changelog and release dates: 2009-12-08 Release automake 1.11.1 2012-02-21 Add serial-tests support

bug#13378: Backward-compatibility in the autotools

On 01/12/2013 04:45 AM, Stefano Lattarini wrote: As a rule of thumb on when to remove a macro - I would personally like being able to write a configure script that works on both RHEL 5 (or CentOS 5) (autoconf 2.59, automake 1.9.6) as well as rawhide (eventually automake 1.14 and beyond),

Re: bug#13378: Backward-compatibility in the autotools

On 01/12/2013 04:45 AM, Stefano Lattarini wrote: As a rule of thumb on when to remove a macro - I would personally like being able to write a configure script that works on both RHEL 5 (or CentOS 5) (autoconf 2.59, automake 1.9.6) as well as rawhide (eventually automake 1.14 and beyond),

bug#13378: [IMPORTANT] Make the 'subdir-objects' setup the default, and only available one

Hi Stefano, On 01/08/2013 08:18 AM, Stefano Lattarini wrote: Actually no, the change tend to be much more extensive (as they've been between 1.12 and 1.13, not always smoothly or pleasantly). Maybe, to make this clear, we should name release a 2.0 version instead of a 1.14? No need, IMHO.

Re: Help2man and Parallel Make Race

because it creates a different dependency graph for maintainers and users similar to AM_MAINTAINER_MODE. Cheers, Peter -- Peter Johansson

Re: looking for a good example of non-recursive Make using project

have Automake fragments in a directory 'am/' which are included into Makefile.am [in topdir]. For those fragment files, it would probably be confusing if paths were inserted into variables. Perhaps one could have a switch to turn that feature on. Cheers, Peter -- Peter Johansson

Re: how to specify compile_et command in makefile.am

On 10/31/2012 04:57 PM, Coly Li wrote: Is there any method that I can add something into Makefile.am, so that the generated Makefile can looks like: -- foo_err.c foo_err.h: foo_err.et compile_et prof_err.et -- Sure add just that to Makefile.am and it should be

Re: [Automake] Including Shared Objects and other files in Makefile.am

On 10/03/2012 02:15 PM, Sujit Devkar wrote: Dear Sir/Madam, I am working on a C++ project in which I am trying to use autotools to make my project easy to deploy. I have some .so files in a directory and some other files in different directory. Before using autotools, I had a shell script to

help2man rule with non-recursive Makefile

that the rule was triggered before 'bin/svndigest' was built. What is the wisest solution for this problem? I can see that one could move the rule out from 'make all' or that one have different rules depending on building from VCS or tarball. Any thoughts? Cheers, Peter -- Peter Johansson

Re: help2man rule with non-recursive Makefile

On 9/30/12 8:27 PM, Peter Johansson wrote: Any thoughts? I should read the manual before making noise. Sorry. http://www.gnu.org/software/automake/manual/automake.html#Errors-with-distclean -- Peter Johansson

bug#12495: AC_CONFIG_HEADERS with

between your setup and mine is that I only have one Makefile. But I just recently converted to non-recursive makefiles, and haven't noticed this bug, which suggests this is a recent regression (1.12???). Cheers, Peter -- Peter Johansson

should aclocal warn when picking up installed macros???

Hi, I just helped a co-developer who experienced a mysterious autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force autoreconf: configure.ac: tracing autoreconf: configure.ac: adding subdirectory c++ to autoreconf autoreconf:

Re: using $(wildcard) in EXTRA_DIST

On 09/19/2012 04:23 PM, Vincent Torri wrote: Hey our documentation provides some images files in a subdirectory 'img'. So, in EXTRA_DIST, we have added: $(wildcard $(srcdir)/img/*.*) automake reports that warning: doc/Makefile.am:35: wildcard $(srcdir: non-POSIX variable name

bug#12130: Fwd: bug#12130: sudo make install applies umask to new directories

[CC coreutils this is http://lists.gnu.org/archive/html/bug-automake/2012-08/msg1.html] On 09/14/2012 07:29 PM, didi wrote: You can already do this. You can, e.g., install packages with make install MKDIR_P=mkdir -p -m 700 Unfortunately this doesn't seem to work properly, as the

bug#12130: Fwd: bug#12130: sudo make install applies umask to new directories

On 08/21/2012 02:46 PM, Jason Eisner wrote: Better idea: Have default 644 for files and 755 for directories, but let the user override this by explicitly specifying any of * the desired file permissions * the desired directory permissions for newly created directories * the desired group

distinguish automake 1.11 from 1.12+ at autoconf time

Hi, I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf time. I wonder is there's any documented macro that was introduced in 1.12 that I could use to m4_ifdef? Cheers, Peter

Re: distinguish automake 1.11 from 1.12+ at autoconf time

Hi Eric, On 08/07/2012 09:36 AM, Eric Blake wrote: On 08/06/2012 05:29 PM, Peter Johansson wrote: Hi, I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf time. I wonder is there's any documented macro that was introduced in 1.12 that I could use to m4_ifdef? If nothing

bug#12064: distclean failure with Automake 1.12.2

Hi automakers, I was about to make a release when I discovered that distcheck suddenly didn't work anymore. The distclean rule failed with Making distclean in doc make[2]: Entering directory `/home/peterJo/projects/software/yat-0.8.x/yat-0.8.2/_build/doc' Makefile:498:

Re: files left in build directory after distclean

On 05/30/2012 02:09 AM, Adam Mercer wrote: On Wed, May 23, 2012 at 6:13 PM, Peter Johanssontroj...@gmail.com wrote: For me distcheck complains about no sed file which is because you call it 'sed -f git_version.sed' while it should be 'sed -f $(srcdir)/git_version.sed' as the sed script is

Re: files left in build directory after distclean

On 05/24/2012 02:59 AM, Adam Mercer wrote: Hmm, distcheck is still complaining. I've attached a tarball containing a striped down version of my project which illustrates the problem. Can anyone see what I'm doing wrong? Hi Adam, For me distcheck complains about no sed file which is because

Re: files left in build directory after distclean

Hi Adam, On 05/24/2012 02:59 AM, Adam Mercer wrote: On Wed, May 23, 2012 at 10:03 AM, Adam Mercerramer...@gmail.com wrote: Is 'git_version.sed' intended to be distributed? If yes, you must place it in EXTRA_DIST (and you have an usage error in that you've not done so). Of course! Thanks, I

Re: bug#11356: automake 1.12 and (C) 2011

Hi Stefano, Sorry about this late reply. On 04/28/2012 12:34 AM, Stefano Lattarini wrote: --- a/bootstrap +++ b/bootstrap @@ -77,6 +77,8 @@ dosubst () { rm -f $2 in=`echo $1 | sed 's,^.*/,,'` + current_year=`date +%Y` test -n $current_year \ +|| { echo $me: cannot get current

Re: Wait, isn't rpath supposed to be set automagically?

On 2/26/12 11:31 PM, Miles Bader wrote: I think it's desirable that it just work wherever it gets installed, and no matter who installs it (e.g. prefix=$HOME should work, and shouldn't require setting LD_LIBRARY_PATH). In my case it did work with prefix=$HOME because in that case -rpath was

Re: Automake 1.11.1b test release

On 12/17/11 11:10 AM, Adam Mercer wrote: On Sat, Dec 10, 2011 at 13:03, Stefano Lattarini stefano.lattar...@gmail.com wrote: Please report bugs and problems tobug-autom...@gnu.org, and send general comments and feedback toautomake@gnu.org. On Mac OS X 10.7 (Lion) All 826 tests behaved as

Re: minor error and a question

On 11/30/11 11:11 AM, Joakim Tjernlund wrote: Question: make install always install all targets, even if some of then haven't been rebuilt since last install. Is it possible to have some dependency sensitive install so only rebuilt targets are reinstalled? Hi Jocke, In one of my projects I

Re: Could automake-generated Makefiles required GNU make?

On 11/24/11 11:40 AM, Bob Friesenhahn wrote: On Thu, 24 Nov 2011, Peter Rosin wrote: There is one possibly hard bootstrapping problem. What if you want to deploy some package that does not need a C compiler on some system that lacks both a C compiler and GNU Make? You would have problems there

bug#9242: distcheck fails when having TEST in sub-directory

Hello automakers, I have a non-recursive Makefile.am but keep the tests in sub-directory named test. Surprisingly distcheck fails for me with this set up, which to me seems to be caused by some VPATH issue. Below is a trimmed down test case that fails for me with make check-TESTS make[2]: ***

Re: ./configure can't find Boost headers

On 7/26/11 4:13 PM, myrdos2 wrote: I have the following configure.ac file: This is more of an Autoconf issue, so you may have better luck asking on autoconf at... # Checks for header files. AC_CHECK_HEADERS_ONCE([boost/asio.hpp boost/bind.hpp boost/function.hpp inttypes.h zlib.h]) Why not

bug#9026: Supporting $ACLOCAL_PATH?

Hi Bruno, On 7/8/11 5:24 PM, Bruno Haible wrote: +If you are using GNU @code{automake} 1.10 or newer, it is even easier: +Add the line + +@example +ACLOCAL_AMFLAGS = --install -I m4 +@end example + +@noindent +to your top level @file{Makefile.am}, and run @samp{aclocal --install -I m4}. +This

bug#7988: the manual suggests installing macro files to hard-coded location

Hello Stefano, On 3/19/11 8:36 AM, Stefano Lattarini wrote: On Saturday 05 February 2011, Peter Johansson wrote: I find the last sentence a bit strange because to me that sounds like Automake suggests that packagers should install macro files in a hard-coded directory not relative to $(prefix

Re: aclocal only picking up /usr/local/share and not /usr/share

[removing automake-patches] On 3/17/11 10:39 AM, Maynard Johnson wrote: you aclocal calls. Also, in the next automake release, aclocal will probably support a new 'ACLOCAL_PATH' environment variable that would help solving this kind of problems Well, you could always resort to adding proper

Re: $(srcdir)/foo is not generated because $(srcdir)/$(srcdir)/foo exists

Thanks Ralf for your quick reply, On 2/13/11 2:44 AM, Ralf Wildenhues wrote: I would prepend all lines of a rule with a TAB, not just those not following a backslash-escaped newline. I'm actually not totally sure whether that was for portability to non-Posix make or so automake would parse

  1   2   >