zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Possible impact of RE: PATCH: large file support on SunOS 5
Date: Fri, 07 May 1999 12:08:30 +0200	[thread overview]
Message-ID: <9905071008.AA38229@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Andrej Borsenkow""'s message of "Fri, 07 May 1999 12:57:39 DFT." <006a01be9867$a8b43b70$21c9ca95@mow.siemens.ru>

"Andrej Borsenkow" wrote:
> The LFS_CFLAGS (or, for that matter, LFS64_CFLAGS) make the off_t and ino_t
> 64 bit long. Dunno about Solaris, but at least on our system they are of
> type "long long" and there is no standard portable way to print 64 bit
> integers (if sizeof(long) < 8). Our system is using %lld; Solaris is using
> %qd if I'm not wrong.

This will take a little work, but perhaps it's not so bad.  off_t is
checked for in configure.  It needs to be propagated where it occurs in the
sources, e.g. in an .st_size member, instead of being assigned to longs (I
don't think that happens much anyway, but I could be wrong).  For printing,
one of %lld or %qd will probably work; there's already a test for %qd in
the rlim_t test in configure, which can be made more general.  ino_t isn't
tested in configure so probably needs adding in the same way.

I already have several things to finish off, so maybe someone else will
feel like looking at this first (although maybe hell will freeze over while
I wait :-)).

> P.S. I am running zsh in LP64 mode for quite a long time. This is different,
> as in this case all of off_t, ino_t and long are 8 bytes, so nothing in the
> code changes. May be, if a system supports LP64 we should prefer it to LFS?

I have no idea how to do this.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-05-07 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-06 15:23 Peter Stephenson
1999-05-07  8:57 ` Possible impact of " Andrej Borsenkow
1999-05-07 10:08   ` Peter Stephenson [this message]
1999-05-07 10:55     ` Andrej Borsenkow

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9905071008.AA38229@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).