From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] 32 or 64 bits file offsets?
Date: Mon, 9 Dec 2013 15:13:10 +0100 [thread overview]
Message-ID: <20131209141310.GB2415@pengutronix.de> (raw)
In-Reply-To: <loom.20131208T090536-151@post.gmane.org>
On Sun, Dec 08, 2013 at 08:14:37AM +0000, Felix Mellmann wrote:
> Bernhard Walle <bernhard@...> writes:
> > No, not in general. This flag "just" sets --enable-lfs or
> > --enable-largefile as configure option for programs that support it.
> > Grep for 'PTXCONF_GLOBAL_LARGE_FILE' and 'GLOBAL_LARGE_FILE_OPTION'.
> >
> > It doesn't set compile flags directly.
>
> D'oh! But your clue was the right direction.
> The problem lies in how apr (Apache Portable Runtime) detects how to use
> large file support. On the one hand side it detects, that additional CFLAGS
> are not needed on the other hand side it detects, that off_t should be
> redefined as off64_t (which is ok for my x86-64 machine).
>
> As I'm using apr-1.4.8 instead of current shipped apr-0.9.20, I'm going to
> investigate, if this happens also to apr-0.9.20.
> If so, I would post a patch. This patch should include selectable large file
> support as well?
Don't add an extra option. Just use PTXCONF_GLOBAL_LARGE_FILE.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-12-09 14:13 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 [this message]
2013-12-26 19:19 ` Felix Mellmann
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=20131209141310.GB2415@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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