[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Present-But-Cannot-Be-Compiled bug
From: |
Eric Blake |
Subject: |
Re: Present-But-Cannot-Be-Compiled bug |
Date: |
Fri, 16 Oct 2009 17:03:35 -0600 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Please don't top-post on technical lists.
According to Jorma Karvonen on 10/16/2009 12:59 PM:
> checking whether gettimeofday clobbers localtime buffer... yes
> checking sys/timeb.h usability... no
> checking sys/timeb.h presence... yes
> configure: WARNING: sys/timeb.h: present but cannot be compiled
> configure: WARNING: sys/timeb.h: check for missing prerequisite headers?
> configure: WARNING: sys/timeb.h: see the Autoconf documentation
> configure: WARNING: sys/timeb.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/timeb.h: proceeding with the compiler's result
Looking more at your config.log, I see:
> configure:14781: checking sys/timeb.h usability
> configure:14781: gcc -std=gnu99 -c -g -O2 conftest.c >&5
> In file included from /usr/include/stdio.h:34,
> from conftest.c:136:
> /usr/local/lib/gcc/i686-pc-linux-gnu/4.3.4/include/stddef.h:214: error:
> duplicate 'unsigned'
> /usr/local/lib/gcc/i686-pc-linux-gnu/4.3.4/include/stddef.h:214: error: two
> or more data types in declaration specifiers
> In file included from /usr/include/inttypes.h:28,
> from conftest.c:161:
> /usr/include/stdint.h:139: error: 'long long long' is too long for GCC
> /usr/include/stdint.h:139: error: 'long long long' is too long for GCC
What is at line 214 of that stddef.h file, and line 139 of stdint.h? It
might be a macro being previously (but incorrectly) redefined by
configure? This may also be a case where your system headers came from a
different version of glibc and gcc than what you are now using, so that
there are some unexpected conflicts due to newer semantics of an updated
compiler.
>
> I will email config.log to you only Eric with my next email.
Sorry - I saw that mail before this one, so my response to that mail was
lacking this context. This mail certainly fills in some of the gaps that
I wasn't seeing in the other one.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrY+8cACgkQ84KuGfSFAYC7xQCgicGgZIRd6ZhD3nbwlq9fFz4z
YIAAoJbRAho6F84KFWC5h/632bmypV8V
=GrZ4
-----END PGP SIGNATURE-----