/usr/lib64? Wait what? [LWN.net]

/usr/lib64? Wait what?

Posted Jan 28, 2021 23:35 UTC (Thu) by mirabilos (subscriber, #84359)
Parent article: A year of Python in Fedora

There’s no /usr/lib64 in Debian, and there never will be.

Debian has migrated to Multi-Arch paths, so we have /usr/lib/i386-linux-gnu/ and /usr/lib/arm-linux-gnueabi/ and /usr/lib/x86_64-linux-gnu/ and even /usr/lib/x86_64-linux-musl/ now. Have been having for quite a couple of years, actually.

to post comments

/usr/lib64? Wait what?

Posted Jan 29, 2021 14:22 UTC (Fri) by mathstuf (subscriber, #69389) [Link] (1 responses)

The mention in the article is that it was adopted for Red Hat-based multilib layouts (and all those distros had carried the patch(es) for years). What gives you the idea that it is in any way related to Debian's multiarch layouts?

/usr/lib64? Wait what?

Posted Jan 29, 2021 14:30 UTC (Fri) by jake (editor, #205) [Link]

> What gives you the idea that it is in any way related to Debian's multiarch layouts?

Well, Miro's post does mention Debian and I reported that:

> Work from both Fedora and openSUSE developers means that those distributions,
> and others such as Gentoo and Debian, can stop carrying a patch that has been
> around for 16 years at this point.

I assume (but have not looked into it) that Debian uses the patch to put the modules in some other directory, not /usr/lib64

jake

/usr/lib64? Wait what?

Posted Jan 29, 2021 15:07 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link] (1 responses)

The pr for this is linked in the article:

https://github.com/python/cpython/commit/8510f430781118d9...

This merged pr from Fedora means that instead of carrying a patch, Debian should be able to just use the configure option and pass a different param depending on the distro local preferences.

/usr/lib64? Wait what?

Posted Jan 29, 2021 17:55 UTC (Fri) by nix (subscriber, #2304) [Link]

Of course, whether it's platlibdir or platlitdir depends on which part of the patch you read. Gotta love typos. :)

/usr/lib64? Wait what?

Posted Jan 31, 2021 3:25 UTC (Sun) by Conan_Kudo (subscriber, #103240) [Link] (4 responses)

That directory exists on Debian too. 😉
You can even see it in Debian 11 and Ubuntu 20.04 today.

/usr/lib64? Wait what?

Posted Jan 31, 2021 3:45 UTC (Sun) by pabs (subscriber, #43278) [Link] (2 responses)

That isn't true, there are no packages containing /usr/lib64:

$ apt-file search /usr/lib64 ; echo ⭲ $?
⭲ 1

I assume you are getting confused by the usrmerge hack, which breaks a bunch of different things, including `dpkg -S` and is considered broken and unsupported by the dpkg maintainer.

$ ls -ld /lib64
drwxr-xr-x 2 root root 4096 Jan 5 23:41 /lib64
$ sudo chronic apt -qqy install usrmerge
$ ls -ld /lib64
lrwxrwxrwx 1 root root 9 Jan 31 03:43 /lib64 -> usr/lib64

https://wiki.debian.org/Teams/Dpkg/MergedUsr

/usr/lib64? Wait what?

Posted Jan 31, 2021 4:51 UTC (Sun) by Conan_Kudo (subscriber, #103240) [Link] (1 responses)

Packages in Debian using that path are prefixed with lib64, like lib64z1 on i386 and armhf.

/usr/lib64? Wait what?

Posted Jan 31, 2021 13:20 UTC (Sun) by mirabilos (subscriber, #84359) [Link]

The libz multilib packages are one of the *very* few remnants of a pre-Multi-Arch world and will probably be removed some day.

/usr/lib64? Wait what?

Posted Jan 31, 2021 3:53 UTC (Sun) by mirabilos (subscriber, #84359) [Link]

It doesn’t.

There’s /lib64 but that’s only required because it contains the path to the dynamic linker (ld.so) which is mandated by the ABI. No other file is permitted into this nōn-filesystem-hierarchy-standard(as-specified-by-Debian)-compliant directory.