On 2019-04-21 11:27 +0800, Kevin Buckley via lfs-dev wrote: > On Sat, 20 Apr 2019 at 23:49, Bruce Dubbs via lfs-dev > <[email protected]> wrote: > > Indeed, I now see why you would want multiple, arch-specific, locations > for arch-specific Pkg-Config files, and a location for arch-agnostic ones, > however, the question, for me, still remains as to why an x86_64 specific > udev.pc ends up in a "common/arch-agnostic" location and not below > /usr/lib/pkgconfig (the home of the x86_64 arch) ? > > The content of > > /usr/share/pkgconfig/udev.pc > > Name: udev > Description: eudev > Version: 220 > prefix=/usr > exec_prefix=${prefix} > udevdir=/lib/udev > > by virtue of pointing to the /lib/udev, which is arch-specific,
It's not. /lib/udev only contains udev scripts and some executable helpers for udevd. There are no libraries in it. We can not have two udevd instances for x86_64 and i686, so udevd is not arch- specific. Run `ps -e | grep udevd` and you won't see something like "udevd-32" or "udevd-64". -- Xi Ruoyao <[email protected]> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
