Hi Jim,
* Jim Meyering wrote on Thu, May 14, 2009 at 03:21:11PM CEST:
Are you ready to release 1.11? ;-)
;-)
Using the latest from git/master (v1.10b-55-g27f63d4),
make check passed on each of the following systems:
Fedora rawhide
Fedora 10
Debian unstable
Red Hat Enterprise
Yes, score=5.4 required=5.0
tests=DATE_IN_FUTURE_24_48,RDNS_DYNAMIC,SPF_FAIL,WEIRD_PORT autolearn=no
version=3.2.5 (2008-06-10) host=yxa-v.extundo.com
---BeginMessage---
Hi! I installed automake 1.11 without any problems except that one
self-test failed, see snippet from tests/test-suite.log
Hi Ralf,
On Sun, 2009-05-17 at 09:41 +0200, Ralf Wildenhues wrote:
* Jürg Billeter wrote on Fri, May 15, 2009 at 03:50:55PM CEST:
This does not yet implement full per-target support for VALAFLAGS,
however, this change at least fixes building when there is only one
target per source file,
Hi Jürg,
* Jürg Billeter wrote on Fri, May 15, 2009 at 03:50:55PM CEST:
This does not yet implement full per-target support for VALAFLAGS,
however, this change at least fixes building when there is only one
target per source file, which is the most common situation.
When testing vala5.test
Hi Jürg,
* Jürg Billeter wrote on Sun, May 17, 2009 at 10:01:38AM CEST:
On Sun, 2009-05-17 at 09:41 +0200, Ralf Wildenhues wrote:
Please note that I'm really close to finishing 1.11, and considering
to postpone this change unless there is an easy way out.
I expect per-target VALAFLAGS
Hi Jürg,
I'm following up on this patch with this one, to document the temporary
requirement for GNU make and avoid test failure reports that we already
know of.
Cheers,
Ralf
Vala: for now, require GNU make.
* doc/automake.texi (Vala Support): GNU make is currently
required for
tags upstream fixed-upstream
thanks
[ adding automake-patches; see http://bugs.debian.org/524176 ]
Hello Matthias, and sorry for the delay,
* Matthias Klose wrote on Wed, Apr 15, 2009 at 12:17:57PM CEST:
The current implementation of the AM_PATH_PYTHON passes the unexpanded
'${prefix} and
[ adding automake-patches ]
* Ralf Wildenhues wrote on Sun, May 17, 2009 at 01:56:39PM CEST:
NetBSD (and other BSD) `make -jN' without `-B'
- reuses shells between multiple commands in one rule
(without resetting the working directory, environment variables etc),
- sprinkles --- $target
What about packages that don't support arbitrary prefix override
(all those using current libtool), or packages or systems that
don't support DESTDIR installs? This wording creates problems
for them.
Indeed - I want to be very clear in INSTALL that there are some
In addition, if you use an unusual directory layout you can give
options like @option{--bind...@var{dir}} to specify different
values for particular kinds of files. Run @samp{configure --help}
for a list of the directories you can set and what kinds of files
go
Indeed - I want to be very clear in INSTALL that there are some
basics that pretty much any client of this file provide (make, make
install), and some options that nice packages provide but which may
fail if someone borrowed this file but does follow everything
checked by automake's
Robert Collins wrote:
On Sat, 2009-05-16 at 19:04 -0500, Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to invoke the
pkg-config macro with --static (so that it does not select private libraries
in the .pc
Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to
invoke the pkg-config macro with --static (so that it does not select
private libraries in the .pc file)?
It seems that LT_INIT has been executed, the shell
Alfred,
can you please also read, and follow
http://lists.gnu.org/archive/html/autoconf/2009-05/msg00058.html?
I'm sure you must have missed it because I failed to spam it to three
mailing lists. But your repetitions are just as boring as those from
everyone else. And get bug-coreutils and
Hi Lorenzo,
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 09:07:16AM CEST:
Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to
invoke the pkg-config macro with --static (so that it does not select
private
Ralf Wildenhues wrote:
Hi Lorenzo,
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 09:07:16AM CEST:
Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to
invoke the pkg-config macro with --static (so that it does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add this:
%option prefix=prefix outfile=lex.yy.c
Dont change the outfile ylwrap needs it to be
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 12:27:32PM CEST:
Ralf Wildenhues wrote:
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 09:07:16AM CEST:
Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to
On Sun, 2009-05-17 at 11:49 +0100, Philip Herron wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add this:
%option prefix=prefix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ahh interesting, I did stumble upon your mail before but I missed
the bit about the outfile option, so I got stuck with that. I
guess this option is flex-specific but at this point I just want it
to work, portability is less important since only I
Hello,
* Philip Herron wrote on Sun, May 17, 2009 at 12:49:32PM CEST:
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add this:
%option prefix=prefix outfile=lex.yy.c
I don't see %option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
Hello,
* Philip Herron wrote on Sun, May 17, 2009 at 12:49:32PM CEST:
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add
* Philip Herron wrote on Sun, May 17, 2009 at 02:00:45PM CEST:
But i'll maby play with this. If i find a more standard solution what
should i do?
Write a patch (preferably against git master of Automake) that fixes the
Automake manual to document this precisely, and add a test to the test
suite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
* Philip Herron wrote on Sun, May 17, 2009 at 02:00:45PM CEST:
But i'll maby play with this. If i find a more standard solution
what should i do?
Write a patch (preferably against git master of Automake) that
fixes the
can you please also read, and follow
http://lists.gnu.org/archive/html/autoconf/2009-05/msg00058.html?
I'm sure you must have missed it because I failed to spam it to
three mailing lists. But your repetitions are just as boring as
those from everyone else. And get bug-coreutils
On Sun, 2009-05-17 at 13:46 +0200, Ralf Wildenhues wrote:
Hello,
* Philip Herron wrote on Sun, May 17, 2009 at 12:49:32PM CEST:
I solved this problem a while back!
http://lists.gnu.org/archive/html/automake/2009-04/msg00095.html
The trick is in each of your lexers(flex .l) add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey guys
I just made a quick test project there its not pretty but the
src/Makefile.am
bin_PROGRAMS = test
noinst_LIBRARIES = libparser_a.a libparser_b.a
test_SOURCES = main.c
test_LDADD = libparser_a.a libparser_b.a
libparser_a_a_YFLAGS = -d -p
Has anyone successfully written a configure.ac that successfully tests for the
Gnu Scientific Library (aka GSL)?
I would appreciate knowing how you did it?
Additional comment: GSL requires an additional library so that the traditional
test by compiling a test routine fails because there is no
Ralf Wildenhues wrote:
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 12:27:32PM CEST:
Ralf Wildenhues wrote:
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 09:07:16AM CEST:
Bob Friesenhahn wrote:
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared,
Is anyone aware of specific vendor make programs which fail with
automake 1.11's new `silent-rules' option?
- The `silent-rules' option enables Linux kernel-style silent build output.
This option requires the widely supported but non-POSIX `make' feature
of recursive variable
I see that the only way to request the new `silent-rules' feature is
by using the new form of AM_INIT_AUTOMAKE to pass the option. Since
my package can not use the new form of AM_INIT_AUTOMAKE, then it can
not request `silent-rules'.
The reason for this limitation is that using the new form
On Sunday 17 May 2009 2:52:17 pm Ralf Wildenhues wrote:
Hello Gerald,
* Gerald I. Evenden wrote on Sun, May 17, 2009 at 08:40:46PM CEST:
Has anyone successfully written a configure.ac that successfully tests
for the Gnu Scientific Library (aka GSL)?
AFAIK the GSL package distributes a
Bob Friesenhahn bfrie...@simple.dallas.tx.us writes:
The reason why my package can not use AC_INIT is that the package
version information is (often) computed by shell script code based on
the last entry in the project ChangeLog or other information. It is
(apparently) not possible for
On Sun, 2009-05-17 at 15:43 -0500, Bob Friesenhahn wrote:
The reason why my package can not use AC_INIT is that the package
version information is (often) computed by shell script code based on
the last entry in the project ChangeLog or other information. It is
(apparently) not possible
On Sun, May 17, 2009 at 4:43 PM, Bob Friesenhahn
bfrie...@simple.dallas.tx.us wrote:
I see that the only way to request the new `silent-rules' feature is by
using the new form of AM_INIT_AUTOMAKE to pass the option. Since my package
can not use the new form of AM_INIT_AUTOMAKE, then it can not
Bob Friesenhahn wrote:
It does not make sense to manually edit configure.ac each time a new
package needs to be produced.
Is there a way that some of my own script code can be executed prior to
AC_INIT and a way to pass this information in a shell variable to
AC_INIT? If so, then I can
On Sun, 17 May 2009, NightStrike wrote:
On Sun, May 17, 2009 at 4:43 PM, Bob Friesenhahn
bfrie...@simple.dallas.tx.us wrote:
I see that the only way to request the new `silent-rules' feature is by
using the new form of AM_INIT_AUTOMAKE to pass the option. Since my package
can not use the new
On Sun, 17 May 2009, Peter O'Gorman wrote:
Hi Bob,
You can use m4_easycmd to run your scripts at autoconf time. E.g. (from
autoconf itself):
AC_INIT([GNU Autoconf],
m4_esyscmd([build-aux/git-version-gen .tarball-version]),
[bug-autoc...@gnu.org])
I still owe you large quantities
On Sun, 17 May 2009, Bob Friesenhahn wrote:
I still owe you large quantities of beer. However, in order to clarify, I
would like to be able to execute configure script shell script code (more
like a configure test) and not generate a new configure script just because
the version has changed.
Hi Bob,
* Bob Friesenhahn wrote on Sun, May 17, 2009 at 09:59:17PM CEST:
Is anyone aware of specific vendor make programs which fail with
automake 1.11's new `silent-rules' option?
I don't know of any.
Cheers,
Ralf
Hi,
The instmany-python test is failing for me on Mac OS X 10.5.7. Looks
like it is trying to install things into /Library/Python, and as I did
not run make check as the superuser, can't.
Also, I wonder if it is worth checking for bsd''s 'jot' utility in these
tests that use seq?
Thanks,
Peter
Hi Bob,
* Bob Friesenhahn wrote on Sun, May 17, 2009 at 10:43:51PM CEST:
I see that the only way to request the new `silent-rules' feature is by
using the new form of AM_INIT_AUTOMAKE to pass the option. Since my
package can not use the new form of AM_INIT_AUTOMAKE, then it can not
42 matches
Mail list logo
