ubuntu-389-directory-server team mailing list archive

[Launchpad Bug Tracker <2052578@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package 389-ds-base - 2.4.4+dfsg1-1ubuntu1

---------------
389-ds-base (2.4.4+dfsg1-1ubuntu1) noble; urgency=medium

  * d/p/32bit-support.diff: Fixes support for 32-bit architectures
    (LP: #2052578)

 -- Chris Peterson <chris.peterson@xxxxxxxxxxxxx>  Thu, 08 Feb 2024
16:26:51 -0800

** Changed in: 389-ds-base (Ubuntu)
       Status: Triaged => Fix Released

-- 
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:
  Fix Released

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