FS#32901 - [ntfs-3g] FILE_OFFSET_BITS

Attached to Project: Arch Linux
Opened by Evaggelos Balaskas (ebal) - Thursday, 29 November 2012, 16:35 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 01 December 2012, 14:33 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

the existing PKGBUILD doesnt have support for large files.

at line 21 (just before ./configure)
you could add

CFLAGS=" -D_FILE_OFFSET_BITS=64"

to enable this feature

Additional info:
* package version(s)

2012.1.15

* config and/or log files etc.

checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
configure: creating ./config.status
config.status: creating Makefile

Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 01 December 2012, 14:33 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Original report is not a bug. Unrelated bug is fixed in SVN without a release.
Comment by Dave Reisner (falconindy) - Saturday, 01 December 2012, 01:19 GMT
You've neglected to mention the architecture here, and I suspect it's x86_64 -- which means that off_t is already 64bit. The flag is only needed for 32bit where configure reports...

checking for _FILE_OFFSET_BITS value needed for large files... 64

Is there an actual problem here, or are you just raising alarm based on the configure output?
Comment by Evaggelos Balaskas (ebal) - Saturday, 01 December 2012, 10:17 GMT
Yes my architecture is x86_64 [ -march=x86-64 ], sorry for not posting that.
No, i dont believe there is an actual problem with that.

although i am trying to resolve this: https://bbs.archlinux.org/viewtopic.php?id=153915
cause i cant build libguestfs (the existence of /lib from ntfs-3g is in conflict with glibc symbolic link /lib)

all of my outputs (makepkg on PKGBUILD from abs) are returning the below lines (at configure)

checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
configure: creating ./config.status


after a lot of research and a gazillion tests (PKGBUILD and ntfs-3g source), i think that i now understand why this is happening.

Reading also fuse code i've noticed that -D_FILE_OFFSET_BITS=64 is in fact a CFLAG that is being added to ntfs-3g compilation from fuse, when ntfs-3g is trying to compile binaries & libraries based on fuse libs.


I know that it does offer much, but it doesnt hurt also to add enable-largefile at PKGBUILD with the CFLAG for _FILE_OFFSET_BITS, something like this:

CFLAGS=" -D_FILE_OFFSET_BITS=64"
./configure \
--prefix=/usr \
--enable-largefile \
--with-fuse=external \
--disable-static \
--enable-posix-acls \
--disable-ldconfig \
--mandir=/usr/share/man


I respect your work and your i value your opinion.
You do know better these staff than me.

So if you believe that this Feature Request doesnt offer much, i can live with that result.

if have can spare a moment, take a quick look at id=153915 on forum.
related to this (ntfs-3g PKGBUILD).

thank you
Comment by Dave Reisner (falconindy) - Saturday, 01 December 2012, 14:32 GMT
> So if you believe that this Feature Request doesnt offer much, i can live with that result.
Right, as I mentioned, it's a no-op on 64-bit, and the configure script already does the right thing on 32-bit, adding the flag.

> although i am trying to resolve this: https://bbs.archlinux.org/viewtopic.php?id=153915
I've fixed this in SVN. ABS will update tonight with the change, or you can pick it from trunk.

Loading...