Re: follow-up on backdoor CPU usage (was: libsystemd dependencies)

2024-04-26 Thread Jacob Bachmeyer
Jacob Bachmeyer wrote: [...] The preliminary reports that it was an RCE backdoor that would pass commands smuggled in public key material in SSH certificates to system(3) (as root of course, since that is sshd's context at that stage) are inconsistent with the slowdown that caused the

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-20 Thread Bogdan
Gavin Smith , Sun Mar 19 2023 19:52:15 GMT+0100 (Central European Standard Time) On Sun, Mar 19, 2023 at 05:57:19PM +0100, Bogdan wrote: Anyway, I just provide code the way I'd do it. It's up to "someone higher up", like you, to make the decision if the patch is to be merged, modified first,

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-20 Thread Bogdan
Karl Berry , Mon Mar 20 2023 15:36:11 GMT+0100 (Central European Standard Time) Gavin, thanks for your comments. Always appreciated. Bogdan, thanks for the patch. I (or the mythical Someone Else) will look into it. My gut reaction is that it's good to make things work with old versions in

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-20 Thread Karl Berry
Gavin, thanks for your comments. Always appreciated. Bogdan, thanks for the patch. I (or the mythical Someone Else) will look into it. My gut reaction is that it's good to make things work with old versions in principle, although admittedly Apple's no-GPLv3 policy is not something we care about

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-19 Thread Gavin Smith
On Sun, Mar 19, 2023 at 05:57:19PM +0100, Bogdan wrote: > Anyway, I just provide code the way I'd do it. It's up to "someone higher > up", like you, to make the decision if the patch is to be merged, modified > first, or to be simply left out for some reason. There surely are things I > don't

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-19 Thread Bogdan
Gavin Smith , Sun Mar 19 2023 11:17:31 GMT+0100 (Central European Standard Time) On Sat, Mar 18, 2023 at 10:10:05PM +0100, Bogdan wrote: The problem was with "--build-dir=": the old texi2dvi (which is a shell script) splits "--build-dir=xxx" into "--build-dir" and "xxx", interprets the

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-19 Thread Gavin Smith
On Sat, Mar 18, 2023 at 10:10:05PM +0100, Bogdan wrote: > The problem was with "--build-dir=": the old texi2dvi (which is a shell > script) splits "--build-dir=xxx" into "--build-dir" and "xxx", interprets > the "--build-dir" switch as "--batch" (checks just the first letter, great) > and the

bug#29188: [PATCH] texi2dvi usage doesn't work with

2023-03-18 Thread Bogdan
Hello. The attached patch fixes bug#29188. The problem was with "--build-dir=": the old texi2dvi (which is a shell script) splits "--build-dir=xxx" into "--build-dir" and "xxx", interprets the "--build-dir" switch as "--batch" (checks just the first letter, great) and the "xxx" stays on

[bug#60771] [PATCH] tests: disable git log pager usage

2023-01-13 Thread Karl Berry
- (cd "$am_top_srcdir" && git log -1) || st=1 + (cd "$am_top_srcdir" && git --no-pager log -1) || st=1 Sure. Please commit. Thanks. -k

[bug#60771] [PATCH] tests: disable git log pager usage

2023-01-12 Thread Mike Frysinger
When running this code locally, the git log call can trigger a pager depending on the local settings, which in turn forces the test to be interactive. Run git with --no-pager to force disable it. * t/get-sysconf.sh: Run git with --no-pager. --- t/get-sysconf.sh | 2 +- 1 file changed, 1

bug#38043: [PATCH 1/6] py-compile: clean up usage info

2022-02-05 Thread Mike Frysinger
Include the full summary of options in the output. * lib/py-compile: Update usage output. * t/py-compile-usage.sh: Update test to match new output. --- lib/py-compile| 8 +++- t/py-compile-usage.sh | 4 ++-- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/lib/py

Minimal example for understanding the usage of TESTS in Makefile.am

2013-08-01 Thread Peng Yu
Hi, I'm not able to understand the usage of TESTS in Makefile.am, as there are many other things discussed in conjunction with TESTS and which obscures the description of TESTS. Could anybody point me a minimal example (without any things unrelated to TESTS) that demonstrates the usage of TESTS

Re: Minimal example for understanding the usage of TESTS in Makefile.am

2013-08-01 Thread Simon Richter
Hi, On 01.08.2013 00:46, Peng Yu wrote: I'm not able to understand the usage of TESTS in Makefile.am, as there are many other things discussed in conjunction with TESTS and which obscures the description of TESTS. Could anybody point me a minimal example (without any things unrelated

bug#12540: Usage of srcdir when valac is generating a header file

2012-10-02 Thread Stefano Lattarini
Thanks Nick for chiming in. Your explanation is basically right: Automake ought to place generated-but-distributed files in the source directory rather than in the build directory, for two major reasons: 1. as you've noted, putting such files in builddir could cause inconsistencies in

[Automake-NG] [FYI] [ng] tests: fix unportable $((...)) usage

2012-07-21 Thread Stefano Lattarini
* t/longline.sh: Use $i, not bare i, to reference the value of the shell variable 'i' in a $((...)) expression. Issue revealed by a failure with dash 0.5.2. Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com --- t/longline.sh |2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[Automake-NG] [PATCH] [ng] tests: fix unportable find(1) usage

2012-06-09 Thread Stefano Lattarini
* t/subobj10.sh: The use of find(1) without an explicitly given file or directory argument (as in find -name '*.o' instead of find . '-name.o') is mostly a GNU extension, and not portable to POSIX find. Fix it. Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com --- t/subobj10.sh |

Re: [PATCH] init: warn against obsolete usage of AM_INIT_AUTOMAKE

2012-05-06 Thread Stefano Lattarini
On 05/01/2012 06:11 PM, Stefano Lattarini wrote: Support for the two- and three-arguments invocation forms of the AM_INIT_AUTOMAKE macro, as in: AM_INIT_AUTOMAKE($PACKAGE, $VERSION) or: AM_INIT_AUTOMAKE($PACKAGE, $VERSION, NODEFINE) will be removed in the next major Automake

[PATCH 2/4] tests: fetch the 'ar-lib' script for archiver usage

2012-01-30 Thread Peter Rosin
From 2db9e742fea06449216b19d61707bc8362cdb612 Mon Sep 17 00:00:00 2001 From: Peter Rosin p...@lysator.liu.se Date: Mon, 30 Jan 2012 11:12:45 +0100 Subject: [PATCH 2/4] tests: fetch the 'ar-lib' script for archiver usage tests/libobj10.test: The archiver is used, so the 'ar-lib' script needs

Re: [PATCH 2/4] tests: fetch the 'ar-lib' script for archiver usage

2012-01-30 Thread Stefano Lattarini
On 01/30/2012 12:41 PM, Peter Rosin wrote: From 2db9e742fea06449216b19d61707bc8362cdb612 Mon Sep 17 00:00:00 2001 From: Peter Rosin p...@lysator.liu.se Date: Mon, 30 Jan 2012 11:12:45 +0100 Subject: [PATCH 2/4] tests: fetch the 'ar-lib' script for archiver usage tests/libobj10.test

Re: [PATCH 2/4] tests: fetch the 'ar-lib' script for archiver usage

2012-01-30 Thread Stefano Lattarini
for archiver usage tests/libobj10.test: The archiver is used, so the 'ar-lib' script needs to be present for inferior hosts. Fetch it. ACK for master. Oops, wait: you should add `* ' before `tests/libobj10.test' in the commit message. *Then* ACK for master. Sorry for the noise, Stefano

bug#10210: [PATCH] lib/depcomp: spelling fix in usage message

2011-12-04 Thread Stefano Lattarini
2001 Message-Id: 053534fc5718ad3aea4f2f1c5817d2a114fe5699.1322997518.git.stefano.lattar...@gmail.com From: Paul Eggert egg...@cs.ucla.edu Date: Sun, 4 Dec 2011 12:11:30 +0100 Subject: [PATCH] depcomp: spelling fix * lib/depcomp (-h): Fix misspelling in usage diagnostic. --- ChangeLog |5

bug#10210: [PATCH] lib/depcomp: spelling fix in usage message

2011-12-03 Thread Paul Eggert
Found while spell-checking Emacs. Here's a proposed patch. There are similar misspellings in the ChangeLogs but that's less important. depcomp: spelling fix * lib/depcomp (-h): Fix misspelling in usage diagnostic. diff --git a/lib/depcomp b/lib/depcomp index 9825d56..b97ed64 100755 --- a/lib

Re: * tests/amhello-binpkg.test: Add missing $EXEEXT usage.

2011-09-05 Thread Stefano Lattarini
On Monday 05 September 2011, Peter Rosin wrote: Hi! Hi Peter, thanks for the patch. This fixes a fail on Cygwin (and others I suppose). I'm aware that the lax non-gnu-tar branch adds even more laxness since $EXEEXT normally contains a dot for the oddball cases when it's non-empty, but

Re: * tests/amhello-binpkg.test: Add missing $EXEEXT usage.

2011-09-05 Thread Peter Rosin
Den 2011-09-05 10:06 skrev Stefano Lattarini: On Monday 05 September 2011, Peter Rosin wrote: Hi! Hi Peter, thanks for the patch. This fixes a fail on Cygwin (and others I suppose). I'm aware that the lax non-gnu-tar branch adds even more laxness since $EXEEXT normally contains a dot for

Re: * tests/amhello-binpkg.test: Add missing $EXEEXT usage.

2011-09-05 Thread Peter Rosin
Den 2011-09-05 11:37 skrev Stefano Lattarini: On Monday 05 September 2011, Peter Rosin wrote: Den 2011-09-05 10:06 skrev Stefano Lattarini: On Monday 05 September 2011, Peter Rosin wrote: Hi! Hi Peter, thanks for the patch. This fixes a fail on Cygwin (and others I suppose). I'm aware

Re: * tests/amhello-binpkg.test: Add missing $EXEEXT usage.

2011-09-05 Thread Stefano Lattarini
On Monday 05 September 2011, Peter Rosin wrote: Den 2011-09-05 11:37 skrev Stefano Lattarini: Ouch! Silly me for not thinking about that. And the quoting was off too, should have been s/\././g to do what you intended... :-) Double ouch, you're right again! $ x=`echo a.b |

* tests/amhello-binpkg.test: Add missing $EXEEXT usage.

2011-09-04 Thread Peter Rosin
2011-09-05 Peter Rosin p...@lysator.liu.se * tests/amhello-binpkg.test: Add missing $EXEEXT usage. From 396f69c65ddc01ebbcfcccb59381a80b9c050b1a Mon Sep 17 00:00:00 2001 From: Peter Rosin p...@lysator.liu.se Date: Mon, 5 Sep 2011 00:31:48 +0200 Subject: [PATCH] * tests/amhello-binpkg.test

[PATCH 4/4] {testsuite-work} tests: better respect of TAP usage in wrapped tests

2011-08-29 Thread Stefano Lattarini
index be5d736..4ca10ca 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,14 @@ 2011-08-29 Stefano Lattarini stefano.lattar...@gmail.com + tests: better respect of TAP usage in wrapped tests + * tests/gen-wrap-tests: Partial rewrite to take into account the + possibility

Re: [FYI] {master} docs: fix unportable example of AM_TESTS_ENVIRONMENT usage

2011-06-30 Thread Ralf Wildenhues
Hi Stefano, * Stefano Lattarini wrote on Thu, Jun 23, 2011 at 10:56:31PM CEST: On Thursday 23 June 2011, Ralf Wildenhues wrote: -AM_TESTS_ENVIRONMENT = exec 92; warn_fileno=9; export warn_fileno; This example served two purposes: use of AM_TESTS_ENVIRONMENT, and showing how to produce

Re: [FYI] {master} docs: fix unportable example of AM_TESTS_ENVIRONMENT usage

2011-06-30 Thread Stefano Lattarini
On Thursday 30 June 2011, Ralf Wildenhues wrote: Hi Stefano, * Stefano Lattarini wrote on Thu, Jun 23, 2011 at 10:56:31PM CEST: On Thursday 23 June 2011, Ralf Wildenhues wrote: -AM_TESTS_ENVIRONMENT = exec 92; warn_fileno=9; export warn_fileno; This example served two purposes:

Re: [FYI] {master} docs: fix unportable example of AM_TESTS_ENVIRONMENT usage

2011-06-30 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Thu, Jun 30, 2011 at 10:45:02PM CEST: On Thursday 30 June 2011, Ralf Wildenhues wrote: I'm fairly sure that's only with historic shells and not an issue in practice any more (Sven Mascheck's pages will have the details for the curious). Anyway, I do think that

[FYI] {master} docs: fix unportable example of AM_TESTS_ENVIRONMENT usage

2011-06-23 Thread Stefano Lattarini
-world usage (the GNU coreutils testsuite). --- ChangeLog | 10 ++ doc/automake.texi | 32 +--- 2 files changed, 27 insertions(+), 15 deletions(-) diff --git a/ChangeLog b/ChangeLog index f121e0e..d226120 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3

Re: [FYI] {master} docs: fix unportable example of AM_TESTS_ENVIRONMENT usage

2011-06-23 Thread Ralf Wildenhues
'). Give another example, simpler this time, but still inspired to real-world usage (the GNU coreutils testsuite). --- a/doc/automake.texi +++ b/doc/automake.texi @@ -8742,21 +8742,23 @@ code and set environment variables for the tests' runs. The user can still employ the @code

[FYI] {master} tests: fix spurious failure (non-renamed AM_TESTS_SETUP usage)

2011-04-24 Thread Stefano Lattarini
, 24 Apr 2011 18:08:44 +0200 Subject: [PATCH] tests: fix spurious failure (non-renamed AM_TESTS_SETUP usage) * tests/parallel-tests-reset-term.test: Use AM_TESTS_ENVIRONMENT instead of AM_TESTS_SETUP (which has been removed in commit v1.11-349-g12f48fa). Fix spurious failure introduced by merge

drop usage of obsolete AC_OBJEXT and AC_EXEEXT

2008-03-08 Thread Ralf Wildenhues
Applied to master and branch-1-10. Cheers, Ralf 2008-03-08 Ralf Wildenhues [EMAIL PROTECTED] Drop usage of obsolete macros AC_EXEEXT and AC_OBJEXT. * tests/ansi4.test: Drop AC_OBJEXT and AC_EXEEXT. * tests/ansi6.test: Likewise. * tests/ansi7.test: Likewise

GNU Mach's usage of the Auto* tools (was: [OT] avoid long ac_user_opts line in configure)

2007-01-15 Thread Thomas Schwinge
[Moved to the autoconf@gnu.org and automake@gnu.org mailing lists.] Hello! On Thu, Jan 11, 2007 at 12:17:25AM +0100, Ralf Wildenhues wrote: * Thomas Schwinge wrote on Wed, Jan 10, 2007 at 09:40:41PM CET: #v+ $ ~/tmp/source/gnumach/clean/gnumach-1-branch/configure --help | egrep ^\ \

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
Hi Ralf Norbert Sendetzky wrote: This works, but as soon as I move AM_CFLAGS to the Makefile.am in the parent directory, they aren't set any more. Is this the way it was intended and the only way to set them globally is to AC_SUBST them or is there something wrong in my files?

Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Corsepius
On Mon, 2006-06-12 at 10:16 +0200, Norbert Sendetzky wrote: Hi Ralf Norbert Sendetzky wrote: This works, but as soon as I move AM_CFLAGS to the Makefile.am in the parent directory, they aren't set any more. Is this the way it was intended and the only way to set them globally is

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
On Monday 12 June 2006 10:28, Ralf Corsepius wrote: Note though that -Wall -ansi -pedantic is pretty GCC specific, and will make many other compilers barf heavily. So if your package targets portability, it'd be nice to allow your users to override these flags (preferably by

Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Wildenhues
* Norbert Sendetzky wrote on Mon, Jun 12, 2006 at 11:06:36AM CEST: On Monday 12 June 2006 10:28, Ralf Corsepius wrote: Note though that -Wall -ansi -pedantic is pretty GCC specific, and will make many other compilers barf heavily. So if your package targets portability,

Re: AM_CFLAGS usage

2006-06-12 Thread Norbert Sendetzky
On Monday 12 June 2006 12:53, Ralf Wildenhues wrote: : ${CFLAGS='-Wall -ansi -pedantic'} before AC_PROG_CC in configure.ac. Users with non-GCC compilers won't like you because they will have to set CFLAGS to override this, and users (with any kind of compiler) won't like you because you

Re: AM_CFLAGS usage

2006-06-12 Thread Ralf Wildenhues
Hello Norbert, * Norbert Sendetzky wrote on Mon, Jun 12, 2006 at 06:42:15PM CEST: Ehm, where do I find the documentation to config.site? Oh, sorry, I forgot to mention that config.site is an Autoconf feature. Its manual has the information. (The current manual isn't online, but let's hope

Re: AM_CFLAGS usage

2006-06-11 Thread Ralf Wildenhues
Hello Norbert, Marc, Norbert Sendetzky wrote: This works, but as soon as I move AM_CFLAGS to the Makefile.am in the parent directory, they aren't set any more. Is this the way it was intended and the only way to set them globally is to AC_SUBST them or is there something wrong

Re: some usage questions

2004-09-07 Thread Alexandre Duret-Lutz
Martin == Martin MAURER [EMAIL PROTECTED] writes: [...] Martin I thought about a noinst library, and this might be an option. It is. Martin what i would like to have is a configure file in the Martin toplevel directory, which then checks the dependencies Martin for all the clients and

some usage questions

2004-08-31 Thread Martin MAURER
Hello all, I am developing a project (http://fireflier.sf.net), which uses automake. I don't know a lot about automake, and so far i didnt find documentation, which helps me with my problem - so any pointers in the correct direction will be appreciated. fireflier is a interactive firewall system

Usage

2003-12-24 Thread John Darrington
Recent versions of auto{make,conf} have become a pain to use. Especially if you're using gettext too. I think that some of these tools are trying to be just a little bit too clever. One particular problem is the way in which they modify each other's input files. After a while, your Makefile.am

Re: Usage

2003-12-24 Thread Tom Tromey
John == John Darrington [EMAIL PROTECTED] writes: John One particular problem is the way in which they modify each other's John input files. After a while, your Makefile.am looks like this: John SUBDIRS= intl m4 intl m4 intl m4 intl m4 intl m4 intl m4 John intl m4 intl m4 Report this as

automake usage

2001-06-29 Thread Tom Tromey
Today I wrote a dumb little script to estimate how often automake is used. The script searches a set of SRPM files for `configure.in' and `Makefile.am' files, and generates a report showing how many packages use autoconf and how many use automake. Then I ran this script on all the SRPMs in Red