Remove SVR2 support from mountlist

2018-10-14 Thread Andrew Borodin
Hi! A year ago (commit 467061a2014d742a27eb8d4498e8d09fb3225d53), the SVR2 support was removed from fsusage. Should it be removed from mountlist either? -- Andrew

[PATCH] libc-config: merge from glibc

2018-10-14 Thread Paul Eggert
* lib/cdefs.h (__glibc_has_attribute): New macro. --- ChangeLog | 3 +++ lib/cdefs.h | 6 ++ 2 files changed, 9 insertions(+) diff --git a/ChangeLog b/ChangeLog index 31cf9791d..dcabc939b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,8 @@ 2018-10-15 Paul Eggert +

[PATCH] regex: depend on libc-config

2018-10-14 Thread Paul Eggert
* modules/regex (Depends-on): Add libc-config. This is needed after the recent autoupdate from glibc. --- ChangeLog | 6 ++ modules/regex | 1 + 2 files changed, 7 insertions(+) diff --git a/ChangeLog b/ChangeLog index acd7e51bc..31cf9791d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3

Re: Current requirements for Java

2018-10-14 Thread Akim Demaille
Hi all! > Le 14 oct. 2018 à 22:24, Bruno Haible a écrit : > > The essential reference is the timeline of Java releases: > https://en.wikipedia.org/wiki/Java_version_history Thanks! > As you can see, Java specification levels 1.3, 1.4, 1.5 are outdated for > more than 3 years. And level 1.6

Re: doc: update for Solaris 11.4

2018-10-14 Thread Paul Eggert
Bruno Haible wrote: - They added 'timegm' and 'timelocal', but since gnulib does not have a unit test for them, I have no idea how buggy they are. Paul, do you have a unit test for these functions in some corner? I'm afraid not, and it's low priority. timelocal is merely a

Re: Current requirements for Java

2018-10-14 Thread Bruno Haible
Hi Akim, > In Bison we have a Java backend. We use gnulib to handle the > Java tool chain. In particular, in configure.ac we have > > gt_JAVACOMP([1.3], [1.4]) > gt_JAVAEXEC > > it worked like a charm for years. > > Until macOS Mojave; Yu Yijun reported that we get: > > 467. java.at:367:

Re: Current requirements for Java

2018-10-14 Thread Paul Eggert
Akim Demaille wrote: he changed CONF_JAVAC='javac -target 1.4 -source 1.3' to CONF_JAVAC='javac -target 1.6 -source 1.6' and had all the tests pass without any error. I have absolutely no idea what that change implies. It means the Java compiler accepts Java 6 source code and

Current requirements for Java

2018-10-14 Thread Akim Demaille
In Bison we have a Java backend. We use gnulib to handle the Java tool chain. In particular, in configure.ac we have gt_JAVACOMP([1.3], [1.4]) gt_JAVAEXEC it worked like a charm for years. Until macOS Mojave; Yu Yijun reported that we get: 467. java.at:367: testing Calculator ...

localename: Add support for per-thread locales on Solaris 11.4

2018-10-14 Thread Bruno Haible
Solaris 11.4 has added uselocale(), newlocale(), etc. However, the data structure of locale_t does not contain the locale category names. But this is essential for gettext() to work, when a per-thread locale has been set! gettext() relies on the gnulib 'localename' module for fetching the name of

Re: Fix crash in gnulib-tool.py under Python 2.6 and lower

2018-10-14 Thread Darshit Shah
* Tim Rühsen [181014 15:07]: > On 13.10.18 23:19, Darshit Shah wrote: > > Well, I don't think there will be a Python 4 for a very long time. The major > > version number changes only for a large backwards incompatibility. It's > > taken > > them ~10 years and people still not on Python 3. > > >

Re: Fix crash in gnulib-tool.py under Python 2.6 and lower

2018-10-14 Thread Tim Rühsen
On 13.10.18 23:19, Darshit Shah wrote: > Well, I don't think there will be a Python 4 for a very long time. The major > version number changes only for a large backwards incompatibility. It's taken > them ~10 years and people still not on Python 3. > > Anyways, I don't think this will break even

Re: timevar: 3/3: use clock_gettime to get wall clock time

2018-10-14 Thread Bruno Haible
Akim Demaille wrote: > > ‘sys' -> 'wall' > > 易 The first of these characters is described by Emacs as "Not Assigned". Time to get a newer Emacs, I guess :) > Fixed. Can I push it? Sure. Bruno

wcsnrtombs: work around Solaris 11.4 bug

2018-10-14 Thread Bruno Haible
2018-10-14 Bruno Haible wcsnrtombs: Work around Solaris 11.4 bug. * m4/wcsnrtombs.m4 (gl_WCSNRTOMBS_WORKS_IN_TRADITIONAL_LOCALE): New macro. (gl_FUNC_WCSNRTOMBS): Invoke it. * doc/posix-functions/wcsnrtombs.texi: Mention the Solaris bug. diff --git

mbsnrtowcs: work around Solaris 11.4 bug

2018-10-14 Thread Bruno Haible
2018-10-14 Bruno Haible mbsnrtowcs: Work around Solaris 11.4 bug. * m4/mbsnrtowcs.m4 (gl_MBSNRTOWCS_WORKS_IN_TRADITIONAL_LOCALE): New macro. (gl_FUNC_MBSNRTOWCS): Invoke it. * doc/posix-functions/mbsnrtowcs.texi: Mention the Solaris bug. diff --git

doc: update for Solaris 11.4

2018-10-14 Thread Bruno Haible
Hi, Solaris 11.4 was released in August 2018. The relevant improvements are listed here: https://docs.oracle.com/cd/E37838_01/html/E60974/golbg.html >From the gnulib perspective, the notable changes are: - They added per-thread locales: functions newlocale, *_l, etc. - All libnsl functions

floor, ceil, trunc, truncf, truncl: Defeat GCC optimizations

2018-10-14 Thread Bruno Haible
On Solaris 11.4, a couple of *_LIBM variables come out wrong in config.status (empty instead of '-lm'). The reason are apparently optimizations by GCC 7. This fixes it. 2018-10-14 Bruno Haible floor, ceil, trunc, truncf, truncl: Defeat GCC optimizations. * m4/floor.m4

Re: timevar: 3/3: use clock_gettime to get wall clock time

2018-10-14 Thread Akim Demaille
> Le 14 oct. 2018 à 09:15, Bruno Haible a écrit : > > Hi Akim, > > Looks good, except for one copy mistake: >> + fprintf (fp, "%11.6f (%2d%%)\n", tv->elapsed.wall * 1e-9, sys); > ‘sys' -> 'wall' 易 Fixed. Can I push it?

Re: timevar: 3/3: use clock_gettime to get wall clock time

2018-10-14 Thread Bruno Haible
Hi Akim, Looks good, except for one copy mistake: > + fprintf (fp, "%11.6f (%2d%%)\n", tv->elapsed.wall * 1e-9, sys); 'sys' -> 'wall' Bruno

Re: timevar: 3/3: use clock_gettime to get wall clock time

2018-10-14 Thread Akim Demaille
Hi Bruno! > Le 13 oct. 2018 à 18:11, Bruno Haible a écrit : > > Hi Akim, > >> Or we filter on the percentages. > > Yes, filtering on percentages is the way to go. The user doesn't > care about contributions < 1% or < 0.5%. When people draw pie charts, > such minimal contributions are usually