Skip to contentSkip to conversation

docs: ubuntu_essential.sh: explicitly add libcrypt-dev

PATCH Applied [email protected] 3 participants 4 messages Apr 10 – Apr 16

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs: ubuntu_essential.sh: explicitly add libcrypt-dev

From: Martin Jansa <[email protected]>

In latest ubuntu-26.04 build-essential no longer installs libcrypt-dev But virtual/crypt-native is in ASSUME_PROVIDED and is expected to be usable for development.

It used to be installed as build-essential -> libc6-dev -> libcrypt-dev,b ut not anymore since 2.42-7:

25.10 questing with 2.42-0ubuntu3.1:
https://packages.ubuntu.com/questing/libc6-dev
26.04 resolute with 2.43-2ubuntu1:
https://packages.ubuntu.com/resolute/libc6-dev

https://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.43-2ubuntu1/changelog:
...
glibc (2.42-7) unstable; urgency=medium

[ Aurelien Jarno ]
* debian/control.in/libc, debian/rules.d/debhelper.mk: drop libcrypt-dev dependency from libc6-dev. Thanks to Helmut Grohne for proposing that, doing an archive rebuild and filling the bug reports.
* debian/control.in/main, debian/sysdeps/linux.mk: enable SystemTap static probes.
* debian/debhelper.in/libc-dev.NEWS: add a NEWS entry about the removal of the obsolete termio interface. Closes: #1124068.
* debian/rules.d/debhelper.mk: ensure that linker scripts work even when

    /usr is unmerged.  Closes: #1120508

* debian/debhelper.in/libc-dev{,-alt}.lintian-overrides, source/lintian-overrides, rules.d/debhelper.mk, salsa-ci.yml: drop unpack-message-for-{orig,source} overrides, fixed in lintian 2.128.0.
* debian/control.in/main: drop Rules-Requires-Root: no, this is now the default.
* debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: remove the workaround for GLIBC_ABI_GNU_TLS. Closes: #1122038.
* debian/control.in/{libc,i386}: ensure that libdpkg-perl is fixed wrt GLIBC_ABI_GNU_TLS.

-- Aurelien Jarno <[email protected]> Sun, 04 Jan 2026 10:07:24 +0100
...

Without libcrypt-dev installed on host building shadow-native will fail with:
checking for crypt in -lcrypt... no
configure: error: crypt() not found
and python3-native with:
The necessary bits to build these optional modules were not found:
_crypt
To find the necessary bits, look in configure.ac and config.log.

---
 documentation/tools/host_packages_scripts/ubuntu_essential.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
documentation/tools/host_packages_scripts/ubuntu_essential.sh +1 -1
index 6584a0403..6234f885e 100644
@@ -1 +1 @@
-sudo apt-get install build-essential chrpath cpio debianutils diffstat file gawk gcc git iputils-ping libacl1 locales python3 python3-git python3-jinja2 python3-pexpect python3-pip python3-subunit socat texinfo unzip wget xz-utils zstd
+sudo apt-get install build-essential libcrypt-dev chrpath cpio debianutils diffstat file gawk gcc git iputils-ping libacl1 locales python3 python3-git python3-jinja2 python3-pexpect python3-pip python3-subunit socat texinfo unzip wget xz-utils zstd
Acked-by on v1 1/1
#1 lore raw

Hi Martin,

Quoted 11 lines · Martin Jansa via lists.yoctoproject.org

From: Martin Jansa <[email protected]>

In latest ubuntu-26.04 build-essential no longer installs libcrypt-dev But virtual/crypt-native is in ASSUME_PROVIDED and is expected to be usable for development.

It used to be installed as build-essential -> libc6-dev -> libcrypt-dev,b ut not anymore since 2.42-7:

25.10 questing with 2.42-0ubuntu3.1:
https://packages.ubuntu.com/questing/libc6-dev

Broken link.

Quoted 30 lines

26.04 resolute with 2.43-2ubuntu1:
https://packages.ubuntu.com/resolute/libc6-dev

https://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.43-2ubuntu1/changelog:
...
glibc (2.42-7) unstable; urgency=medium

[ Aurelien Jarno ]
* debian/control.in/libc, debian/rules.d/debhelper.mk: drop libcrypt-dev dependency from libc6-dev. Thanks to Helmut Grohne for proposing that, doing an archive rebuild and filling the bug reports.
* debian/control.in/main, debian/sysdeps/linux.mk: enable SystemTap static probes.
* debian/debhelper.in/libc-dev.NEWS: add a NEWS entry about the removal of the obsolete termio interface. Closes: #1124068.
* debian/rules.d/debhelper.mk: ensure that linker scripts work even when

     /usr is unmerged.  Closes: #1120508

* debian/debhelper.in/libc-dev{,-alt}.lintian-overrides, source/lintian-overrides, rules.d/debhelper.mk, salsa-ci.yml: drop unpack-message-for-{orig,source} overrides, fixed in lintian 2.128.0.
* debian/control.in/main: drop Rules-Requires-Root: no, this is now the default.
* debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: remove the workaround for GLIBC_ABI_GNU_TLS. Closes: #1122038.
* debian/control.in/{libc,i386}: ensure that libdpkg-perl is fixed wrt GLIBC_ABI_GNU_TLS.

-- Aurelien Jarno <[email protected]> Sun, 04 Jan 2026 10:07:24 +0100
...

Quoted 9 lines

Without libcrypt-dev installed on host building shadow-native will fail with:
checking for crypt in -lcrypt... no
configure: error: crypt() not found
and python3-native with:
The necessary bits to build these optional modules were not found:
_crypt
To find the necessary bits, look in configure.ac and config.log.

Note that we share the Ubuntu instructions with Debian (and for many different versions).

On pkgs.org, libcrypt-dev exists for Debian Bullseye, Bookworm and Trixie. I manually installed the package on 22.04, 24.04, 25.04 and 25.10 and they all exist.

So:

Thanks!
Quentin

#2 lore raw
Quoted 10 lines · Quentin Schulz

Hi Martin,

Quoted 6 lines · Martin Jansa via lists.yoctoproject.org

From: Martin Jansa <[email protected]>

In latest ubuntu-26.04 build-essential no longer installs libcrypt-dev But virtual/crypt-native is in ASSUME_PROVIDED and is expected to be usable for development.

Quoted 7 lines
Quoted 5 lines

It used to be installed as build-essential -> libc6-dev -> libcrypt-dev,b ut not anymore since 2.42-7:

25.10 questing with 2.42-0ubuntu3.1:
https://packages.ubuntu.com/questing/libc6-dev

Broken link.

That's probably temporarily broken as it often returns 500 Internal Server Error, but it was working link yesterday :).

Quoted 40 lines
Quoted 30 lines

26.04 resolute with 2.43-2ubuntu1:
https://packages.ubuntu.com/resolute/libc6-dev

https://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.43-2ubuntu1/changelog:
...
glibc (2.42-7) unstable; urgency=medium

[ Aurelien Jarno ]
* debian/control.in/libc, debian/rules.d/debhelper.mk: drop libcrypt-dev dependency from libc6-dev. Thanks to Helmut Grohne for proposing that, doing an archive rebuild and filling the bug reports.
* debian/control.in/main, debian/sysdeps/linux.mk: enable SystemTap static probes.
* debian/debhelper.in/libc-dev.NEWS: add a NEWS entry about the removal of the obsolete termio interface. Closes: #1124068.
* debian/rules.d/debhelper.mk: ensure that linker scripts work even when

     /usr is unmerged.  Closes: #1120508

* debian/debhelper.in/libc-dev{,-alt}.lintian-overrides, source/lintian-overrides, rules.d/debhelper.mk, salsa-ci.yml: drop unpack-message-for-{orig,source} overrides, fixed in lintian 2.128.0.
* debian/control.in/main: drop Rules-Requires-Root: no, this is now the default.
* debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: remove the workaround for GLIBC_ABI_GNU_TLS. Closes: #1122038.
* debian/control.in/{libc,i386}: ensure that libdpkg-perl is fixed wrt GLIBC_ABI_GNU_TLS.

-- Aurelien Jarno <[email protected]> Sun, 04 Jan 2026 10:07:24 +0100
...

Quoted 9 lines

Without libcrypt-dev installed on host building shadow-native will fail with:
checking for crypt in -lcrypt... no
configure: error: crypt() not found
and python3-native with:
The necessary bits to build these optional modules were not found:
_crypt
To find the necessary bits, look in configure.ac and config.log.

Quoted 6 lines

Note that we share the Ubuntu instructions with Debian (and for many different versions).

On pkgs.org, libcrypt-dev exists for Debian Bullseye, Bookworm and Trixie. I manually installed the package on 22.04, 24.04, 25.04 and 25.10 and they all exist.

Yes, the package exists and will probably exist for a long time, it's just not installed as build-essential dependency anymore.