From: Neil Jerram <neil@ossau.uklinux.net>
To: Roger Mc Murtrie <rogermc@iinet.net.au>
Cc: bug-guile@gnu.org
Subject: Re: guile-1.8.3 Intel Mac Leopard compilation fails due to no off64_t
Date: Thu, 10 Jan 2008 18:30:39 +0000 [thread overview]
Message-ID: <87prw9354g.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <CC1EEE5D-CA55-4CC3-9862-75A0D958E379@iinet.net.au> (Roger Mc Murtrie's message of "Wed, 9 Jan 2008 14:00:05 +1100")
Roger Mc Murtrie <rogermc@iinet.net.au> writes:
> Compilation of guile-1.8.3 fports.c failed as the stat64 package in
> Mac OSX Leopard does not seem to declare off64_t.
> only off_t seems to be declared.
> To get fports.c to compile:
> In _scm.h I changed
> #define off_t_or_off64_t CHOOSE_LARGEFILE(off_t,off64_t)
> to
> #define off_t_or_off64_t off_t
> and in fports.c fport_seek I changed
> off64_t to off_t
So is this OS's off_t actually 64-bit, or is it 32-bit?
Thanks,
Neil
next prev parent reply other threads:[~2008-01-10 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 3:00 guile-1.8.3 Intel Mac Leopard compilation fails due to no off64_t Roger Mc Murtrie
2008-01-09 3:09 ` Roger Mc Murtrie
2008-01-10 18:40 ` Neil Jerram
2008-01-10 18:30 ` Neil Jerram [this message]
[not found] ` <881AD488-9F97-4F0D-B078-BEBD5BB684B8@iinet.net.au>
2008-01-10 22:53 ` Neil Jerram
2008-01-10 23:53 ` Roger Mc Murtrie
2008-01-10 23:59 ` Roger Mc Murtrie
[not found] ` <Pine.LNX.4.62.0801110725270.6071@ashmore.csail.mit.edu>
[not found] ` <Pine.LNX.4.62.0801110754040.6071@ashmore.csail.mit.edu>
2008-01-11 19:26 ` Make problem Mac OS X Roger Mc Murtrie
[not found] ` <Pine.LNX.4.62.0801120948290.23339@ashmore.csail.mit.edu>
2008-01-12 23:18 ` Roger Mc Murtrie
2008-01-21 22:47 ` Neil Jerram
2008-01-22 22:10 ` guile-1.8.3 Intel Mac Leopard compilation fails due to no off64_t Neil Jerram
2008-01-22 22:57 ` Roger Mc Murtrie
2008-01-22 23:09 ` Neil Jerram
2008-01-22 23:42 ` Roger Mc Murtrie
2008-01-30 23:08 ` Neil Jerram
2008-01-30 23:10 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prw9354g.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=rogermc@iinet.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).