Ralf Wildenhues schrieb am Sonntag, dem 03. Dezember 2006:
> On Sun, Dec 03, 2006 at 01:41:44AM +0100, Peter Palfrader wrote:
> >
> >Starting with 2.61-1 autoconf's AC_FUNC_FSEEKO no longer makes fseeko() or
> >ftello() visible on sid. It still worked with 2.60a4-1.
>
> Please post the parts of config.log that belong to the fseeko tests
> (both old and new).
---------------------------------------------------------
old:
---------------------------------------------------------
[..]
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for _LARGEFILE_SOURCE value needed for large files... 1
checking for fseeko... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for _LARGE_FILES value needed for large files... no
checking whether to enable maintainer-specific portions of Makefiles... no
configure: creating ./config.status
[..]
configure:4269: checking for stdio.h
configure:4277: result: yes
configure:4295: checking for _LARGEFILE_SOURCE value needed for large files
configure:4323: gcc -c -g -O2 conftest.c >&5
conftest.c: In function 'main':
conftest.c:26: error: 'fseeko' undeclared (first use in this function)
conftest.c:26: error: (Each undeclared identifier is reported only once
conftest.c:26: error: for each function it appears in.)
configure:4329: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "programm"
| #define VERSION "0.0.1"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STDIO_H 1
| /* end confdefs.h. */
| #include <stdio.h>
| int
| main ()
| {
| return !fseeko;
| ;
| return 0;
| }
configure:4382: gcc -c -g -O2 conftest.c >&5
conftest.c: In function 'main':
conftest.c:27: warning: the address of 'fseeko', will always evaluate as 'true'
configure:4388: $? = 0
configure:4395: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:4398: $? = 0
configure:4405: test -s conftest.o
configure:4408: $? = 0
configure:4422: result: 1
configure:4436: checking for fseeko
configure:4462: gcc -o conftest -g -O2 conftest.c >&5
conftest.c: In function 'main':
conftest.c:27: warning: the address of 'fseeko', will always evaluate as 'true'
configure:4468: $? = 0
configure:4475: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:4478: $? = 0
configure:4485: test -s conftest
configure:4488: $? = 0
configure:4501: result: yes
configure:4518: checking for special C compiler options needed for large files
configure:4645: result: no
configure:4651: checking for _FILE_OFFSET_BITS value needed for large files
configure:4687: gcc -c -g -O2 conftest.c >&5
configure:4693: $? = 0
[..]
---------------------------------------------------------
new:
---------------------------------------------------------
[..]
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether to enable maintainer-specific portions of Makefiles... no
configure: creating ./config.status
[EMAIL PROTECTED]:/tmp/ac261# grep -i fseek config.log
#define HAVE_FSEEKO 1
[EMAIL PROTECTED]:/tmp/ac261#
I'll send the complete logs and configure scripts to the BTS (in a mail to
-quiet). They will be available at http://bugs.debian.org/401377 shortly.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
