Your message dated Tue, 23 May 2023 19:33:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#1032958: rsyslog: Enable Large File Support (LFS)
has caused the Debian Bug report #1032958,
regarding rsyslog: Enable Large File Support (LFS)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1032958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032958
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Tags: ftbfs, hppa, patch
Version: 8.2302.0-1
rsyslog randomly fails to build from source on the hppa platform due to
some testcases randomly failing.
I've tracked down various issues, partly related to how the debian
buildd server is setup on hppa, but the main problem is, that
rsyslog isn't built with large file support, which allows 32-bit platforms
(like hppa) to access files on the filesystem beyond the 2GB limit.
This affects all "stat()" and "readdir()" glibc calls in the source.
If rsyslog is built with LFS enabled (when _FILE_OFFSET_BITS=64
_LARGEFILE_SOURCE are defined for gcc),
the testcases succeed.
So, please enable LFS for rsyslog in the next upload.
The easiest way to do that in a compatible way is to simply
add "future=+lfs" to DEB_BUILD_MAINT_OPTIONS
in the "debian/rules" file, like this:
export DEB_BUILD_MAINT_OPTIONS = hardening=+all future=+lfs
This should fix all other 32-bit platforms as well and has no effect
on 64-bit platforms.
Thanks,
Helge
--- End Message ---
--- Begin Message ---
On Tue, 14 Mar 2023 21:57:46 +0100 Helge Deller <[email protected]> wrote:
On 3/14/23 19:20, Michael Biebl wrote:
> Am 14.03.23 um 19:13 schrieb Helge Deller:
>> On 3/14/23 19:06, Helge Deller wrote:
>>>>> That flag is then used only for one C-file in the subdir
contrib/omhiredis.
>>>>
>>>> Which flag?
>>>
>>> I meant the compiler preprocessor defines:
>>> The c-files should be compiled with:
>>> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
>>
>> Example:
>> In plugins/impstats/impstats.c the glibc function readdir() is used.
>> Without the "_FILE_OFFSET_BITS=64" define this readdir() will
suddenly/randomly fail
>> at runtime if the directory (or the files inside the directory) are stored
at an
>> inode with doesn't fit into 32-bits.
>
> The generated config.h contains
> /* Number of bits in a file offset, on hosts where this is settable. */
> #define _FILE_OFFSET_BITS 64
>
> and plugins/impstats/impstats.c includes config.h
Seems you are correct.
My request might be bogus. Will check further.
I'm closing this with the information I have currently.
If you have further updates, please let me know.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
