quickly become
a habit ... well, fairly quickly; the first couple of wasted
builds are a great inducement to learning :-)
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
,
Eric.
intermediate is foo.c (leaving aside the even-more-transient
y.tab. silliness); foo.o and foo.h are both legitimate final
products of the rule.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
; then $(CYGPATH_W)
'$<'; else $(CYGPATH_W) '$(srcdir)/$<'`; \
Notice the missing fi inside the backticks.
I don't have the automake sources in front of me, but the file to patch
gets installed as /usr/share/automake/am/depend2.am.
2002-11-14 Eric Blake <[EMAIL PR
rojects where you need a different version, name it
explicitly:
/usr/local/stow/automake-1.4/bin/automake [options]
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
der* -- but it understands Java better than I believe make
(and thus automake) ever will. So one possibility might be to
pull the code for the task out of ant, and turn it into a
standalone Java-compiler driver; then call it from a Makefile, as
the gods and Stuart Feldman intended :-) A few other
On Fri, Feb 14, 2003 at 06:41:04PM +, Dr. David Kirkby wrote:
> Eric Siegerman wrote:
> AC_HAVE_HEADERS(gsl/gsl_sf_ellint.h,[gsl_inc_count=$(($gsl_inc_count +
> 1))])
Right; "$((expr))" -- "arithmetic expansion" it's called in
ksh(1) -- is another nonstandar
On
some systems it's called "md5sum"; other systems might not have
it at all. But "cmp" is as sure to be there as are "cat" and
"ls".
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
l supported, but more or
less deprecated.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
me how to rewrite my
> makefiles the "right way".
>
> I suspect this is a dependency bug in the Debian packaging system, which
> ony people who don't know enough about autotools (like me) will
> experience, as everyone who knows will have upgraded automake already.
The
DIRS = ... ...
SUBDIRS = $(UNCONDITIONAL_SUBDIRS) @MAKE_SNTP@
DIST_SUBDIRS = $(UNCONDITIONAL_SUBDIRS) sntp
That won't solve your other problems of course.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
When I came back around from the dark side, the
the values into
it. Then call the script from the Makefiles, either explicitly
or via an implicit rule.
> -- and sometimes I need to do it to a file where there isn't a
> Makefile in that directory.
So add one...
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL P
ly runs if the first one succeeded, runs the tests
while ignoring errors.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
When I came back around from the dark side, there in front of me would
be the landing area where the crew was, and the Earth, all in the vi
Hello,
The mkinstalldirs script which ships with Autoconf and Automake leaves bogus
directories named "-p" and "--" in its wake on platforms (such as NextStep
and OpenStep) for which the `mkdir' command does not recognize any options.
Here is a patch which fixes this bug. The patch is base
Alexandre Duret-Lutz wrote:
Thank you. Automake is the master for this file. Given
Andrea's comment and yours about _AS_MKDIR_P_PREPARE, how about
the following instead?
+ test -d ./-p && rmdir ./-p
+ test -d ./-- && rmdir ./--
+ # Clean up after NextStep and OpenStep mkdir.
+
help
avoid them.
The situation seems very similar to that of Autoconf's
config.cache. Those files used to be kept between runs by
default, but it was decided that doing so causes too many
problems, so now the default is to throw them away; the user must
ask for the less-safe behaviour.
--
| |
ence to undefined
function bazzle(), but nothing *following* foo.o on the command
line can satisfy that reference. You get an "undefined" error.
But with:
ld foo.o -lbar
the linker knows, while searching -lbar, that it needs bazzle().
The situation with two libraries is s
hardwired,
it'll frustrate some users who want it the other way; and unless
all levels are hardwired the same way, it'll confuse and
frustrate *most* users.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have so
Hello,
Here is a patch for Automake which ensures that generated makefiles also
clean up config.status.lineno at distclean time. (Makefiles already know how
to clean up configure.lineno, but neglect to remove its cousin.)
Eric
2003-01-07 Eric Sunshine <[EMAIL PROTECTED]>
of the subpackage to be buildable,
you have to defeat this behaviour (or rather, you had to do so
the last time I tried it), by:
AC_CONFIG_AUX_DIR([.])
See http://www.mail-archive.com/[EMAIL PROTECTED]/msg08005.html
for the gory details.
--
| | /\
|-_|/ > Eric Siegerman, Tor
On Sat, 31 Jan 2004 23:28:29 +0100, Alexandre Duret-Lutz wrote:
> I'm posting it here for comment. (In fact I'm mainly hoping
> that some kind fellow will point out English mistakes...)
It is well written.
> One of the output (here `data.c') is used as a witness of the run of
> `foo'.
Perhaps:
d "foo" is suppressed.
This scales to multiple outputs too, but it gets a bit ugly, since
one has to impose a serial ordering on all of them:
data.c data.h data.x data.y: data.foo
foo data.foo
data.h: data.c
data.x: data.h
data.y: data.x
I h
On Thu, Feb 05, 2004 at 10:49:07AM +1100, Robert Collins wrote:
> On Thu, 2004-02-05 at 10:36, Eric Siegerman wrote:
>
> > I believe this fails on the following corner case. Suppose the
> > date ordering is like this (with data.h being the oldest):
> > da
it :-)
[Usually I avoid me-too posts, but in this case it seems
warranted.]
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground a
Hello all,
I have written (I am still writing actually) an application and use
automake/autoconf. I would like to have my headers to be installed under
/usr/local/include when applying make install.
I wonder if someone can help me how to reach this with automake.
Thanks for any contribution.
Thanks Adreas,
What about if my headers should be in /usr/local/include/myapp ?
cheers
On Wednesday 11 February 2004 15:22, you wrote:
> Eric Tchepannou <[EMAIL PROTECTED]> writes:
> > Hello all,
> >
> > I have written (I am still writing actually) an application an
0: using the `aclocal' command, and then run `automake' again.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau
be that the
right aclocal program is still finding the old 1.4 macros. I
don't know how to check for that, but take a look at aclocal.m4,
to see if you can find anything that indicates which version of
the Automake-related macros aclocal picked up.
--
| | /\
|-_|/ > Eric Siegerman, To
target for making the texinfo-based subset of the
HTML might indeed be "texinfohtml", and correspondingly for
install and uninstall. But that should be purely a detail of
automake's implementation:
html: texinfohtml whatever_other_html_targets_make_sense
It need not, a
because I chose to CVSify the package.
Maybe this isn't Karl's responsibility; and I'm not sure what, if
anything, can be done about it in any case; but it seemed worth
bringing up while we're on the subject.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROT
ion *not* as a criticism, but merely as a data point relevent
to the version-check question. It's perfectly ok to add new
features that require the new program version to process them;
it's a disregard for *backward* compatibility that's antisocial
behaviour, and again, I'm not acc
spec file is (intended to be) hand-written, or at
least hand-tuned; so decisions about which directories to
list in it are made by a human, not by code.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
It must be said that they would have sounded bette
Alexandre Duret-Lutz wrote:
This suggests that shell running this code does not split
$list and $subdir get the full list. Zsh would do that.
Could you compare the output of
grep 'SHELL =' Makefile
on the working and non-working tarballs?
CVS Autoconf has a new SHELL selection code. That could
On Sun, 18 Apr 2004 10:02:14 -0500 (CDT), Bob Friesenhahn wrote:
> On Sun, 18 Apr 2004, Alexandre Duret-Lutz wrote:
> > This suggests that shell running this code does not split $list
> > and $subdir get the full list. Zsh would do that. Could you
> > compare the output of grep 'SHELL =' Makefile
On Sun, 18 Apr 2004 23:18:05 +0200, Alexandre Duret-Lutz wrote:
> [EMAIL PROTECTED] selects the new pax format defined by POSIX
> +1003.1-2001. It supports filenames with up to 65535 characters.
> +However this format is very young and should probably be avoided in
> +all packages that do not targ
On Sun, 18 Apr 2004 13:08:54 -0500 (CDT), Bob Friesenhahn wrote:
> On Sun, 18 Apr 2004, Eric Sunshine wrote:
> > Can you apply the following manual edit to the configure script
> > (not the configure.ac file) and report if it fixes the problem?
> > In con
On Sun, 18 Apr 2004 16:45:00 -0500 (CDT), Bob Friesenhahn wrote:
> On Sun, 18 Apr 2004, Eric Sunshine wrote:
> > I can submit a patch to autoconf-patches to make Autoconf's shell
> > selection more backward-compatible with earlier versions of Autoconf,
> > however thi
On Mon, 19 Apr 2004 21:01:58 +0200, Alexandre Duret-Lutz wrote:
> A suggestion was to always use `SHELL = /bin/sh' in Makefiles.
> I simply don't know how correct this is, because that's how it
> was in the past before Chris Provenzano changed it to what it is
> now. The reason for that change see
No doctor visit needed
I don't like emails.
should be
modified to
handle subversion philosophy), and in particular when doing a 'svn copy'.
Thanks for your comments (and your solutions),
Eric PAIRE
Hello Gary,
Gary Thomas wrote:
Bonjour, Eric :-)
On Wed, 2004-12-01 at 04:38, Eric PAIRE wrote:
Hi all,
Here is the description of a problem met with subversion and autotools.
If anybody has a clean solution, let me/us know:
1) I have a project using the autotools for the environment management
Bob Friesenhahn wrote:
On Wed, 1 Dec 2004, Eric PAIRE wrote:
It this solution is so obvious, I don't understand why autotools
developers have not already set up a tool which automatically removes
the files generated by the autotools (perhaps this tool exists and I
don't know abou
hive/html/libtool-patches/2004-12/msg00091.html,
parsing $MAKEFLAGS is inherently non-portable. `info make' also has a
page dedicated to "Phony Targets" that discusses the more portable way to
have a recursive target, although I don't know how well it scales to the
more than 15 recu
mostlyclean-recursive,
> clean-recursive, distclean-recursive, maintainer-clean-recursive):
> Process all words of $MAKEFLAGS when checking for -k.
> * tests/check4.test: New file.
> * tests/Makefile.am (TESTS): Add check4.test.
> Report from Eric Blake.
I verified t
something1incdir = $(includedir)/dir1
something1inc_HEADERS = header1.h header2.h ...
something2incdir = $(includedir)/dir2
something2inc_HEADERS = header3.h hea
(clipped from
http://sources.redhat.com/ml/automake/2001-04/msg00346.html)
but that "something1incdir" do
AM_INIT_AUTOMAKE takes a VERSION option that does what you want.
--
I don't care where he was born. He's one of us, in all the ways
that matter most. (Even, perhaps, in the groping.)
-- Steven Den Beste, on Arnold Schwarzenegger
alternate names in config.h such as:
/* Define to the value of SEEK_SET from . */
#define MY_SEEK_SET 0
...
Can this be done in Autotools? If so, how?
Thanks,
Eric.
> -Original Message-
> From: Andreas Schwab [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 26, 2005 2:28 PM
> To: Eric Lemings
> Cc: 'autoconf@gnu.org'; 'automake@gnu.org'
> Subject: Re: Defining Macros With Literal Values
>
>
try to do the Right
Thing (which, as others have pointed out, is impossible in
theory), but to make Automake work better with stow, which makes
the Right Thing trivial.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
to me, Charlie Brown represented the co
t was
capable of removing a /usr/local!
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
to me, Charlie Brown represented the courage to be sincere in the face of
ridicule. he was NOT a loser.
thank you, Mr. Schulz.
- Robert C. Mayo
I have a directory that contains only source files that I only want to
compile when I do a make all. What should I put in the Makefile.am
file?
Thanks,
Eric.
age from
automake and failed to check for non-zero exit status. Automake won't
produce Makefile.in if required files are missing.
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
, so the test is always true.
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt virtualization library http://libvirt.org
s commit is purely for future repo archaeology.
Then it's not NEWS-worthy. It's worth keeping that analysis in the git
commit message (as you say, for repo archaeology), but let's limit it to
just there, rather than potentially causing users to worry about some
perceived loss of porta
elled $(MODULE). But
that is unrelated to fixing AM_SILENT_RULES to produce POSIX-compliant
makefiles.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
the old name to the previous node, then we may want
to move the anchor to appear after the @node.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
$(srcdir)/$@.in >$@.tmp
+ $(do_subst) $(srcdir)/$@.in | ./config.status --file=- >$@.tmp
chmod +x $@.tmp
chmod a-w $@.tmp
mv -f $@.tmp $@
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
in automake.
Re-read the list where we discussed this - gcc is doing a better
maintenance job of multilib support in the first place, so this move is
intended to point you towards the better-maintained source in the first
place.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt vi
figure out, but that should hopefully
help you get started on seeing how others have used it.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
by way of a
new standardized configure option for specifying the alternate package
name of the second installation, and then adding automake and/or
autoconf support for providing configure support for an alternate
package name, seems like it would be worthwhile for more than just grub.
--
Eric
t
> eats away space that could be used by those command lines? Oh joy ...
Yes. Unlike on *ix systems, where argv and environ are independent
entities, Windows makes you deal with both limits at the same time, so
increasing the size of environ reduces the size permitted in argv.
--
Eric Blake e
conditions make it so there are no
contents in a directory, then the directory is created _unless_ the
noinst_ prefix also appeared with that directory.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
ical way to do this?
No, because the moment you quit distributing these files, you have
required end users to have more tools available than normally required
by the GNU Coding Standards to even be able to use your tarball.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualizatio
these scripts are updated.
* config/srclist.txt: Drop elisp-comp, missing, and ylwrap.
* build-aux/elisp-comp: Delete.
* build-aux/missing: Likewise.
* build-aux/ylwrap: Likewise.
Signed-off-by: Eric Blake
---
Any objections to this patch?
ChangeLog|8 ++
build-aux/elisp-comp
[adding autoconf]
On 06/26/2012 12:26 PM, Bruno Haible wrote:
> Eric Blake wrote:
>> * build-aux/elisp-comp: Delete.
>
> What about modules/elisp-comp?
That module has only had one edit: it's introduction in 2006:
https://lists.gnu.org/archive/html/bug-gnulib/2006-08/msg0024
;
> ftp://ftp.gnu.org/gnu/automake/automake-1.11.6.tar.gz
> ftp://ftp.gnu.org/gnu/automake/automake-1.11.6.tar.xz
>
> Please report bugs and problems to , and send
> general comments and feedback to .
>
> Thanks to everyone who has reported problems, contributed patches,
> and
* Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> On 07/10/2012 12:14 AM, Eric Dorland wrote:
> >
> > Are older versions of automake also vulnerable?
> >
> Yes, all those back to 1.4 (at least). Sorry for not stating that
> explicitly.
Awesome :) Is there
* Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> On 07/10/2012 12:40 AM, Eric Dorland wrote:
> > * Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> >> On 07/10/2012 12:14 AM, Eric Dorland wrote:
> >>>
> >>> Are older versions of auto
* Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> On 07/10/2012 12:14 AM, Eric Dorland wrote:
> >
> > Are older versions of automake also vulnerable?
> >
> Yes, all those back to 1.4 (at least). Sorry for not stating that
> explicitly.
So I'm not obvi
* Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> On 07/12/2012 08:23 PM, Eric Dorland wrote:
> > * Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> >> On 07/10/2012 12:14 AM, Eric Dorland wrote:
> >>>
> >>> Are older versions of automake
gt; *not* fix it for the more modern versions (e.g., Automake 1.11), probably
> being convinced it had been solved as part of the fix for CVE-2009-4029;
> so I spoke too fast and inconsiderately by accusing them so somehow
> withold a security fix from upstream.
I didn't write the patch
there's
something you do with 1.12 that doesn't work with 1.11 and therefore you
are trying to make it conditional so that 1.11 can still process the
rest of the file. Determine that feature, and we are that much closer
to helping you conditionalize your configure.ac to work with both
I see v1.12.2, but no tag for v1.11.6 for the CVE-2012-3386 fix. Is
this intentional?
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
On 08/14/2012 04:24 PM, Stefano Lattarini wrote:
> Hi Eric.
>
> On 08/15/2012 12:16 AM, Eric Blake wrote:
>> I see v1.12.2, but no tag for v1.11.6 for the CVE-2012-3386 fix.
>>
> Hmm... I can see it without problems:
>
> <http://git.savannah.gnu.org/cgit/automa
fig.site that forces noisy builds. The
'silent-rules' change in automake change did NOT make more builds
instantly silent, nor are we preventing you from your goal of noisy
builds for the Fedora buildbots. Quit beating a dead horse to spread
FUD about something which is not true.
--
Er
u provided a feature that could be probed at m4
time in order to write a configure.ac that can then set an automake
conditional, so that Makefile.am can then set either INCLUDES or
AM_CPPFLAGS as appropriate within the two branches of the conditional.
--
Eric Blake ebl...@redhat.com+1-919-3
eloper_Toolset/1/html/User_Guide/chap-Red_Hat_Developer_Toolset.html#sect-Red_Hat_Developer_Toolset-About
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
ot;undefine" test script.
Indeed - while the upstream debate continues on whether 'make',
'automake', or both should be patched to allow 'undefine', downstream in
libvirt, I am pushing this trivial patch:
From a20f06d9d9b0353d7fb7a8e11a631253d5961b96 Mon Sep 17 00:
In all other cases, it makes more sense for the user to build the
binary themselves from the source (where user includes major distros,
who will then package it up in .rpm or apt formats as appropriate for
the distro, and where the distro package-manager software like yum or
apt-get can then b
otools is not the place to do this:
https://lists.gnu.org/archive/html/bug-autoconf/2012-09/msg00049.html
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
e}/file3.c ${more}/file4.c
so that a rename now only has to touch the 'more =' line, rather than
every use.
--
Eric Blake ebl...@redhat.com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
o type, without quite so much quoting:
version_suffix=dc_version_suffix
AS_IF([test "x$version_suffix" = "xdevel"], [
AC_DEFINE([USE_REVISION], [1], [Use the revision number.])
])
>
> Does anyone know how to implement this correctly?
It really depends on what you are trying to accomplish by deciding
something at m4 time, but deferring the action on that decision until
configure time.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
x27; should be rewindable.
>
> If you agree with my proposal, I think the new schemes could be
> implemented right after the 1.13.2 release; so that the planned
> Automake 1.13.3 will be released as 1.14, and the planned Automake
> 1.14 will be released as Automake 2.0.
I think it wo
hope that we can get automake stable enough that you can spend some fun
time with Automake-NG.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
hat it will be easier to fix issues upstream and re-release than to
make the distros have to carry downstream patches against configure.ac
and Makefile.am that require rerunning the autotools as part of the
distro process.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualizati
e Automake flags (in AM_INIT_AUTOMAKE, for example).
Or don't use $(shell), or upgrade to Automake-NG (which _requires_ GNU
make to be installed on the end-user's machine, and therefore should let
you use GNU make extensions without question).
--
Eric Blake eblake redhat com+1-91
On 04/01/2013 05:07 PM, Borchert, Oliver wrote:
> Eric and Russ,
>
> thanks for the reply. After long testing back and forth I decided to use
> AC_SUBST.
> My solution might not be the cleanest but it works for me.
It may work for you, but it alienates all users that were pre
eed across platforms?
.lo, on the other hand, is platform independent, so it needs no variable
wrapper.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
ion to this:
https://lists.gnu.org/archive/html/automake/2013-04/msg00014.html
with this answer of no (which really means: if YOU write the patches and
prove that they are worth maintaining, then it could be added in the
future, but no one else is interested in this unusual setup):
https://lists.gn
f the Automake-generated
> targets 'dist-shar' and 'dist-tarZ' will unconditionally display
> (non-fatal) warnings at make runtime.
>
> * New configure runtime warnings about "rm -f" support:
>
> - To simplify transition to Automake 2.0, the shell code expanded by
> AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
> 'rm' program in PATH doesn't complain when called without any
> non-option argument if the '-f' option is given (so that commands like
> "rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
> If this is not the case, the configure script is aborted, to call the
> attention of the user on the issue, and invite him to fix his PATH.
> The checked 'rm' behavior is very widespread in the wild, and will be
> required by future POSIX versions:
>
> <http://austingroupbugs.net/view.php?id=542>
>
> The user can still force the configure process to complete even in the
> presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
> environment variable to "yes". And the generated Makefiles should
> still work correctly even when such broken 'rm' is used. But note
> that this will no longer be the case with Automake 2.0 though, so, if
> you encounter the warning, please report it to us ASAP (and try to fix
> your environment as well).
>
>
>
--
Eric Dorland
ICQ: #61138586, Jabber: ho...@jabber.com
signature.asc
Description: Digital signature
d this to your configure.ac:
AC_SUBST([PYTHON], ...)
AC_CONFIG_FILES([script], [chmod +x script])
prior to the AC_OUTPUT, so that running config.status (as part of the
configure script itself) will automatically replace @PYTHON@ from the
script.in template into the output script without you rep
* Eric Dorland (e...@debian.org) wrote:
> Hi Stefano,
>
> I was just getting around to packaging this for Debian and I have a
> question. Given the new versioning scheme shouldn't the APIVERSION (as
> defined in configure.ac) be 1.13 and not 1.14? Or more precisely, does
>
* Dan Kegel (d...@kegel.com) wrote:
> On Thu, Aug 8, 2013 at 2:39 PM, Eric Dorland wrote:
> > Previously I would upgrade the automake package to the latest version
> > and add a new binary package for the previous version. So, for
> > example, if automake was at version 1.10
* Dan Kegel (d...@kegel.com) wrote:
> On Thu, Aug 8, 2013 at 4:43 PM, Eric Dorland wrote:
> >> That sounds kind of risky, promises of compatibility notwithstanding.
> >
> > Can you elaborate why?
>
> No. I'm just being paranoid. But there is good prece
* Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> [Re-adding the list, sorry for the confusion]
>
> On 08/12/2013 06:16 AM, Eric Dorland wrote:
> > * Stefano Lattarini (stefano.lattar...@gmail.com) wrote:
> >> Hi everybody.
> >
> > (You didn&#x
around. Perhaps others have better solutions?
And when you do come to consensus on the best solution, please also send
a patch to the autoconf list so that they can update their manual to
include it as an example.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library h
On 09/26/2013 12:13 PM, Diab Jerius wrote:
> On Thu, Sep 26, 2013 at 2:09 PM, Eric Blake wrote:
>> On 09/26/2013 10:16 AM, Diab Jerius wrote:
>>> I embarked on a journey yesterday involving automake, autotest, and
>>> non-recursive makes. I started with the
1 - 100 of 295 matches
Mail list logo
