Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
64-bit sparc instructions
- X-seq: zsh-workers 14447
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Paul Ackersviller <paulda@xxxxxxxxxxxxx>
- Subject: 64-bit sparc instructions
- Date: Wed, 23 May 2001 04:41:28 +0000
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <20010522200425.A9730@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20010522200425.A9730@xxxxxxxxxxxxxxxxxxxxxxxxx>
On May 22, 8:04pm, Paul Ackersviller wrote:
}
} [...] What does make a difference is simply generating default 32-bit
} sparc instructions. I'd negelected to mention that I was using Sun's
} compiler and 64-bit code. I suppose it's fair to blame this one on Sun.
Is that problem solved by the following?
On May 22, 2:32pm, Clint Adams wrote:
} Subject: Re: 4.0.1-pre-5 (solaris issues)
}
} > the 64-bit Forte compiler. Can you figure out what we need to be passing
} > as a compiler argument that we aren't, or whatever?
}
} LFS64_CFLAGS: -D_LARGEFILE64_SOURCE
} LFS_CFLAGS: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
}
} By replacing the latter with the former, the test [succeeds].
If so, can you identify a configure test we can use to decide when to
use LFS64_CFLAGS instead of LFS_CFLAGS ? (The existing test is in the
definition of zsh_LARGE_FILE_SUPPORT in aczsh.m4.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author