kumquat-buildroot/package/e2fsprogs/e2fsprogs.mk

98 lines
3.2 KiB
Makefile
Raw Normal View History

################################################################################
#
# e2fsprogs
#
################################################################################
E2FSPROGS_VERSION = 1.43.7
E2FSPROGS_SOURCE = e2fsprogs-$(E2FSPROGS_VERSION).tar.xz
E2FSPROGS_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/people/tytso/e2fsprogs/v$(E2FSPROGS_VERSION)
E2FSPROGS_LICENSE = GPL-2.0, MIT-like with advertising clause (libss and libet)
E2FSPROGS_LICENSE_FILES = NOTICE lib/ss/mit-sipb-copyright.h lib/et/internal.h
E2FSPROGS_INSTALL_STAGING = YES
# Use libblkid and libuuid from util-linux for host and target packages.
# This prevents overriding them with e2fsprogs' ones, which may cause
# problems for other packages.
E2FSPROGS_DEPENDENCIES = host-pkgconf util-linux
HOST_E2FSPROGS_DEPENDENCIES = host-pkgconf host-util-linux
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
# If both e2fsprogs and busybox are selected, make certain e2fsprogs
# wins the fight over who gets to have their utils actually installed
ifeq ($(BR2_PACKAGE_BUSYBOX),y)
E2FSPROGS_DEPENDENCIES += busybox
endif
# e4defrag doesn't build on older systems like RHEL5.x, and we don't
# need it on the host anyway.
# Disable fuse2fs as well to avoid carrying over deps, and it's unused
HOST_E2FSPROGS_CONF_OPTS = \
--disable-defrag \
--disable-e2initrd-helper \
--disable-fuse2fs \
--disable-libblkid \
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
--disable-libuuid \
--enable-symlink-install \
--disable-testio-debug
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
# Set the binary directories to "/bin" and "/sbin" to override programs
# installed by busybox.
E2FSPROGS_CONF_OPTS = \
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
--bindir=/bin \
--sbindir=/sbin \
$(if $(BR2_STATIC_LIBS),--disable-elf-shlibs,--enable-elf-shlibs) \
$(if $(BR2_PACKAGE_E2FSPROGS_DEBUGFS),--enable-debugfs,--disable-debugfs) \
$(if $(BR2_PACKAGE_E2FSPROGS_E2IMAGE),--enable-imager,--disable-imager) \
$(if $(BR2_PACKAGE_E2FSPROGS_E4DEFRAG),--enable-defrag,--disable-defrag) \
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
$(if $(BR2_PACKAGE_E2FSPROGS_FSCK),--enable-fsck,--disable-fsck) \
$(if $(BR2_PACKAGE_E2FSPROGS_RESIZE2FS),--enable-resizer,--disable-resizer) \
--disable-uuidd \
--disable-libblkid \
--disable-libuuid \
--disable-e2initrd-helper \
--disable-testio-debug \
e2fsprogs: refactor to fix conflicts with busybox and util-linux So far we attempted to solve the conflicts between busybox and e2fsprogs by removing busybox programs from /bin and /sbin, leaving the e2fsprogs ones at /usr/bin and /usr/sbin. This fails with BR2_ROOTFS_MERGED_USR=y, leading to situations like the one described in bug 9436. We could provide a better solution by means of a fine-grained selection of programs, like util-linux does, but this would require big changes in e2fsprogs. So instead of resorting to dirty tricks we switch to a more pragmatic approach: - Drop all configs to select/deselect utilities without corresponding enable/disable options to the configure script. In other words, we always install the basic set of utilities. - fsck has a configure option, so use it. Note that --enable-fsck is only about the wrapper, not about e2fsck. - Install e2fsprogs utilities at /bin and /sbin, overriding the ones eventually installed by busybox. - Let the e2fsprogs build system create the symlinks mkfs.ext2 -> mke2fs etc. fsck.ext4dev and mkfs.ext4dev were dropped in version 1.43.4. Notice that these changes do exactly the opposite of what is requested in bug 9436. On the other hand the policy for e2fsprogs becomes coherent with the one for util-linux: busybox never wins. Fixes: https://bugs.busybox.net/show_bug.cgi?id=9436 (no fix, in fact) Signed-off-by: Carlos Santos <casantos@datacom.ind.br> [Arnout: - don't add 'default y' to resize2fs; - don't install the host package in /bin instead of /usr/bin - we install everything under /usr (until /usr will be removed, soon)] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-23 00:49:13 +02:00
--disable-rpath \
--enable-symlink-install
ifeq ($(BR2_PACKAGE_E2FSPROGS_FUSE2FS),y)
E2FSPROGS_CONF_OPTS += --enable-fuse2fs
E2FSPROGS_DEPENDENCIES += libfuse
else
E2FSPROGS_CONF_OPTS += --disable-fuse2fs
endif
ifeq ($(BR2_nios2),y)
E2FSPROGS_CONF_ENV += ac_cv_func_fallocate=no
endif
# Some programs are built for the host, but use definitions guessed by
# the configure script (i.e with the cross-compiler). Help them by
# saying that <sys/stat.h> is available on the host, which is needed
# for util/subst.c to build properly.
E2FSPROGS_CONF_ENV += BUILD_CFLAGS="-DHAVE_SYS_STAT_H"
# Disable use of the host magic.h, as on older hosts (e.g. RHEL 5)
# it doesn't provide definitions expected by e2fsprogs support lib.
HOST_E2FSPROGS_CONF_ENV += \
ac_cv_header_magic_h=no \
ac_cv_lib_magic_magic_file=no
E2FSPROGS_MAKE_OPTS = LDCONFIG=true
E2FSPROGS_INSTALL_STAGING_OPTS = \
DESTDIR=$(STAGING_DIR) \
LDCONFIG=true \
install-libs
E2FSPROGS_INSTALL_TARGET_OPTS = \
DESTDIR=$(TARGET_DIR) \
LDCONFIG=true \
install
define HOST_E2FSPROGS_INSTALL_CMDS
$(HOST_MAKE_ENV) $(MAKE) -C $(@D) install install-libs
endef
$(eval $(autotools-package))
$(eval $(host-autotools-package))