Re: Haiku port status

On 2008-11-15 at 12:42:20 [+0100], Bruno Haible <[EMAIL PROTECTED]> wrote: Sorry for the late reply. I'm just back from a rather busy business trip and trying to catch up with my emails. > Ingo Weinhold [are you 'bonefish'?] wrote: I am indeed. On 2008-11-16 at 18:39:47 [+0100], Bruno Haible <

Re: gnulib/stdint.h not defining typedefs causes failures with Boost

Hi Alexandre, Alexandre Duret-Lutz wrote: > This is actually the third time I send this mail. Apparently mails > comming from lrde.epita.fr do not reach gnu.org :-( You can research about such issues at (courtesy to Jim for the link). > We have started

Re: code/module request: undo setuid

Ben Pfaff wrote: You might find the following paper on the topic interesting: http://www.usenix.org/events/sec02/full_papers/chen/chen.pdf the code in this paper is a perfect candidate for a gnulib module.

gnulib/stdint.h not defining typedefs causes failures with Boost

Hi people, This is actually the third time I send this mail. Apparently mails comming from lrde.epita.fr do not reach gnu.org :-( I'm trying again from gmail. We have started using gnulib in a C++ project that uses Boost. One of our build host is now failing as follows: gnulib/stdint.h has "#

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Brian Dessent <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: > >> +# gl_MANYWARN_ALL_GCC(VARIABLE) >> +# - >> +# Add all documented GCC (currently as per version 4.3.2) warning >> +# parameters to variable VARIABLE. Note that you need to test them >> +# using gl_

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Simon Josefsson wrote: > +# gl_MANYWARN_ALL_GCC(VARIABLE) > +# - > +# Add all documented GCC (currently as per version 4.3.2) warning > +# parameters to variable VARIABLE. Note that you need to test them > +# using gl_WARN_ADD if you want to make sure your gcc understa

Re: MacOSX Leopard gcc-4.2 build problems with coreutils-7.0 and its gnulib

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Thank you-all for responding. Just a quick reply from me for now, I'll get deeper into it later as my head stops swimming (too much going on right now lol). Before you-all branch-off too much, please understand I'm strictly trying to use the (l

Re: gnulib: cond & spinlocks

Bruno Haible wrote: Regarding clisp's xthread.d: The first thing I would do now is to ditch the conditional code for POSIXOLD_THREADS, SOLARIS_THREADS, C_THREADS. You don't need these APIs any more. And with pthreads-win32 you don't need WIN32_THREADS either. my whole point was that I want to _

Re: gnulib-tool and autoreconf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding autoconf list] According to Colin Watson on 11/18/2008 3:35 AM: > I find the advice in gnulib's documentation "Caveat: gettextize and > autopoint users" rather difficult to follow in practice. I prefer to use > autoreconf rather than having to

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> I'm preparing a blog post about gcc warnings, but briefly my idea with >> warnings.m4 is to enable all possible warnings, build your project once >> with -Werror, disable the warnings that cause problems (using >> gl_WARN_COMPLEM

Re: -Wunused

Bruno Haible <[EMAIL PROTECTED]> writes: >> Regarding -Wunused, I was unsure whether it needs to be added. The GCC >> 4.3.2 manual appears contradicting on whether -Wunused is implied by >> -Wall or not > > -Wunused-parameter is implied by the *combination* of -Wall and -W, or of > -Wunused and -

Re: distributing self-tests

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> It is unfortunate because sometimes you get reports about >> gnulib self-tests failures, e.g.: >> >> http://lists.gnu.org/archive/html/help-gsasl/2008-11/msg0.html > > This is good. If you had 'tests' before 'gltests' in SUB

Re: gnulib-tool and autoreconf

Colin Watson <[EMAIL PROTECTED]> writes: > I find the advice in gnulib's documentation "Caveat: gettextize and > autopoint users" rather difficult to follow in practice. I prefer to use > autoreconf rather than having to track which tools and options I'm > supposed to be using, but autoreconf invo

Re: distributing self-tests

Simon Josefsson wrote: > It is unfortunate because sometimes you get reports about > gnulib self-tests failures, e.g.: > > http://lists.gnu.org/archive/html/help-gsasl/2008-11/msg0.html This is good. If you had 'tests' before 'gltests' in SUBDIRS, from the fact that someone reports an error i

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Simon Josefsson wrote: > I'm preparing a blog post about gcc warnings, but briefly my idea with > warnings.m4 is to enable all possible warnings, build your project once > with -Werror, disable the warnings that cause problems (using > gl_WARN_COMPLEMENT), and set up so that the maintainer always b

Re: -Wunused

> Regarding -Wunused, I was unsure whether it needs to be added. The GCC > 4.3.2 manual appears contradicting on whether -Wunused is implied by > -Wall or not -Wunused-parameter is implied by the *combination* of -Wall and -W, or of -Wunused and -W. Bruno

Re: gnulib and distros

On Thu, Nov 06, 2008 at 09:46:45PM +0100, Sylvain Beucler wrote: > On Thu, Nov 06, 2008 at 10:17:21AM +0100, Jim Meyering wrote: > > [this thread started here: > > http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/15559 ] > > > > Sylvain Beucler <[EMAIL PROTECTED]> wrote: > > > FYI, Debian appar

Re: select self-tests causes build failures under mingw

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> I think it may be simpler to simply avoid using gnulib --with-tests when >> importing multiple gnulib instances into one project. It doesn't really >> seem to work reliably. > > I agree with this conclusion, and add some documen

Re: select self-tests causes build failures under mingw

Simon Josefsson wrote: > I think it may be simpler to simply avoid using gnulib --with-tests when > importing multiple gnulib instances into one project. It doesn't really > seem to work reliably. I agree with this conclusion, and add some documentation about it: 2008-11-18 Bruno Haible <[EMAI

Re: MacOSX Leopard gcc-4.2 build problems with coreutils-7.0 and its gnulib

SciFi <[EMAIL PROTECTED]> wrote: ... > I see the snapshot I made a little while ago of gnulib from the > git repo has already fixed this on 2008-10-08, but y'all > apparently don't have this snapshot in your coreutils & findutils > & other projects that use this module (available on the alpha FTP >

gnulib-tool and autoreconf

I find the advice in gnulib's documentation "Caveat: gettextize and autopoint users" rather difficult to follow in practice. I prefer to use autoreconf rather than having to track which tools and options I'm supposed to be using, but autoreconf invokes autopoint followed by the other tools without

Re: MacOSX Leopard gcc-4.2 build problems with coreutils-7.0 and its gnulib

Hello scifi, > I'd like to see how close we can get to having full 32- & 64-bit > universal binaries That's currently something that does not work, because autoconf tests can yield different results in the 32-bit and in the 64-bit case - and some actually do, see below. > (0) I'm building coreu

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Bruno Haible <[EMAIL PROTECTED]> writes: > Hi Simon, > > What is the use of these macros gl_WARN_COMPLEMENT, gl_WARN_SUPPORTED? > They are not documented, and you haven't said what they are good for. I'm using them in some packages like this: http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=bl

stdio: don't replace fseek unless requested

The stdio.in.h file replaces the fseek function when that isn't requested. There is a proper replacement for fseeko further down. How about the patch below? /Simon diff --git a/lib/stdio.in.h b/lib/stdio.in.h index 0e12d94..c4c2a8d 100644 --- a/lib/stdio.in.h +++ b/lib/stdio.in.h @@ -283,11 +28

Re: select self-tests causes build failures under mingw

Simon Josefsson wrote: > > First of all, would this be fixed by moving the define into lib/time.in.h? > > If the generated time.h file is placed in gl/tests/, then I think it > would work. But if it ends up in gl/ the src/*.c files will #include > it, and there will be the same problem again. Ye

Re: select self-tests causes build failures under mingw

Paolo Bonzini <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Paolo Bonzini <[EMAIL PROTECTED]> writes: >> Maybe gnulib self-tests directories should have their own configure.ac and config.h, although I fear the build-times of having 6 CONFIG_SUBDIR statements in GnuTLS...

Re: [PATCH] warnings: Add gl_WARN_COMPLEMENT and gl_WARN_SUPPORTED.

Hi Simon, What is the use of these macros gl_WARN_COMPLEMENT, gl_WARN_SUPPORTED? They are not documented, and you haven't said what they are good for. In particular, I don't see what anyone can do with the list of all GCC supported warning options. While -Wall is widely applicable, most other war