If I have a library which is built for LFS and uses stdio, and the
interface to that library requires passing an open FILE*, does the
app using that library need to be built with the same LFS flags?

ie, if I build the library with LFS support, and use it in my
non-LFS app, will it work but just not really have LFS support
(since the file was opened non-LFS)?

If the interface required stuff like off_t's and such, it's obvious
this wouldn't work correct because the size of those args would
be different.  (eg libelf.h)

-frank

[ Post a follow-up to this message ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Cusack wrote:
> If I have a library which is built for LFS and uses stdio, and the
> interface to that library requires passing an open FILE*, does the
> app using that library need to be built with the same LFS flags?
>
> ie, if I build the library with LFS support, and use it in my
> non-LFS app, will it work but just not really have LFS support
> (since the file was opened non-LFS)?
>
> If the interface required stuff like off_t's and such, it's obvious
> this wouldn't work correct because the size of those args would
> be different.  (eg libelf.h)
>
> -frank

LFS = largefile support, right?

I'd say this is implementation specific behavior, as POSIX doesn't say
anything about largefile support. Concerning Solaris, I'd say that the
descriptors are the same. But a short look at the OpenSolaris source
code reviled that an open64 is actually different to open by adding the
flag FOFFMAX. The descriptor are the same, as the same underlying
function is called.

If you want to take a look yourself, go here:
http://cvs.opensolaris.org/source/x.../syscall/open.c

HTH,
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEHHmh6U+hp8PKQZIRAo9MAKDUW/ZZZiAD8hC6/hRahD9hUXPAKgCfa8AF
VnUx1lI5qN4KnS7c/rGOVqg=
=Vaio
-----END PGP SIGNATURE-----

[ Post a follow-up to this message ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Cusack wrote:
> If I have a library which is built for LFS and uses stdio, and the
> interface to that library requires passing an open FILE*, does the
> app using that library need to be built with the same LFS flags?
>
> ie, if I build the library with LFS support, and use it in my
> non-LFS app, will it work but just not really have LFS support
> (since the file was opened non-LFS)?
>
> If the interface required stuff like off_t's and such, it's obvious
> this wouldn't work correct because the size of those args would
> be different.  (eg libelf.h)
>
> -frank

LFS = largefile support, right?

I'd say this is implementation specific behavior, as POSIX doesn't say
anything about largefile support. Concerning Solaris, I'd say that the
descriptors are the same. But a short look at the OpenSolaris source
code reviled that an open64 is actually different to open by adding the
flag FOFFMAX. The descriptor are the same, as the same underlying
function is called.

If you want to take a look yourself, go here:
http://cvs.opensolaris.org/source/x.../syscall/open.c

HTH,
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEHHnT6U+hp8PKQZIRAgwiAJ9B/fbrkGoUyqPWQG+Gd+zCJbA3dgCeJEJM
mgDR5QVmgOrX1xZq2bszejg=
=ylck
-----END PGP SIGNATURE-----

[ Post a follow-up to this message ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Cusack wrote:
> If I have a library which is built for LFS and uses stdio, and the
> interface to that library requires passing an open FILE*, does the
> app using that library need to be built with the same LFS flags?
>
> ie, if I build the library with LFS support, and use it in my
> non-LFS app, will it work but just not really have LFS support
> (since the file was opened non-LFS)?
>
> If the interface required stuff like off_t's and such, it's obvious
> this wouldn't work correct because the size of those args would
> be different.  (eg libelf.h)
>
> -frank

LFS = largefile support, right?

I'd say this is implementation specific behavior, as POSIX doesn't say
anything about largefile support. Concerning Solaris, I'd say that the
descriptors are the same. But a short look at the OpenSolaris source
code reviled that an open64 is actually different to open by adding the
flag FOFFMAX. The descriptor are the same, as the same underlying
function is called.

If you want to take a look yourself, go here:
http://cvs.opensolaris.org/source/x.../syscall/open.c

HTH,
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iD8DBQFEHHpf6U+hp8PKQZIRAsFzAKCXmMx7Yac7
KwCkfDCen029YW83pACeLQbs
H/OsK9RTukoJsyB4f1ArPVw=
=oxEg
-----END PGP SIGNATURE-----

[ Post a follow-up to this message ]

On 2006-03-18, Thomas Maier-Komor <maierkom@lpr.e-technik.tu-muenchen.de> wrote:
>
> Frank Cusack wrote: 
>
> LFS = largefile support, right?
>
> I'd say this is implementation specific behavior, as POSIX doesn't say
> anything about largefile support.

Not quite... I don't know if POSIX proper mentions it, but SUS calls
fseeko/ftello "large file support".

[ Post a follow-up to this message ]

Thomas Maier-Komor <maierkom@lpr.e-technik.tu-muenchen.de> wrote:
>
> LFS = largefile support, right?
>

Duhh! I read it as "Linux From Scratch". Ha ha!

--
Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Telephone: (0121) 247 1596
International: 0044 121 247 1596

Email: markhobley at hotpop dot donottypethisbit com

http://markhobley.yi.org/

[ Post a follow-up to this message ]

Mark Hobley wrote:
> Thomas Maier-Komor <maierkom@lpr.e-technik.tu-muenchen.de> wrote: 
>
> Duhh! I read it as "Linux From Scratch". Ha ha!

Well, obviously it should be "loopback file system", since we are
talking about I/O...

- Logan

[ Post a follow-up to this message ]

On 2006-03-21, Logan Shaw <lshaw-usenet@austin.rr.com> wrote:
> Mark Hobley wrote: 
>
> Well, obviously it should be "loopback file system", since we are
> talking about I/O...

TLA's suck.

[ Post a follow-up to this message ]