dclarke@charon:~/build/automake-1.11.2-001$ uname -a
Linux charon 2.6.32-5-powerpc64 #1 SMP Wed Jan 11 15:39:26 UTC 2012 ppc64
GNU/Linux
dclarke@charon:~/build/automake-1.11.2-001$ cat /proc/version
Linux version 2.6.32-5-powerpc64 (Debian 2.6.32-39squeeze1) (da...@debian.org)
(gcc version 4.3.5
Hi Dennis, thanks for the report.
On 01/20/2012 06:14 PM, Dennis Clarke wrote:
dclarke@charon:~/build/automake-1.11.2-001$ uname -a
Linux charon 2.6.32-5-powerpc64 #1 SMP Wed Jan 11 15:39:26 UTC 2012 ppc64
GNU/Linux
dclarke@charon:~/build/automake-1.11.2-001$ cat /proc/version
Linux
severity 10568 minor
severity 10565 minor
retitle 10565 specflg10.test failure
retitle 10568 specflg10.test failure
merge 10565 10568
thanks
Hi Dennis.
On 01/20/2012 08:48 PM, Dennis Clarke wrote:
=
1 of 643 tests failed
(92 tests were not run)
See
Stefano Lattarini skrev 2012-01-20 20:53:
On 01/19/2012 02:45 PM, Stefano Lattarini wrote:
[SNIP]
So, to all autoconfers: do you happen to know any reason for which Automake
should use F77FLAGS? If not, I'll assume that is due to a typo or clerical
mistake, and fix it (in 48 hours or so).
Stefano Lattarini skrev 2012-01-19 14:55:
* configure.ac: Look for generic C, C++ and Fortran compilers,
with the aim of starting to use them in the testsuite (this will
be done in future changes). This is more tricky than it seems,
since we don't want to abort the whole configure script even
Hi Peter.
On 01/20/2012 12:56 PM, Peter Rosin wrote:
Stefano Lattarini skrev 2012-01-19 14:55:
[MEGA-SNIP]
+# Prefer generic compilers to GNU ones when possible. This will ensure
+# more testsuite coverage in the wild.
+# FIXME: maybe we should a more comprehensive list too look for more
Stefano Lattarini skrev 2012-01-20 15:02:
Hi Peter.
On 01/20/2012 12:56 PM, Peter Rosin wrote:
Stefano Lattarini skrev 2012-01-19 14:55:
[MEGA-SNIP]
+# Prefer generic compilers to GNU ones when possible. This will ensure
+# more testsuite coverage in the wild.
+# FIXME: maybe we should
On 01/20/2012 06:14 PM, Peter Rosin wrote:
+
+# The list of C++ compilers here has been copied, pasted and edited
+# from `lib/autoconf/c.m4:AC_PROG_CXX' in the Autoconf distribution.
+# Keep it in sync, or better again, find out a way to avoid this code
+# duplication.
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?).
It's not considered portable make.
Still, it's worth
Hi Nick.
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 had actually specified the source file
normally. Presumably
=
1 of 643 tests failed
(92 tests were not run)
See tests/test-suite.log
Please report to bug-autom...@gnu.org
=
dclarke@charon:~/build$ uname -a
Linux charon 2.6.32-5-powerpc64 #1 SMP Wed Jan 11 15:39:26 UTC 2012 ppc64
On 01/19/2012 02:45 PM, Stefano Lattarini wrote:
[SNIP]
So, to all autoconfers: do you happen to know any reason for which Automake
should use F77FLAGS? If not, I'll assume that is due to a typo or clerical
mistake, and fix it (in 48 hours or so).
The attached patch should take care of
On Fri, 2012-01-20 at 20:35 +0100, Stefano Lattarini wrote:
What automake does for source files it knows about is just include
$(DEPDIR)/srcfile.Po (apparently include is considered portable
make?).
It's not considered portable make.
Still, it's worth noting that it works with every
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 Wed, Jan 18, 2012 at 8:49 PM, Miles Bader mi...@gnu.org wrote:
For cleaning non-automake-handled stuff, you can add a clean-local:
rule (and maintainer-clean-local: etc) that does cleaning however
you want. The automake-generated clean rule will depend on it, but
you control what it does.
16 matches
Mail list logo