mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Felix Mellmann <felix.mellmann@googlemail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] 32 or 64 bits file offsets?
Date: Thu, 26 Dec 2013 19:19:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20131226T200810-352@post.gmane.org> (raw)
In-Reply-To: <20131209141310.GB2415@pengutronix.de>

Michael Olbrich <m.olbrich@...> writes:

> 
> 
> Don't add an extra option. Just use PTXCONF_GLOBAL_LARGE_FILE.
> 
> Michael
> 

At last, I didn't investigate on how to enable proper large file support for
Apache Portable Runtime (apr), but I'd like to suggest a patch which will
override sizeof(off_t) to be in line with sizeof(size_t). In case of a 64
bit cross compiling host, sizeof(off_t) will lead to a value of 8 instead of 4.

In my particular case, using subversion (svn) fails with unexpected errors.
Since APR is used by apache webserver as well, modifing sizeof(off_t) will
also have an effect on apache but this is untested.

The maintainers may add my address and name as signed-off.

Regards,
Felix

diff -urdN ptxdist-2013.12.0/rules/apr.make
ptxdist-2013.12.0.debugged/rules/apr.make
--- ptxdist-2013.12.0/rules/apr.make    2013-12-18 10:48:42.000000000 +0100
+++ ptxdist-2013.12.0.debugged/rules/apr.make   2013-12-26
20:05:11.205107001 +0100
@@ -32,6 +32,7 @@
 APR_CONF_ENV := \
        $(CROSS_ENV) \
        ac_cv_file__dev_zero=yes \
+       ac_cv_sizeof_off_t=4 \
        ac_cv_sizeof_size_t=4 \
        ac_cv_sizeof_ssize_t=4 \
        ac_cv_struct_rlimit=yes \




-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2013-12-26 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 16:47 Felix Mellmann
2013-12-07 18:40 ` Bernhard Walle
2013-12-08  8:14   ` Felix Mellmann
2013-12-09 14:13     ` Michael Olbrich
2013-12-26 19:19       ` Felix Mellmann [this message]

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=loom.20131226T200810-352@post.gmane.org \
    --to=felix.mellmann@googlemail.com \
    --cc=ptxdist@pengutronix.de \
    /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