Re: frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Gary V. Vaughan
Hi Bruno, On 25 Jan 2008, at 10:50, Bruno Haible wrote: Gary V. Vaughan wrote: Can you run the test program mentioned in [2]? Sure: $ gcc -o testfrexpl testfrexpl.c $ ./testfrexpl -16384 0.5 ... checking whether frexpl works... yes Sorry, this makes no sense to me. The testfrexpl.c test

Re: frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Bruno Haible
Gary V. Vaughan wrote: > > Can you run the test program mentioned in [2]? > > Sure: > > $ gcc -o testfrexpl testfrexpl.c > $ ./testfrexpl > -16384 0.5 ... > checking whether frexpl works... yes Sorry, this makes no sense to me. The testfrexpl.c test is nearly literally contained in the "whether

Re: config.guess and $CC

2008-01-24 Thread Peter O'Gorman
Bruno Haible wrote: > Yes. And a new platform x86_64*darwin* has appeared. People who have > configure scripts that check only for known platforms obviously have to > make adjustments when new platforms appear. New platforms have been > appearing constantly for the past 15 years. I have a hard ti

Re: frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Peter O'Gorman
Gary V. Vaughan wrote: > I'm not passing any special flags, so whatever is standard for the apple > shipped > build of gcc on 10.5.1. I believe that is 64 bit mode, unless I'm just > falling > for the hype... 32 bit is the default, you have to either pass -m64 or -arch x86_64 to the compiler to g

Re: frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Gary V. Vaughan
On 25 Jan 2008, at 07:12, Bruno Haible wrote: Hi Gary, Hallo Bruno, Gary V. Vaughan wrote: ... upgrade my gnulib checkout and rebuild m4 HEAD against it. ... there are /\(still\|new\)/ frexpl bugs in gnulib on my intel MacBook: $ VERBOSE=1 make check TESTS='test-frexpl test-printf-frexpl

Re: frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Bruno Haible
Hi Gary, Gary V. Vaughan wrote: > ... upgrade my gnulib checkout and rebuild m4 HEAD against it. > ... there are /\(still\|new\)/ frexpl bugs in gnulib on my intel MacBook: > > $ VERBOSE=1 make check TESTS='test-frexpl test-printf-frexpl' > [[...]] > make check-TESTS > i:-16382 exp:-16384 > .../

Re: sockets

2008-01-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 1/24/2008 7:58 AM: | Since there weren't any other comments after close to a week, and the | 'sockets' module doesn't affect anyone that isn't strictly using it, I | have committed the patch below. | | + * tests/tes

Re: config.guess and $CC

2008-01-24 Thread Bruno Haible
Peter O'Gorman wrote: > I worry that changing this will break something. Is there any written documentation of config.*, except in the comments of config.guess and config.sub? I only see vague terms like "CPU types", "canonical", and such. No formal definitions in terms of ABI, of backward compati

Re: config.guess and $CC

2008-01-24 Thread Peter O'Gorman
Paul Eggert wrote: > Bruno Haible <[EMAIL PROTECTED]> writes: > >> On a bi-arch system (i.e. a system that can execute 32-bit mode binaries and >> 64-bit mode binaries), what is the expected behaviour of config.guess? >> Should it return different triplets for CC="gcc -m32" and CC="gcc -m64", >> o

isnanl problem on Solaris 8 with GCC 4.2.2

2008-01-24 Thread Paul Eggert
I ran into this problem when compiling coreutils 6.10 on Solaris 8 (sparc) with GCC 4.2.2: frexp.c: In function 'rpl_frexpl': frexp.c:63: warning: implicit declaration of function 'isnanl' vasnprintf.c: In function 'is_infinitel': vasnprintf.c:252: warning: implicit declaration of function 'isnanl

signbit glitch (coreutils 6.10, Solaris 8 sparc, GCC 4.2.2)

2008-01-24 Thread Paul Eggert
I ran into the following minor glitch when compiling coreutils 6.10 on Solaris 8 sparc with GCC 4.2.2: vasnprintf.c: In function 'vasnprintf': vasnprintf.c:2196: warning: implicit declaration of function 'signbit' Here is a patch to the gnulib signbit module to work around this problem: 2008-01-

Re: config.guess and $CC

2008-01-24 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > On a bi-arch system (i.e. a system that can execute 32-bit mode binaries and > 64-bit mode binaries), what is the expected behaviour of config.guess? > Should it return different triplets for CC="gcc -m32" and CC="gcc -m64", > or the same? My assumption

Re: (x)gethostname

2008-01-24 Thread Simon Josefsson
Brian Dessent <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: > >> 3) Is there any chance that the #define gethostname rpl_gethostname and >> replacement prototype of gethostname in gnulib's unistd.h will cause >> problems? Consider that gethostname in winsock2.h is declared with >> PASCAL c

Re: (x)gethostname

2008-01-24 Thread Brian Dessent
Simon Josefsson wrote: > 3) Is there any chance that the #define gethostname rpl_gethostname and > replacement prototype of gethostname in gnulib's unistd.h will cause > problems? Consider that gethostname in winsock2.h is declared with > PASCAL calling conventions, so the prototype is not the sa

Re: (x)gethostname

2008-01-24 Thread Simon Josefsson
Here is an updated patch to get gethostname working under MinGW. It uses the recent new gnulib module 'sockets'. The module works like this: If the gethostname function is not found on the system, it pulls in gethostname.c into the gnulib library, and defines gethostname to rpl_gethostname. rpl_

frexpl bugs remain on OS X 10.5 intel

2008-01-24 Thread Gary V. Vaughan
Hi Bruno, In preparation for some libtool patches against Eric's reports, I decided to upgrade my gnulib checkout and rebuild m4 HEAD against it.I'm on the opposite side of the planet to my ppc machine for the next few months, but there are /\(still\|new\)/ frexpl bugs in gnulib on my

Re: sockets

2008-01-24 Thread Brian Dessent
Simon Josefsson wrote: > Thanks for testing. I think the test "just happens" to fail under > cygwin, but as long as that is always consistent, I think that is fine. In a sense, HAVE_WINSOCK2_H=0 is in fact correct on Cygwin. Even though the header is available it's not correct to include it in

Re: sockets

2008-01-24 Thread Simon Josefsson
Brian Dessent <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: > >> continue to work under cygwin. Btw, could you quote the part from >> config.log which explains _why_ the m4 macro fails under cygwin? It >> isn't clear from the M4 check that it would fail under cygwin, but maybe >> it is ju

Re: (x)gethostname

2008-01-24 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: >> > And it is necessary to still override the function, in order to >> > WSAStartup before? >> >> No, this doesn't seem to be necessary, at least under Wine. > > I don't think that you can judge the behaviour of Windows by testing on > Wine. You know that

Re: sockets

2008-01-24 Thread Brian Dessent
Simon Josefsson wrote: > continue to work under cygwin. Btw, could you quote the part from > config.log which explains _why_ the m4 macro fails under cygwin? It > isn't clear from the M4 check that it would fail under cygwin, but maybe > it is just my lack of knowledge with cygwin. Still, if it

Re: sockets

2008-01-24 Thread Simon Josefsson
Eric Blake <[EMAIL PROTECTED]> writes: > According to Simon Josefsson on 1/18/2008 7:45 AM: > | One thing worries me though; cygwin. I don't know if this is needed on > | cygwin. I would expect the answer is no? The m4 check should fail on > | cygwin, but I'm not sure it does right now. > > You