Your message dated Sun, 11 Feb 2024 23:29:24 +0100
with message-id <[email protected]>
and subject line Re: Bug#1063733: no -D_TIME_BITS=64 on builds where t64
support is supposed to be done
has caused the Debian Bug report #1063733,
regarding no -D_TIME_BITS=64 on builds where t64 support is supposed to be done
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.)
--
1063733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063733
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gpgme1.0
Version: 1.18.0-4.1~exp1
Severity: important
[ let's no get into a discussion on the sense of this transition. I
actually believe this isn't needed and we can leave 32 bit die in 2038
but anyways...
The transition is ongoing now in experimental. So be it ]
Hi,
I just tried a rebuild of libreoffice with
DEB_HOST_MAINT_OPTIONS="abi=+time64" to actually see what happens.
It failed in a certificate unit tests so I tried to rebuild the
"certificate" related (build-)dependencies also with
DEB_HOST_MAINT_OPTIONS="abi=+time64"
While doing so I noticed that gpgme1.0 doesn't define -D_TIME_BITS=64
even when built for t64 (as in the experimental NMU renaming to t64) on
the affected architectures (anything 32-bit except i386).
This is probably because it doesn't honout dpkg-buildflags.
But even if you don't like dpkg-buildflags that define has to be done.
Regards,
Rene
P.S::
Thankfully libreoffice is fine without a rebuilt gpgme1.0 somehow
--- End Message ---
--- Begin Message ---
Hi,
Am 11.02.24 um 23:22 schrieb Sven Joachim:
While doing so I noticed that gpgme1.0 doesn't define -D_TIME_BITS=64
even when built for t64 (as in the experimental NMU renaming to t64)
on the affected architectures (anything 32-bit except i386).
This is probably because it doesn't honout dpkg-buildflags.
No, this is because debian/rules already sets DEB_BUILD_MAINT_OPTIONS,
overriding the value from the environment. Either add abi=+time64 there
But LO also does, and there the envvar took effect..
or set DEB_BUILD_OPTIONS rather than DEB_BUILD_MAINT_OPTIONS in the
environment.
with DEB_BUILD_OPTIONS I get
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
I don't think there is a bug here.
Looks like it, sorry.
Regards,
Rene
--- End Message ---
