[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250503131202.GY1827@brightrain.aerifal.cx>
Date: Sat, 3 May 2025 09:12:02 -0400
From: Rich Felker <dalias@...c.org>
To: lid gnulinux <lidgnulinux@...il.com>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>,
raniriahmad@...il.com, ahmadraniri1994@...il.com
Subject: Re: Musl & libxcrypt library.
On Thu, May 01, 2025 at 09:03:16PM +0700, lid gnulinux wrote:
> Hello, I hope it's still relevant with musl.
> About two months ago, I built a Linux
> >From Scratch with musl. I mistakenly also
> built libxcrypt and not knowing that libxcrypt
> will replace some header files from musl.
> I fortunately restore some replaced headers
> back. Today I realized I still have libcrypt.so
> from libxcrypt. Do I need to keep that library?
> When I move it (instead of delete it) I can't
> build shadow package (it complained about
> missing crypt() function). Thanks.
musl has a working crypt implementation and it's not intended that you
need to use libxcrypt on a musl-based system, unless you want it for
the "heavy" hashes. If you do want to use it, it's recommended that
you install the headers in a separate directory so you can select them
by putting the appropriate -I in CFLAGS, rather than clobbering the
libc header. Likewise, the library should be named libxcrypt, not
libcrypt, so it doesn't supersede or clobber the (intentionally empty;
all actual functions are in libc.{a,so}) libcrypt.a shipped with musl.
Then you can select it with the appropriate -I and -l.
Without further information I don't know what your problem building
the shadow package is, and whether it's a consequence of something
that got clobbered, some wrong detection the shadow build process is
doing, or just failure to re-run configure or whatever after fixing
the mess.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
