Kean Johnston wrote:
> Although I agree its a problem, which may well be addressed by changing
> the particular usage you encountered to an unambiguous type such as
> apr_uint32_t, I think the real error is in how you are compiling svn. If
> you have decided to use the Perl bindings then you should compile svn in
> the same approximate environment that Perl was compiled in. This
> includes subtle things like _FILE_OFFSET_BITS, as well as other things
> such as FD_SETSIZE or other nasty things that can trip you up if they
> are set to different values in different applications. Likewise things
> like threading.
Sorry, I am the one who noticed the problem, and I did exactly that. While
debugging this, I literally built _everything_ from the ground up, including
Perl, SWIG, Subversion, and the Perl bindings. If there is something special I
need to do at any point with _FILE_OFFSET_BITS, et al, then the build system
must be enhanced to do this, or else the bindings are useless to anyone not
running a pure-64bit environment.
It just so happens that Ben was developing with a 64bit pre-release version of
Mandrake, so he didn't see the problem. I'm using a 32bit distro (currently a
much more common environment), so although I can build Perl to use 64-bit ints,
I shouldn't have to unless I want to for some other reason. I will, in fact,
build a 64-bit aware Perl and see if that fixes it (as it should). But the
larger issue of relying on an off_t that is not consistent is still a problem
that needs solving.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 12 16:02:31 2004