Hi Karl,
Am 01.06.2015 um 23:02 schrieb Karl Berry :
> Running a configure script on solaris 5.10 generated with automake-1.15,
> I got these errors about id, which being pre-POSIX, does not support -u:
>
> id: illegal option -- u
> Usage: id [-ap] [user]
> id: illegal option -- g
On 19 Feb 2022 15:03, Patrice Dumas wrote:
> In Texinfo, we have a texinfo manual which is automatically generated
> from Pod sections from Texinfo perl modules. When this generated manual
> is removed, automake cannot run anymore. To workaround this issue, we
> have a generation of a fake manual
On 21 Dec 2018 10:46, Thomas Klausner wrote:
> When running the self tests on NetBSD (8.99.27/amd64) with perl
> 5.28.1, I see 26 test failures.
>
> The log is attached.
from the log:
> FAIL: t/instspc
this seems to be due to install-sh being used over normal mkdir -p. but
that should be fine b
On 20 Jan 2019 22:00, Dennis Clarke wrote:
> The usual. Nothing new here. Four failed tests on ye old Solaris 10
> sparc with Oracle Studio 12.6 compiler tools.
>
> test-suite.log attached.
from the log:
> FAIL: t/dist-formats
> + bzip2 -d parallel-compression-1.0.tar.bz2
> bzip2: Caught a SIG
Fixes automake bug https://bugs.gnu.org/32800.
Have the regex match the entire path with word boundaries on both
sides. This should reduce false positives when the full cwd happens
to match parent directories.
* t/silent-custom.sh: Update the header output regex.
---
t/silent-custom.sh | 2 +-
Fixes automake bug https://bugs.gnu.org/7610.
Use of \# is not portable. POSIX does not provide any way of retaining
the # marker in variables. There is wide spread support for \# though
in GNU & BSD Make implementations.
Today, with plain variable assignments, Automake leaves the line alone:
I think it would be a mistake to change where check-local runs,
in any way. In Peter's message, it is running after any $(check_DATA).
It does not seem that is still the case after your patch, Mike?
(As usual, I didn't actually try it. Sorry.)
Although it would be nice if there were perfect consis
Agreed that it is better to preserve the input text.
Agreed that a warning is indicated, but as Stefano suggested, I think
the warning should only be given if -Wportability is enabled (which it
is by default, I gather), not unconditionally. From our manual:
`portability'
Portab
Subject: bug#10828: [PATCH] rm: handle -f w/no arguments gracefully
Patch looks good to me (just reading through it).
Thanks for doing all that work. -k
if we can only test tools during configure, and the dist step
requires results from that probing ...
Fair enough. Patch is fine on that basis. --thanks, karl.
10 matches
Mail list logo
