Re: module gethostname

2010-09-15 Thread Dustin J. Mitchell
On Wed, Sep 15, 2010 at 12:01 PM, Bruce Korb wrote: > So, let's start that discussion again:  let's make an installable > gnulib that basically does all the configure tests for the current > target and cover 99% of all configure runs.  If someone has > a strange configuration with extra libraries

Re: author names in .c files

2010-09-14 Thread Dustin J. Mitchell
On Tue, Sep 14, 2010 at 6:03 AM, Bruno Haible wrote: > You should be able to feel reward by your name in a file that you wrote. I don't have any feelings one way or the other on the application of this principle to gnulib, but I thought I'd add two points to this particular question all the same.

Re: [PATCH] getopt: handle POSIXLY_CORRECT set but not exported

2010-09-07 Thread Dustin J. Mitchell
On Tue, Sep 7, 2010 at 4:58 PM, Eric Blake wrote: > In complete patch form.  I'll be pushing this soon, after more > testing completes. This looks great, and works for me. Thanks! Dustin -- Open Source Storage Engineer http://www.zmanda.com

Re: POSIXLY_CORRECT not correctly unset in getopt.m4?

2010-09-07 Thread Dustin J. Mitchell
On Tue, Sep 7, 2010 at 1:10 PM, Eric Blake wrote: > By the way, you should report this as a bug in curl-config; it should be > calling: > > pkg-config --libs libcurl > > to be safe to things like POSIXLY_CORRECT. It's already fixed in newer versions (it doesn't call pkg-config at all anymore). B

Re: POSIXLY_CORRECT not correctly unset in getopt.m4?

2010-09-07 Thread Dustin J. Mitchell
On Tue, Sep 7, 2010 at 10:17 AM, Eric Blake wrote: >> I explained in the first email: at the beginning of the macro, > > Which macro?  You didn't mention that in the first email. Oops, sorry! gl_GETOPT_CHECK_HEADERS > Yes, /bin/sh has two namespaces - exported vs. locally-set variables, but > t

Re: POSIXLY_CORRECT not correctly unset in getopt.m4?

2010-09-07 Thread Dustin J. Mitchell
On Tue, Sep 7, 2010 at 9:16 AM, Eric Blake wrote: > Thanks for the report.  However, I fail to see how getopt.m4 sets > POSIXLY_CORRECT in perpetuity, because it is immediately followed by > AS_UNSET if it was determined that POSIXLY_CORRECT was not set prior to the > test.  While I appreciate the

Re: getopt configure check fails in linux

2010-09-06 Thread Dustin J. Mitchell
On Mon, Sep 6, 2010 at 3:46 PM, Lorenzo Bettini wrote: > (indeed, this way, the gnulib version of getopt is used, instead of GNU libc > version) Is this related to the getopt bug I reported earlier? Dustin -- Open Source Storage Engineer http://www.zmanda.com

Re: POSIXLY_CORRECT not correctly unset in getopt.m4?

2010-09-05 Thread Dustin J. Mitchell
On Sun, Sep 5, 2010 at 10:42 AM, Dustin J. Mitchell wrote: > I re-updated my gnulib repository, and I don't see any changes to this > file, so I'm assuming that the bug is still present.  I will look for > a fix and send a patch, but I thought I would poll for corrobora

POSIXLY_CORRECT not correctly unset in getopt.m4?

2010-09-05 Thread Dustin J. Mitchell
I just had a very long chase for a new build error that began after a recent gnulib upgrade. Briefly, the symptoms were that an invocation of curl-config --libs was returning nothing when run by configure on systems with older curls. curl-config is a shell script, which calls pkg-config libcu

socklen_t on HP/UX

2008-05-20 Thread Dustin J. Mitchell
As you probably know, on HP/UX, accept, getpeername, et al. take (.., int *addrlen), not (.., socklen_t *addrlen) unless _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED are defined. However, if these macros are not defined, socklen_t is still defined. This means that the test in socklen.m4 doesn't have

Re: syntax error in m4/socklen.m4

2008-04-09 Thread Dustin J. Mitchell
On Wed, Apr 9, 2008 at 5:45 PM, Bruno Haible <[EMAIL PROTECTED]> wrote: > It's not only the indented #include which fails. The compiler message > "error 1705: Function prototypes are an ANSI feature." clearly indicates > that many more errors are to be expected, because the compiler is not even

syntax error in m4/socklen.m4

2008-04-09 Thread Dustin J. Mitchell
A user is building Amanda on HPUX, and ran into a compiler error: | /* end confdefs.h. */ | #include | #include | | int getpeername (int, void *, long int *); | int | main () | { | long int len; | getpeername (0, 0, &len); | ; | return 0; | } config