ubuntu-389-directory-server team mailing list archive
-
ubuntu-389-directory-server team
-
Mailing list archive
-
Message #00356
[Bug 2052578] Re: 2.4.4+dfsg1-1 is FTBFS on armhf in Noble
** Changed in: 389-ds-base (Ubuntu)
Status: New => Incomplete
** Changed in: 389-ds-base (Ubuntu)
Status: Incomplete => Triaged
** Changed in: 389-ds-base (Ubuntu)
Status: Triaged => In Progress
** Changed in: 389-ds-base (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/2052578
Title:
2.4.4+dfsg1-1 is FTBFS on armhf in Noble
Status in 389-ds-base package in Ubuntu:
Triaged
Bug description:
build fails with:
ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c: At top level:
ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c:429:26: error: unknown type name ‘off64_t’; did you mean ‘off_t’?
429 | bdb_seek43_large(int fd, off64_t offset, int whence)
| ^~~~~~~
| off_t
The source properly detects when to define _LARGEFILE64_SOURCE but I think this is an ordering issue of the define and a standard library header include.
I can recreate this on an armhf machine by including <stdio.h> before
the LFS define.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2052578/+subscriptions
References