Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Cc: bugs-bitbucket@netlabs.develooper.com, dev@perl.apache.org,
    Nick Ing-Simmons <nick.ing-simmons@elixent.com>, Nick Ing-Simmons   <
 nick@ing-simmons.net>, perl5-porters@perl.org
Subject: Re: [perl #22163] perlio callback functions get their args mangled
In-Reply-To: <3EBF3747.8000109@stason.org> from Stas Bekman on Mon,
    12 May 2003 15:55:19 +1000
References: <rt-22163-57019.13.823672351236@bugs6.perl.org>
   <20030510220404.2454.6@
   bactrian.ni-s.u-net.com>   <3EBE05D3.1060909@stason.org> <20030511103046.
    1946.3@bactrian.elixent.com>   <3EBE303C.3060606@stason.org>   <
 20030511160440.1660.2@bactrian.ni-s.u-net.com>   <3EBF3747.8000109@stason.
 org>
Content-Type: text/plain; charset="UTF-8"
To: stas@stason.org
Message-Id: <20030512080008.1864.5@bactrian.elixent.com>
Date: Mon, 12 May 2003 09:00:08 +0100
Sender: Nick Ing-Simmons <nick.ing-simmons@elixent.com>
From: Nick Ing-Simmons <nick.ing-simmons@elixent.com>
Reply-To: Nick Ing-Simmons <nick.ing-simmons@elixent.com>

Stas Bekman <stas@stason.org> writes:
>
>Thanks Nick.
>
>After confirming that using an explicit 'long long int offset' solves the 
>problem (for the given setup):
>
>static IV PerlIOAPR_seek(pTHX_ PerlIO *f, long long int offset, int whence)
>
>I went to figure out where the difference comes from. And then I've found that 
>mod_perl rips off the flags '-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' when 
>building mod_perl objects, since Apache 2.0 (to be exact libapr) always builds 
>without largefiles support (at least on linux). The two are binary 
>incompatible. Sigh :(
>
>Looks like it happens to work for me, if I build only apr_perlio.c with 
>'-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', since that's the only place 
>where we use Off_t. I don't know whether it'll work on other platforms.
>
>Currently, if you want to use APR::PerlIO's seek function, with offset 
>different from 0, you have to rebuild perl without uselargefiles, which is far 
>from being an acceptable solution.

Does this make the ticket "resolved" - as far as perl is concerned?


>
-- 
Nick Ing-Simmons
http://www.ni-s.u-net.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org