message for Eric Blake

Eric, Hope you can read this through gmane. There are problems with your email account. I got this reply from: Mail Delivery Subsystem <[EMAIL PROTECTED]> - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> (reason: 550 5.1.1 Not our Customer) - Tran

Re: multiple invocations of gnulib-tool

Simon Josefsson wrote: > The problem is gone, but if anyone is interested, the reason the problem > occurred was that gnutls has several gnulib directories, one for LGPL > files that can be used by the library, and other gnulib directories for > GPL stuff. The string.h module is added in the LGPL

Re: Generating code coverage reports

jemarch-mXXj517/[EMAIL PROTECTED] writes: > Hi Simon. > >I was inspired by gnupdf's code coverage reports: > >http://www.gnupdf.org/prmgt/coverage/ > >So I looked into how to integrate a script to generate them for some of >my projects. I couldn't think of how to implement this as

Re: lib/regex_internal.h on 1.4.11

On Wed, Oct 08, 2008 at 02:06:28AM +0200, Bruno Haible wrote: > Eric Blake wrote: > > > Indeed, we're in a maze of twisty little HP cc compiler bugs: > > > > > >

Re: Generating code coverage reports

> Does that make sense? Oh, I am not that familiar with how the profiling code actually works, thanks for explaining. I haven't found anything in gnupdf that works around the problem, so maybe gnupdf is affected as well, but I am not certain. The stats stored in the .gcda files a

Re: [pdf-devel] Generating code coverage reports

Hi Simon. I was inspired by gnupdf's code coverage reports: http://www.gnupdf.org/prmgt/coverage/ So I looked into how to integrate a script to generate them for some of my projects. I couldn't think of how to implement this as a gnulib module, but I wrote rules for maintainer-m

Re: Generating code coverage reports

* Ludovic Courtès wrote on Tue, Oct 28, 2008 at 07:10:52PM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > FWIW, IIRC then the directory handling of the files was only fixed to be > > sane rather recently in the GCC tree (I guess 4.4 only). > > By "directory handling", you mean the locat

Re: new modules: times and sys_times

This part was forgotten, now pushed as well. /Simon >From 9903ce8582d50b6cd5338dd9ca06b674da7a6c36 Mon Sep 17 00:00:00 2001 From: Simon Josefsson <[EMAIL PROTECTED]> Date: Tue, 28 Oct 2008 18:22:28 +0100 Subject: [PATCH] Add files missing from last commit. --- tests/test-sys_times.c | 29

Re: Generating code coverage reports

Hi Ralf, Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Ludovic, Simon, > > * Ludovic Courtès wrote on Tue, Oct 28, 2008 at 05:48:12PM CET: >> >> Let me explain this. Suppose you have tests T1 and T2: >> >> * T1 uses code from foo.c and t1.c; >> * T2 uses code from foo.c and t2.c. >>

Re: new modules: times and sys_times

I have pushed this. /Simon >From 66de54f8a195583a3e324df9b8072faab7b76561 Mon Sep 17 00:00:00 2001 From: Simon Josefsson <[EMAIL PROTECTED]> Date: Tue, 28 Oct 2008 18:19:49 +0100 Subject: [PATCH] Add modules for sys/times.h header and times function. --- ChangeLog| 14

Re: Generating code coverage reports

Hello Ludovic, Simon, * Ludovic Courtès wrote on Tue, Oct 28, 2008 at 05:48:12PM CET: > > Let me explain this. Suppose you have tests T1 and T2: > > * T1 uses code from foo.c and t1.c; > * T2 uses code from foo.c and t2.c. > > Running "make check" runs T1, then T2: > > * T1 is run, prod

Re: Generating code coverage reports

[EMAIL PROTECTED] (Ludovic Courtès) writes: > Hi, > > Simon Josefsson <[EMAIL PROTECTED]> writes: > >> build-coverage: >> make CFLAGS=$(COVERAGE_OPTS) CXXFLAGS=$(COVERAGE_OPTS) VALGRIND= >> make CFLAGS=$(COVERAGE_OPTS) CXXFLAGS=$(COVERAGE_OPTS) VALGRIND= check >> mkdir -p doc/covera

Re: Generating code coverage reports

Hi, Simon Josefsson <[EMAIL PROTECTED]> writes: > build-coverage: > make CFLAGS=$(COVERAGE_OPTS) CXXFLAGS=$(COVERAGE_OPTS) VALGRIND= > make CFLAGS=$(COVERAGE_OPTS) CXXFLAGS=$(COVERAGE_OPTS) VALGRIND= check > mkdir -p doc/coverage > lcov --directory . --output-file doc/cove

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

2008/10/28 Simon Josefsson <[EMAIL PROTECTED]>: > I looked into this more, and it seems v2.4.x and older called strerror > inside cdk_strerror. However, the cdk_strerror function is itself > unused, so you can safely remove its definition from lib/opencdk/main.c. > I have made this change on the v

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

Eric Blake <[EMAIL PROTECTED]> writes: >> I found this while linking against gnutls, which uses the string >> module, which then uses '#define strerror rpl_strerror' in its lgpl >> library when strerror is not found. That, in turn, leads to an >> undefined rpl_strerror symbol in libgnutls.so. > >

Re: gnulib-tool (or something else?) misbehaving...

Jim Meyering wrote: > Updating ./gnulib/lib/.gitignore (backup in ./gnulib/lib/.gitignore~) > sed: file /u/jt503.zc6WFk/glnfwWQ6/sed-ignore-removed line 2: extra > characters after command > Creating ./gnulib/m4/.gitignore > Updating ./gnulib/tests/.cvsignore (backup in ./gnulib/tests/.cvs

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

Gary V. Vaughan wrote: > The easy fix would be to change both instances of 'strerror(-2)' > to 'strerror(1)' in strerror.m4 The 'strerror(-2)' is there on purpose: We don't want a strerror function that crashes. The comment in strerror.m4 says it: if test $gl_cv_func_working_strerror = no; th

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gary V. Vaughan on 10/27/2008 11:49 PM: > The current test code inside strerror.m4 says: > > AC_LANG_PROGRAM( > [[#include > ]], > [[return !*strerror (-2);]]) > > Which is fine for Solaris 9 and 10 w

gnulib-tool (or something else?) misbehaving...

FYI, I just saw this go by, but don't have time to diagnose it right now: [ BTW, my $TMPDIR is /u/jt503.zc6WFk ] Updating ./gnulib/lib/.gitignore (backup in ./gnulib/lib/.gitignore~) sed: file /u/jt503.zc6WFk/glnfwWQ6/sed-ignore-removed line 2: extra characters after command Creating ./gnu

lstat: LGPLv2+, tempname: depend on lstat

FYI, I've just pushed these two changes. The latter was needed on mingw. >From 3af39f5a9b75a2ca892a19c800cfe27cf0031b00 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Tue, 28 Oct 2008 11:55:43 +0100 Subject: [PATCH 1/2] * modules/lstat (License): Relicense: LGPL -> LGPLv2+.

Re: argp-tests: needs EXEEXT

Simon Josefsson <[EMAIL PROTECTED]> writes: > This patch fixes the argp failure in: > > http://autobuild.josefsson.org/gnulib/log-200810270833778763000.txt > > I have pushed it. > > I have been using the same idiom in e.g. gnutls for scripts that needs > to invoke built programs. Are there any th

Generating code coverage reports

FYI, I was inspired by gnupdf's code coverage reports: http://www.gnupdf.org/prmgt/coverage/ So I looked into how to integrate a script to generate them for some of my projects. I couldn't think of how to implement this as a gnulib module, but I wrote rules for maintainer-makefile's 'cfg.mk'.

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

I looked into this more, and it seems v2.4.x and older called strerror inside cdk_strerror. However, the cdk_strerror function is itself unused, so you can safely remove its definition from lib/opencdk/main.c. I have made this change on the v2.4.x branch as well, in case we ever make another relea

Re: strerror.m4 test fails incorrectly on solaris 8 and earlier [and bonus gnutls bug]

"Gary V. Vaughan" <[EMAIL PROTECTED]> writes: > [[Simon, I'm Cc:ing you for the gnutls bug at the bottom]] Thanks for looking into this. > Even with the strerror detection fixed, gnutls will still create > an unusable libgnutls.so whenever it is built on a machine that > doesn't provide a strerr