andy dougherty uloqorhilafayetteedu mon 22 oct 2007 rafael garciasuarez wrote atoll warning freebsd also bit worrying doesnt seem harmful need tuits borrow mine patch mostly selfexplanatory think even work perlcurrentcflagssh 20070814 025927000000000 0400 perlandycflagssh 20071022 120257000000000 0400 10417 10432 struct compared gcc releases flat integer strlen iv iv off_t t0a 2 strlen t0b 3 int t0c t0a t0b return 0 freebsd 62 probably releases duse64bitint perl use atoll3 however declaration hidden force compiler use stdc89 mode iv atol42 return t0c iv 42 0 1 try avoid unused warnings __eot__ stdflags gcc warning options gcc warning options build list options work note problems may show combinations options eg warning might show wall ansi either one individually todo ponder whether migrate back configure hints files tweak also paranoid whether results weve deduced configure especially things like long long c89 still valid add flags like stdc89 case gccversion 12 gcc versions 1 gasp 2 good 1248 1399 case ccflags opt skip already rm f _cflags_exe case cc cflags opt _cflagsc _cflags_exe 21 case cc cflags warn opt _cflagsc _cflags_exe 21 unrecognized implicit declaration something useful hidden invalid valid c test x _cflags_exe 1586 17418 warnecho warnsed spedantic esac similarly since long long isnt part c89 freebsd 62 headers dont declare atoll stdc89 need general insisting stdc89 inconsistent insisting using long long drop stdc89 ansi well using long long main integral type case ivtype long long ccflagsecho ccflagssed e spedantic e sstdc89 e sansi warnecho warnsed e spedantic e sansi stdflagsecho warnsed e sstdc89 esac fi using certain features like gcc statement expressions requires knowing whether pedantic specified andy dougherty uloqorhilafayetteedu wed 06 aug 2008 165859 0400 patch freebsd atoll warning code freeze