[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


On Sun, Nov 30, 2003 at 09:18:28PM +1100, Brian May wrote:
> I am trying to get long file names to work in dar (uptodate
> debian/unstable).
> So far, I don't think I have had any success (at least I
> don't see any evidence...).
> I have traced it to the AC_SYS_LARGEFILE autoconf macro (autoconf 2.57),
> it outputs the following in config.log:
> What is going on here? Any ideas?

hmm, the coresponding code in autoconf/specific.m4 is:

|  AC_CACHE_CHECK([for special C compiler options needed for large files],
|    ac_cv_sys_largefile_CC,
|    [ac_cv_sys_largefile_CC=no
|     if test "$GCC" != yes; then
|       ac_save_CC=$CC
|       while :; do
|         # IRIX 6.2 and later do not support large files by default,
|         # so use the C compiler's -n32 option if that helps.
|         AC_COMPILE_IFELSE([], [break])
|         CC="$CC -n32"
|         AC_COMPILE_IFELSE([], [ac_cv_sys_largefile_CC=' -n32'; break])
|         break
|       done
|       CC=$ac_save_CC
|       rm -f conftest.$ac_ext
|    fi])

(_AC_SYS_LARGEFILE_TEST_INCLUDES includes the failing code), it is never
checked if it finds a gcc. maybe your forget to call AC_PROG_CC before?


> Is this a result of a buggy AC_SYS_LARGEFILE macro???

no, the macro is okay.


No one wants war.
		-- Kirk, "Errand of Mercy", stardate 3201.7

Attachment: signature.asc
Description: Digital signature

Reply to: