Hi Neil, That sounds like an excellent solution.Attached is my config.guess file. (Its just the one from the distribution with no changes).
Roger
config.guess
Description: Binary data
On 23/01/2008, at 9:10 AM, Neil Jerram wrote:
Roger Mc Murtrie <[EMAIL PROTECTED]> writes:This might help: http://developer.apple.com/documentation/Darwin/Conceptual/64bitPorting RogerThank you, that was helpful. Amongst a lot of detail, one of its messages was that most system call APIs (i.e. the traditional ones _without_ "64" in their names) have been 64-bit-capable for a long time now, and so in many cases a developer need take no action to get 64-bit capability. That feels consistent with off_t being 64-bit. In that light, and also because a Guile without LARGEFILE64 support is surely better than no Guile at all, I think we should address this problem for the Mac OSes (and also HP-UX, per [1]), by adding a --disable-64-calls option to ./configure, whose effect will be to prevent Guile from trying to use xxx64() sys and library calls. [1] http://www.nabble.com/Building-guile-1.8.2-on-hpux-td13106681.html That way, you'll at least get 32 bit operation working; you'll probably get a large subset of 64 bit operation working (via the traditional non-"64" API); and any remaining deltas can be worked on by someone in the future with time to invest. If you could tell us what ./config.guess says on your Mac systems, we can make --disable-64-calls the default for those systems, so you don't need to remember this when 1.8.4 comes out. For all other systems, --enable-64-calls will be the default, which means no change to existing behaviour. How does that sound? (Roger, and anyone else please!) Regards, Neil
