Re: libposix build logs

Hi Ralf, On 01/02/11 04:44, Ralf Wildenhues wrote: >> I think the main hangout item is now just that autoconf macro. >> I would guess looking for version.h in /usr/local/include/libposix >> then /usr/include/libposix and provide a --with-libposix=/path. > > Well, the autoconfy way would be to not

Re: libposix build logs

Ralf Wildenhues wrote: > Or you could use pkg-config. > > Me ducks and runs Oh yes, after recommending pkg-config, you should duck and run :-) Bruno [1] http://lists.gnu.org/archive/html/bug-gnulib/2010-09/msg00266.html [2] http://lists.gnu.org/archive/html/bug-gnulib/2010-10/msg00188.html

Re: libposix build logs

Hi Bruce, * Bruce Korb wrote on Fri, Dec 31, 2010 at 12:38:10AM CET: > On my fully patched OpenSuSE 11.3 system, libposix now installs > the files listed below. What is still needed is an autoconf > macro used to detect libposix at some minimum version number. > Currently, the only annotated tag

Re: libposix build logs

On 12/26/10 00:54, Gary V. Vaughan wrote: > That's great news, thanks for following up. As soon as I have > time after the new year I will rerun the tests and let you know > how I get on. I've seen quite a few patches go by in relation > to my original reports; are you saying that (excepting the ab

Re: libposix build logs

Hi Gary, > are you saying that (excepting the above) everything I reported should now > be fixed? Or just the arches quoted above? Just the listed architectures! That means, currently glibc/Linux and OSF/1 5.1. I may also be working on Solaris and HP-UX. Someone else will have to AIX. > As soon

Re: libposix build logs

Hi Bruno, On 25 Dec 2010, at 21:42, Bruno Haible wrote: > Regarding your reports on glibc/Linux systems: >>> Distcheck results by architecture and compiler: >>> >>>ix86 RHEL 3 gcc 3.2.3 (317 tests passed) >>>ix86 RHEL 4 gcc 3.4.6 (test-fcntl-h-c++.cc compile failed:

Re: libposix build logs

I also pushed this, to simplify the logic of my previous change. It shouldn't affect whether the test succeeds. Sorry about the noise. >From f0f3beb58cf369ea9aa146c54422f834dacb84d8 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 25 Dec 2010 14:08:38 -0800 Subject: [PATCH] utimens: simplif

Re: libposix build logs

On 12/25/2010 06:42 AM, Bruno Haible wrote: > - On the first machine type (x86 RHEL 3), I get the test failures > related to NFS timestamps, mentioned in > . I looked into that, and there are some obvious problems with t

Re: libposix build logs

Hi Gary, Regarding your reports on glibc/Linux systems: > > Distcheck results by architecture and compiler: > > > > ix86 RHEL 3 gcc 3.2.3 (317 tests passed) > > ix86 RHEL 4 gcc 3.4.6 (test-fcntl-h-c++.cc compile failed: > > 133:

Re: libposix build logs

Hi Gary, On 2010-11-11 I wrote: > 2010-11-11 Bruno Haible > > fcntl-h: Fix for use of C++ on glibc systems. > * lib/fcntl.in.h: Include before include_next > also on glibc systems in C++ mode. > Reported by Gary V. Vaughan . This fixed only half of the problem. This

Re: libposix build logs

Gary V. Vaughan wrote on 2010-10-20: > dec Tru64 5.1 Compaq C 6.5 (mbrlen.c compile failed: > rpl_mbstate_t has no linkage and a > prior > declaration in scope at > 415:./wchar.h) >

Re: libposix build logs

Jim Meyering wrote: > > 2010-11-12 Bruno Haible > > > > openat: Work around glibc bug with fchownat() and empty file names. > > * m4/openat.m4 (gl_FUNC_FCHOWNAT_EMPTY_FILENAME_BUG): New macro. > > (gl_FUNC_FCHOWNAT): Invoke it. > > * lib/fchownat.c (rpl_fchownat): Handle the empt

Re: libposix build logs

Bruno Haible wrote: > Gary V. Vaughan wrote: >>>ix86 SLED 10 gcc 4.1.2 (fchownat, rename, renameat) > > I'm seeing this failure on a Linux/x86 machine (SUSE Linux Enterprise Server > 10, > Linux 2.6.16.60, glibc 2.4): > > test-chown.h:79: assertion failed > FAIL: test-fchownat >

Re: libposix build logs

Gary V. Vaughan wrote: >>ix86 SLED 10 gcc 4.1.2 (fchownat, rename, renameat) I'm seeing this failure on a Linux/x86 machine (SUSE Linux Enterprise Server 10, Linux 2.6.16.60, glibc 2.4): test-chown.h:79: assertion failed FAIL: test-fchownat The call that fails is ASSERT (fun

Re: libposix build logs

On 11/12/10 08:50, Bruno Haible wrote: > Bruce Korb wrote: >>> +#if !defined __GLIBC__ || (defined __cplusplus && defined GNULIB_NAMESPACE >>> && !(__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3))) >>> # include >> >> This fails, of course, for GCC >= 5.0. > > You mean, GCC 5.0 will rein

Re: libposix build logs

Bruce Korb wrote: > > +#if !defined __GLIBC__ || (defined __cplusplus && defined GNULIB_NAMESPACE > > && !(__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3))) > > # include > > This fails, of course, for GCC >= 5.0. You mean, GCC 5.0 will reintroduce a name mangling bug from GCC 4.2 that

Re: libposix build logs

On 11/11/10 18:21, Bruno Haible wrote: > 2--- lib/fcntl.in.h.orig Fri Nov 12 03:19:39 2010 > +++ lib/fcntl.in.hFri Nov 12 03:18:45 2010 > @@ -26,7 +26,13 @@ > /* Special invocation convention. */ > > #include > -#ifndef __GLIBC__ /* Avoid namespace pollution on glibc systems. */ > +

Re: libposix build logs

Gary V. Vaughan wrote: >>ix86 RHEL 4 gcc 3.4.6 (test-fcntl-h-c++.cc compile failed: >> 133: symbol `mknod' already defined) >>x86_64 RHEL 4igcc 3.4.6 (test-fcntl-h-c++.cc compile failed: >> 124: s

Re: libposix build logs

On 11/11/10 15:42, Bruno Haible wrote: > x86_64-redhat-linuxe3-libposix.log.bz2 contains a failure of > FAIL: test-fprintf-posix2.sh > FAIL: test-printf-posix2.sh > > But on the same build machine as you used (menori.il.thewrittenword.com), > with a testdir created with > $ ./gnulib-tool --c

Re: libposix build logs

Hi Gary, > I've regenerated and concatenated the build logs, config.log and verbose test > logs (on the machines that got that far) for the default compiler (whatever > configure discovered first) on most of the above machines. > > http://blog.azazil.net/buildlogs/ x86_64-redhat-linuxe3-libpos