RE: coreutils-8.14.116-1e18d on HP-UX 11.00

Bruno Haible wrote: > Hi Jim, > > > How about this? > > > > if (diff -u out out < /dev/null) > /dev/null 2>&1; then > > > > As usual, since your name is on it, I'll wait for an ACK > > before pushing it. > > Yes, that's just as good. Thanks! Do we really need a subshell here? This should

Re: gnulib-tool recommendations don't honour command line flags

>> I've invoked gnulib-tool as follows: >> >> gnulib-tool --import \ >> --m4-base=gnulib/m4 \ >> --source-base=gnulib/src \ >> --aux-dir=gnulib getopt-gnu >> >> and the recommendations emitted say this: >> >> Don't forget to >> - add "lib/Makefile"

Re: git-merge-changelog

> The only special "program" in gnulib is git-merge-changelog; > though now that I think about it, it makes more sense to split > out git-merge-changelog into a seperate project. Yes, you're entirely right. The project has been created already: http://savannah.gnu.org/projects/vc-ch

Re: gnulib-tool recommendations don't honour command line flags

Hi Werner, > I've invoked gnulib-tool as follows: > > gnulib-tool --import \ > --m4-base=gnulib/m4 \ > --source-base=gnulib/src \ > --aux-dir=gnulib getopt-gnu > > and the recommendations emitted say this: > > Don't forget to > - add "lib/Makefi

Re: doc: update for recent Solaris release

Simon Josefsson wrote: > All the marketing materials seems to label it as "Solaris 11 11/11". > Where is "Solaris 11 2011-11" used? I took the freedom of transforming the month designation to ISO 8601 format. Two-letter year abbreviations are terrible. Bruno

Re: doc: update for recent Solaris release

Bruno Haible writes: > Oracle released a new version of Solaris 11, in November 2011. The > codename is "Solaris 11 2011-11". Oracle no longer labels it as > "Solaris 11 Express", merely "Solaris 11". All the marketing materials seems to label it as "Solaris 11 11/11". Where is "Solaris 11 2011-

setlocale: avoid test failure on Solaris 11 2011-11

On Solaris 11 2011-11, I see a test failure: Turkish_Turkey.65001: unknown locale setlocale did not fail for explicit (NULL) FAIL: test-setlocale2.sh The reason is that /bin/sh does not like to set LC_ALL to some values: $ /bin/sh -c 'LC_ALL=Turkish_Turkey.65001 pwd' Turkish_Turkey.65001:

posix_spawn_file_actions_addclose on Solaris 11

On Solaris 11 2011-11, I'm seeing these test failures: test-posix_spawn_file_actions_addclose.c:43: assertion failed FAIL: test-posix_spawn_file_actions_addclose test-posix_spawn_file_actions_adddup2.c:43: assertion failed FAIL: test-posix_spawn_file_actions_adddup2 test-posix_spawn_fi

doc: update for recent Solaris release

Oracle released a new version of Solaris 11, in November 2011. The codename is "Solaris 11 2011-11". Oracle no longer labels it as "Solaris 11 Express", merely "Solaris 11". Not much has changed. The most notable change is the new fexecve() function. Let me update the doc. 2012-01-08 Bruno Hai

Re: import question

Hi Werner, Werner LEMBERG wrote: > ... then adding the imported files to the repository. > > I wonder whether the step `adding files to the repository' is > necessary at all. Why not simply calling gnulib-tool directly in the > `autogen.sh' script? Yes. This is in fact what the majority of proj

Re: mktime.c compilation error on Solaris 11

Paul Eggert wrote: > Wow, that's a weird GCC bug. Thanks for diagnosing it, > and your fix looks good. AFter the GCC folks fix it, > we can update mktime.c to use the pragma on sufficiently-new > GCC versions. Indeed, even the newest GCC release (4.6.2) has the bug. Pushed. Bruno

Re: import question

> I (and AFAIK, everyone who contributes regularly here) recommend > *not* to version-control the files that gnulib-tool imports. Good to know. What a relieve :-) Thanks for the answer! Werner

Re: mktime.c compilation error on Solaris 11

Wow, that's a weird GCC bug. Thanks for diagnosing it, and your fix looks good. AFter the GCC folks fix it, we can update mktime.c to use the pragma on sufficiently-new GCC versions.

Re: import question

Werner LEMBERG wrote: > the normal usage of gnulib is to import files into a project, this is, > calling `gnulib-tool --import', then adding the imported files to the > repository. Hi Werner, In my experience, that is not "normal usage". I (and AFAIK, everyone who contributes regularly here) reco

mktime.c compilation error on Solaris 11

On Solaris 11 2011-11 the vendor gcc 4.5.2 cannot compile gnulib's mktime.c: $ make ... gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DGNULIB_STRICT_CHECKING=1 -Wall -D_REENTRANT -g -O2 -MT mktime.o -MD -MP -MF $depbase.Tpo -c -o mktime.o mktime.c &&\ mv -f $depbase.Tpo $depbase.Po Assembler: mkti

lgpl-3.0

For some reason this module didn't exist. /Simon >From c89475637b827cd743ea80e1600c54a1d7af1867 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sun, 8 Jan 2012 14:49:07 +0100 Subject: [PATCH] Add lgpl-3.0 module. * MODULES.html.sh (Support for building documentation): Add lgpl-3.0. * modul

import question

Folks, the normal usage of gnulib is to import files into a project, this is, calling `gnulib-tool --import', then adding the imported files to the repository. I wonder whether the step `adding files to the repository' is necessary at all. Why not simply calling gnulib-tool directly in the `au

gnulib-tool recommendations don't honour command line flags

[gnulib commit 60224129] I've invoked gnulib-tool as follows: gnulib-tool --import \ --m4-base=gnulib/m4 \ --source-base=gnulib/src \ --aux-dir=gnulib getopt-gnu and the recommendations emitted say this: Don't forget to - add "lib/Makefile" to

[PATCH] select.c: indent with spaces, not TABs

FYI, >From 1fa2b522480d4834a8c2724eec571d5ad56031e4 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sun, 8 Jan 2012 14:35:22 +0100 Subject: [PATCH] select.c: indent with spaces, not TABs * lib/select.c (windows_poll_handle): Indent with spaces, not TABs. --- ChangeLog|5 + lib/sel