mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Cc: Sebastian Priebe <sebastian.priebe@konplan.com>
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2025.11.0 released
Date: Tue, 9 Dec 2025 12:15:51 +0100	[thread overview]
Message-ID: <ae36d4ca-c0df-45a4-a105-c432558d277c@t2data.com> (raw)
In-Reply-To: <ZR0P278MB0974D67A7296A31CF735DE709FA3A@ZR0P278MB0974.CHEP278.PROD.OUTLOOK.COM>

Hi Sebastian.

On 12/9/25 8:47 AM, Sebastian Priebe via ptxdist wrote:
> Hello Michael,
> 
> thank you for the new release.
> I wanted to try it out and noticed that after installation the libcrypt.so from the glibc is missing. Also the crypt.h header isn't available in the installation.
> Therefore it fails to build busybox with:
>> libbb/pw_encrypt.c:11:12: fatal error: crypt.h: No such file or directory
> 
> I'm using the following ptxdist configurations:
> aarch64-v8a-linux-gnu_gcc-15.2.1_clang-21.1.6_glibc-2.42_binutils-2.45.1_kernel-6.17.6-sanitized
> arm-1136jfs-linux-gnueabihf_gcc-15.2.1_glibc-2.42_binutils-2.45.1_kernel-6.17.6-sanitized
> 
> Any advice?
> 

libcrypt has been removed from glibc a while ago.
2.38 had it disabled by default and 2.39 removed it completely.
I think most use libxcrypt instead.
It's available in ptxdist.

Regards,
Christian

> Thanks,
> Sebastian
> 
>> -----Ursprüngliche Nachricht-----
>> Von: ptxdist <ptxdist-bounces@pengutronix.de> Im Auftrag von Michael Olbrich
>> <m.olbrich@pengutronix.de>
>> Gesendet: Donnerstag, 27. November 2025 09:11
>> An: ptxdist@pengutronix.de
>> Betreff: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2025.11.0 released
>>
>> Hi,
>>
>> I'm happy to announce that I've just released OSELAS.Toolchain-2025.11.0.
>>
>> This is a major release with significant changes. All components of the primary
>> toolchains have been updated to the latest versions. The highlights
>> are:
>>   - binutils 2.45.1
>>   - clang 21.1.6
>>   - gcc 15.2
>>   - gdb 16.3
>>   - glibc 2.42
>>   - kernel headers 6.17.6
>>   - rustc 1.91.1
>>
>> The minimum kernel version that glibc will run on remained at v5.15.
>>
>> The toolchains with rust also include musl 1.2.5. This is not meant as a general libc.
>> It is used to support an addition target for the rust compiler. It can be used to build
>> smaller static binaries.
>>
>> Download the release here:
>> https://public.pengutronix.de/oselas/toolchain/
>>
>> Debian / Ubuntu Packages will be available at http://debian.pengutronix.de/
>>
>> My current plan is to build packages for Debian forky/sid, trixie, bookworm, and
>> Ubuntu 22.04, 24.04. The packages will show up in the near future.
>>
>> Enjoy,
>> Michael Olbrich
>>
>> --
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
> 




  reply	other threads:[~2025-12-09 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27  8:10 Michael Olbrich
2025-12-09  7:47 ` Sebastian Priebe via ptxdist
2025-12-09 11:15   ` Christian Melki [this message]
2025-12-10  7:56     ` Sebastian Priebe via ptxdist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae36d4ca-c0df-45a4-a105-c432558d277c@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    --cc=sebastian.priebe@konplan.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox