[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Should 32-bit apps work with a 64-bit kernel?



Roger Leigh <rleigh@codelibre.net> writes:

> On Wed, Feb 25, 2009 at 04:16:53PM +0100, Goswin von Brederlow wrote:
>
>> Maybe we need a mass bug filing for programs not using 64bit file
>> offsets.
>
> I think that would be appropriate.  At this point, I can't see a
> valid reason for any package to not have LFS enabled.
>
>> Anyone up for hacking libc to always fail on the 32bit wrappers for
>> seek, stat, ...?
>
> Well, breaking old code might be considered bad.  This would break
> *all* binaries using the old 32-bit ABI.

This would just be on special systems where you want to detect bad
software by breaking it.

Instead of failing the 32-bit calls could also just log arg[0] on the
first use.

> Personally, I would prefer the glibc headers to just set the LFS
> macros to the 64 bit versions by default, so that rather than
> taking extra steps to enable LFS, LFS would be the default and you
> would then need to take extra steps to disable it.
>
> i.e. just default _FILE_OFFSET_BITS to 64 rather than 32.
>
> If someone really, really, wanted 32 bit file offsets, they could
> just set it back to 32 again.

I would like that too. But that would break all sources that just
assume 32bit. Sources that just copy off_t into an int or long, or
blksize_t, or any of the others. That is obviously broken but hard to
detect.

> Regards,
> Roger

MfG
        Goswin


Reply to: