Hi all. I'm trying to compile 2.0.0beta5 on my Solaris 2.6 host, using
gcc-2.7.2.3, and configure is failing:
checking configure summary
ERROR: No disk free routine!
configure: error: summary failure. Aborting config
This apparently comes from the following in ./source/tests/summary.c:
#if !(defined(STAT_STATVFS) || defined(STAT_STATVFS64) ||
defined(STAT_STATFS3_OSF1) || defined(STAT_STATFS2_BSIZE) ||
defined(STAT_STATFS4) || defined(STAT_STATFS2_FSIZE) ||
defined(STAT_STATFS2_FS_DATA))
printf("ERROR: No disk free routine!\n");
exit(1);
#endif
Thanks for any ideas. Please cc me, as I'm subscribed to the digest.
Thanks,
Dave
> Hi all. I'm trying to compile 2.0.0beta5 on my Solaris 2.6 host, using > gcc-2.7.2.3, and configure is failing: > > checking configure summary > ERROR: No disk free routine! > configure: error: summary failure. Aborting configYep, fails for me also with gcc-2.7.2.1, but not with gcc 2.8. Or perhaps not with a gcc that is built for Solaris 2.6 (as opposed to trying to use a gcc built for, say Solaris 2.5, on your 2.6 system)????? At any rate, this patch will get it to configure properly, but isn't deemed to be the correct way to fix the seemingly brokeness for non gcc-2.8 compilers. *** configure.orig Wed Dec 30 20:36:48 1998 --- configure Thu Jan 7 00:45:43 1999 *************** *** 1199,1205 **** *solaris*) case `uname -r` in 5.6*|5.7*) ! CPPFLAGS="$CPPFLAGS -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" ;; esac ;; --- 1199,1205 ---- *solaris*) case `uname -r` in 5.6*|5.7*) ! CPPFLAGS="$CPPFLAGS -D_LARGEFILE64_SOURCE" ;; esac ;; Dan Eischen eischen@vigrid.com
> > checking configure summary > > ERROR: No disk free routine! > > configure: error: summary failure. Aborting config > > Yep, fails for me also with gcc-2.7.2.1, but not with gcc 2.8. > Or perhaps not with a gcc that is built for Solaris 2.6 (as > opposed to trying to use a gcc built for, say Solaris 2.5, > on your 2.6 system)?????The gcc I was using was in fact compiled for 2.6. Should I upgrade to 2.8? From what I understand, there is problems with 2.8, and most people are still using 2.7.2.3, or egcs? Where can I find egcs? Thanks, Dave
> The gcc I was using was in fact compiled for 2.6. Should I upgrade to > 2.8? From what I understand, there is problems with 2.8, and most people > are still using 2.7.2.3, or egcs? Where can I find egcs?Just patch configure. I can't see a release of Samba forcing Solaris 2.6 installations to use one specific version of gcc. Of course, I don't speak for the samba developers... Dan Eischen eischen@vigrid.com
Daniel Eischen <eischen@vigrid.com> wrote: | At any rate, this patch will get it to configure properly, | but isn't deemed to be the correct way to fix the seemingly | brokeness for non gcc-2.8 compilers. Changing CPPFLAGS="$CPPFLAGS -D_LARGEFILE_SOURCE to CPPFLAGS="$CPPFLAGS -D_LARGEFILE64_SOURCE" indeed fixes the gcc 2.7.x compilers, **and is harmless**. Alas, it's different from both my and Sun's reccomendations, in which we're picky about how to implement large files. I strongly reccomend the newer compilers, as they allow Samba to do 64 bits the pedantic way (:-)) --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | http://java.science.yorku.ca/~davecb Work: (905) 477-0437 Home: (416) 223-8968 Email: davecb@canada.sun.com