zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
	"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Possible impact of RE: PATCH: large file support on SunOS 5
Date: Fri, 7 May 1999 12:57:39 +0400	[thread overview]
Message-ID: <006a01be9867$a8b43b70$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <9905061523.AA21545@ibmth.df.unipi.it>


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 has impact at least on stat module (and possibly others) that print
file size and inode. It has possible impact on zftp module that has to
correctly count transferred bytes (and our ftp is able to transfer more than
2GB - I'd expect it from zftp as well).  And may be some others.

What I want to say - it is not enough to simply compile a program with
correct flags - program must be able to correctly handle large files.

Can anybody who knows zsh internals better confirm, that zsh is really able
to handle large files?

/andrej

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?


  reply	other threads:[~1999-05-07  8:58 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 ` Andrej Borsenkow [this message]
1999-05-07 10:08   ` Possible impact of " Peter Stephenson
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='006a01be9867$a8b43b70$21c9ca95@mow.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=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).