gparted/configure.ac

400 lines
13 KiB
Plaintext
Raw Normal View History

AC_INIT([gparted],[0.27.0-git],[https://bugzilla.gnome.org/enter_bug.cgi?product=gparted])
AC_PREREQ([2.50])
AC_CONFIG_SRCDIR([src/main.cc])
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_MACRO_DIR([m4])
AM_INIT_AUTOMAKE([1.9])
2004-09-19 16:32:22 -06:00
AM_MAINTAINER_MODE
2004-09-19 14:24:53 -06:00
2004-09-20 09:46:21 -06:00
2004-09-23 13:32:57 -06:00
dnl======================
dnl checks for programs
2004-09-23 13:32:57 -06:00
dnl======================
2004-09-19 14:24:53 -06:00
AC_PROG_CXX
AC_PROG_CC
AC_PROG_LIBTOOL
AC_PROG_AWK
dnl Check for pkg-config early to avoid splitting message when first used.
PKG_CHECK_EXISTS
2004-09-19 14:24:53 -06:00
dnl======================
dnl checks for other programs
dnl======================
AC_CHECK_PROGS([GKSUPROG], [gksudo gksu kdesudo "xdg-su -c"], [])
2004-09-23 13:32:57 -06:00
dnl======================
dnl i18n stuff
2004-09-23 13:32:57 -06:00
dnl======================
2004-09-20 09:46:21 -06:00
GETTEXT_PACKAGE=gparted
AC_SUBST([GETTEXT_PACKAGE])
AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE], "$GETTEXT_PACKAGE", [description])
2004-09-20 09:46:21 -06:00
AM_GLIB_GNU_GETTEXT
IT_PROG_INTLTOOL([0.35.5])
2004-09-23 13:32:57 -06:00
dnl======================
dnl checks for libs
2004-09-23 13:32:57 -06:00
dnl======================
AC_CHECK_LIB([uuid], [uuid_generate], [], AC_MSG_ERROR([*** libuuid not found.]))
AC_CHECK_LIB([dl], [dlopen], [], AC_MSG_ERROR([*** libdl not found.]))
AC_CHECK_LIB([parted], [ped_device_read], [], AC_MSG_ERROR([*** libparted not found.]))
dnl Check for minimum required libparted version.
dnl 1) Check using pkg-config.
dnl (Older distros tend to not provide pkg-config information for libparted).
dnl 2) Check by linking and running a program to report libparted version directly.
LIBPARTED_REQUIRED_VERSION='1.7.1'
AC_MSG_CHECKING([for libparted >= $LIBPARTED_REQUIRED_VERSION (querying pkg-config)])
LIBPARTED_REQUIRED_INT=`echo "$LIBPARTED_REQUIRED_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
dnl 1) Check using pkg-config.
PKG_CHECK_EXISTS(
[libparted],
[LIBPARTED_FOUND_VERSION=`$PKG_CONFIG --modversion libparted`
LIBPARTED_FOUND_INT=`echo "$LIBPARTED_FOUND_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
AC_MSG_RESULT([$LIBPARTED_FOUND_VERSION])
test "$LIBPARTED_FOUND_INT" -ge "$LIBPARTED_REQUIRED_INT" ||
AC_MSG_ERROR([*** libparted too old. Require libparted >= $LIBPARTED_REQUIRED_VERSION but only found libparted $LIBPARTED_FOUND_VERSION.])
],
[AC_MSG_RESULT([not found])
dnl 2) Check by linking and running a program to report libparted version
dnl directly.
AC_MSG_CHECKING([for libparted >= $LIBPARTED_REQUIRED_VERSION (querying libparted)])
AC_RUN_IFELSE(
[AC_LANG_SOURCE(
[[
#include <stdio.h>
#include <stdlib.h>
#include <parted/parted.h>
int main()
{
const char *version = ped_get_version();
if (version == NULL)
{
fprintf(stderr, "ERROR: ped_get_version() returned NULL\n");
return EXIT_FAILURE;
}
printf("%s\n", version);
return EXIT_SUCCESS;
}
]]
)],
dnl Run test program again to cache libparted version.
[LIBPARTED_FOUND_VERSION=`./conftest$EXEEXT`
LIBPARTED_FOUND_INT=`echo "$LIBPARTED_FOUND_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
test "$LIBPARTED_FOUND_INT" -ge "$LIBPARTED_REQUIRED_INT" ||
AC_MSG_ERROR([*** libparted too old. Require libparted >= $LIBPARTED_REQUIRED_VERSION but only found libparted $LIBPARTED_FOUND_VERSION.])
],
[AC_MSG_ERROR([*** Error querying libparted version. Check config.log for details.])]
)]
)
Fix failure to recognise whole disk file systems in certain cases (#743181) When the following conditions were met GParted would fail to recognise a newly created whole disk device file system, and instead show an unknown file system filling the disk: 1) Disk was previously partitioned and contained at least one partition. 2) Using libparted version 2.0 to 3.0 inclusive. Initial status: # blkid | fgrep sdc # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 # parted /dev/sdc GNU Parted 2.4 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 107GB 107GB primary When creating the loop partition table libparted would not inform the kernel to delete the old partitions. /proc/partitions still contained the details of the old partitions. (parted) mktable loop Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Number Start End Size File system Flags (parted) quit # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 Creation of the whole disk device file system goes unnoticed by blkid because the kernel and therefore blkid's cache have stale partition information. # mkfs.xfs -f /dev/sdc # blkid | fgrep sdc NOTE: On a Linux Software RAID array, as opposed to a hard disk, blkid does notice creation of the whole disk device file system. However the kernel still has old partition details. This was fixed in libparted 3.1 by commit: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=f5c909c0cd50ed52a48dae6d35907dc08b137e88 libparted: remove has_partitions check to allow loopback partitions Fix by deleting old partitions before creating the loop table when compiled with a broken version of libparted. The GParted UI provides no feedback while a new partition table is created, and with some versions of GTK the UI become unresponsive too, so it is important to be as fast as possible. Evaluated three different methods, deleting 15 and 22 MSDOS partitions on a physical 5400 RPM hard drive using libparted 2.4: M1) Delete and commit one partition at a time. Takes up to 24 seconds to delete 15 partitions. With 22 partitions libparted always reports finding some of the partitions busy and unable to inform the kernel about the modifications. Too slow and doesn't work. M2) Delete all partitions in one go and commit once. Takes up to 1.4 seconds to delete either 15 or 22 partitions. Never removes partitions 17 and higher from the kernel. Doesn't work. M3) Write GPT table (letting libparted delete any old partitions). Takes up to 0.8 seconds to delete either 15 or 22 partitions. Fast and works. Use method 3 - write a GPT table thus using libparted code to inform the kernel of the old partition deletions. Bug 743181 - Add unpartitioned drive read-write support
2015-02-21 09:43:42 -07:00
dnl Check for libparted 2.0 to 3.0 inclusive for a bug where loop table
dnl creation doesn't delete old partitions.
LIBPARTED_MIN_WANTED_VERSION='2.0'
LIBPARTED_MAX_WANTED_VERSION='3.0'
AC_MSG_CHECKING([for $LIBPARTED_MIN_WANTED_VERSION <= libparted <= $LIBPARTED_MAX_WANTED_VERSION (loop table creation doesn't delete old partitions)])
LIBPARTED_MIN_WANTED_INT=`echo "$LIBPARTED_MIN_WANTED_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
Fix failure to recognise whole disk file systems in certain cases (#743181) When the following conditions were met GParted would fail to recognise a newly created whole disk device file system, and instead show an unknown file system filling the disk: 1) Disk was previously partitioned and contained at least one partition. 2) Using libparted version 2.0 to 3.0 inclusive. Initial status: # blkid | fgrep sdc # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 # parted /dev/sdc GNU Parted 2.4 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 107GB 107GB primary When creating the loop partition table libparted would not inform the kernel to delete the old partitions. /proc/partitions still contained the details of the old partitions. (parted) mktable loop Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Number Start End Size File system Flags (parted) quit # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 Creation of the whole disk device file system goes unnoticed by blkid because the kernel and therefore blkid's cache have stale partition information. # mkfs.xfs -f /dev/sdc # blkid | fgrep sdc NOTE: On a Linux Software RAID array, as opposed to a hard disk, blkid does notice creation of the whole disk device file system. However the kernel still has old partition details. This was fixed in libparted 3.1 by commit: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=f5c909c0cd50ed52a48dae6d35907dc08b137e88 libparted: remove has_partitions check to allow loopback partitions Fix by deleting old partitions before creating the loop table when compiled with a broken version of libparted. The GParted UI provides no feedback while a new partition table is created, and with some versions of GTK the UI become unresponsive too, so it is important to be as fast as possible. Evaluated three different methods, deleting 15 and 22 MSDOS partitions on a physical 5400 RPM hard drive using libparted 2.4: M1) Delete and commit one partition at a time. Takes up to 24 seconds to delete 15 partitions. With 22 partitions libparted always reports finding some of the partitions busy and unable to inform the kernel about the modifications. Too slow and doesn't work. M2) Delete all partitions in one go and commit once. Takes up to 1.4 seconds to delete either 15 or 22 partitions. Never removes partitions 17 and higher from the kernel. Doesn't work. M3) Write GPT table (letting libparted delete any old partitions). Takes up to 0.8 seconds to delete either 15 or 22 partitions. Fast and works. Use method 3 - write a GPT table thus using libparted code to inform the kernel of the old partition deletions. Bug 743181 - Add unpartitioned drive read-write support
2015-02-21 09:43:42 -07:00
LIBPARTED_MAX_WANTED_INT=`echo "$LIBPARTED_MAX_WANTED_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
Fix failure to recognise whole disk file systems in certain cases (#743181) When the following conditions were met GParted would fail to recognise a newly created whole disk device file system, and instead show an unknown file system filling the disk: 1) Disk was previously partitioned and contained at least one partition. 2) Using libparted version 2.0 to 3.0 inclusive. Initial status: # blkid | fgrep sdc # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 # parted /dev/sdc GNU Parted 2.4 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 107GB 107GB primary When creating the loop partition table libparted would not inform the kernel to delete the old partitions. /proc/partitions still contained the details of the old partitions. (parted) mktable loop Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Number Start End Size File system Flags (parted) quit # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 Creation of the whole disk device file system goes unnoticed by blkid because the kernel and therefore blkid's cache have stale partition information. # mkfs.xfs -f /dev/sdc # blkid | fgrep sdc NOTE: On a Linux Software RAID array, as opposed to a hard disk, blkid does notice creation of the whole disk device file system. However the kernel still has old partition details. This was fixed in libparted 3.1 by commit: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=f5c909c0cd50ed52a48dae6d35907dc08b137e88 libparted: remove has_partitions check to allow loopback partitions Fix by deleting old partitions before creating the loop table when compiled with a broken version of libparted. The GParted UI provides no feedback while a new partition table is created, and with some versions of GTK the UI become unresponsive too, so it is important to be as fast as possible. Evaluated three different methods, deleting 15 and 22 MSDOS partitions on a physical 5400 RPM hard drive using libparted 2.4: M1) Delete and commit one partition at a time. Takes up to 24 seconds to delete 15 partitions. With 22 partitions libparted always reports finding some of the partitions busy and unable to inform the kernel about the modifications. Too slow and doesn't work. M2) Delete all partitions in one go and commit once. Takes up to 1.4 seconds to delete either 15 or 22 partitions. Never removes partitions 17 and higher from the kernel. Doesn't work. M3) Write GPT table (letting libparted delete any old partitions). Takes up to 0.8 seconds to delete either 15 or 22 partitions. Fast and works. Use method 3 - write a GPT table thus using libparted code to inform the kernel of the old partition deletions. Bug 743181 - Add unpartitioned drive read-write support
2015-02-21 09:43:42 -07:00
if test "$LIBPARTED_MIN_WANTED_INT" -le "$LIBPARTED_FOUND_INT" -a \
"$LIBPARTED_FOUND_INT" -le "$LIBPARTED_MAX_WANTED_INT"; then
need_loop_delete_old_ptns_workaround=yes
AC_DEFINE([ENABLE_LOOP_DELETE_OLD_PTNS_WORKAROUND], 1,
[Define to 1 to enable deletion of old partitions before creating a loop table workaround])
AC_MSG_RESULT([(cached) yes])
else
need_loop_delete_old_ptns_workaround=no
AC_MSG_RESULT([(cached) no])
fi
dnl Check for libparted >= 2.2 for improved informing the kernel to
dnl re-read the partition table code and support of larger sector sizes
dnl (> 512 bytes).
LIBPARTED_WANTED_VERSION='2.2'
AC_MSG_CHECKING([for libparted >= $LIBPARTED_WANTED_VERSION (improved pt re-read)])
LIBPARTED_WANTED_INT=`echo "$LIBPARTED_WANTED_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
if test "$LIBPARTED_FOUND_INT" -ge "$LIBPARTED_WANTED_INT"; then
AC_DEFINE([USE_LIBPARTED_LARGE_SECTOR_SUPPORT], 1,
[Define to 1 to use libparted large sector support])
need_pt_reread_workaround=no; support_large_sector_sizes=yes
AC_MSG_RESULT([(cached) yes])
else
AC_DEFINE([ENABLE_PT_REREAD_WORKAROUND], 1,
[Define to 1 to enable partition re-read workaround])
need_pt_reread_workaround=yes; support_large_sector_sizes=no
AC_MSG_RESULT([(cached) no])
fi
dnl Check for ped_file_system_resize() function to determine the existence
dnl of the API in the original parted library. Available in parted <= 2.4.
dnl
dnl NOTE:
dnl For AC_CHECK_LIB the default action-if-found ($3) includes extending
dnl LIBS with the newly found library ($1) thus:
dnl LIBS="-l$1 $LIBS"
dnl
dnl As the default action-if-found is overridden, LIBS isn't extended so
dnl saving and restoring LIBS isn't required.
have_old_lp_fs_resize_api=no
AC_CHECK_LIB(
[parted], [ped_file_system_resize],
[have_old_lp_fs_resize_api=yes]
)
dnl If not already found, check for ped_file_system_resize() function in
dnl the parted-fs-resize library to determine the need to use the new
dnl library. Available in parted >= 3.1.
have_new_lp_fs_resize_lib=no
AS_IF(
[test "x$have_old_lp_fs_resize_api" != xyes],
[AC_CHECK_LIB(
[parted-fs-resize], [ped_file_system_resize],
[have_new_lp_fs_resize_lib=yes
LIBS="-lparted-fs-resize $LIBS"
]
)]
)
dnl Check for libparted >= 3.2 for online resize support.
LIBPARTED_WANTED_VERSION='3.2'
AC_MSG_CHECKING([for libparted >= $LIBPARTED_WANTED_VERSION (online resize)])
LIBPARTED_WANTED_INT=`echo "$LIBPARTED_WANTED_VERSION" |
Fix configuration version compare issue affecting libparted from GIT (#753525) When configuring GParted build with libparted from GIT it may perform the version compares incorrectly and think the version of libparted is higher that it actually is. Libparted uses the number of commits from the last git tag as the third part of the version number. For example install libparted from one commit before release 3.1, 142 commits after release 3.0. $ git checkout v3.1^ $ describe v3.0-142-g82327a3 $ ./bootstrap $ ./configure --prefix=/tmp/parted-3.0-git $ make && make install Configure GParted: $ export CPPFLAGS=-I/tmp/parted-3.0-git/include $ export LDFLAGS=-L/tmp/parted-3.0-git/lib $ export LD_RUN_PATH=/tmp/parted-3.0-git/lib $ export PKG_CONFIG_PATH=/tmp/parted-3.0-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.0.142-8232 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... Libparted is reported as version 3.0.142, but checking of the version between 2.0 and 3.0 inclusive fails. The configure script is multiplying components of the version by 100 when adding them together. $ echo 3.0.142-8232 | awk -F. '{print $1 * 10000 + $2 * 100 + $3}' 30142 So it is only allowing up to 99 commits before it is equivalent to the second minor number increasing by one. Increase the multiplication factor to 10000, allowing up to 9999 commits between releases. An order of magnitude more commits than so far seen between parted releases. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 12:29:12 -06:00
$AWK -F. '{print $1 * 1000000 + $2 * 10000 + $3}'`
if test "$LIBPARTED_FOUND_INT" -ge "$LIBPARTED_WANTED_INT"; then
have_online_resize=yes
AC_MSG_RESULT([(cached) yes])
else
have_online_resize=no
AC_MSG_RESULT([(cached) no])
fi
dnl Check if have libparted fs resize capability
if test [ ${have_old_lp_fs_resize_api} = yes -o ${have_new_lp_fs_resize_lib} = yes ]; then
AC_DEFINE([HAVE_LIBPARTED_FS_RESIZE], [1], [Define to 1 if have libparted fs resize capability])
fi
dnl gthread
PKG_CHECK_MODULES([GTHREAD], [gthread-2.0])
AC_SUBST([GTHREAD_LIBS])
AC_SUBST([GTHREAD_CFLAGS])
dnl GTKMM
PKG_CHECK_MODULES([GTKMM], [gtkmm-2.4 > 2.8])
AC_SUBST([GTKMM_LIBS])
AC_SUBST([GTKMM_CFLAGS])
2004-09-23 13:32:57 -06:00
2004-09-20 09:46:21 -06:00
dnl Check for glibmm >= 2.14 to determine availability of Glib::Regex class
AC_MSG_CHECKING([for Glib::Regex class])
PKG_CHECK_EXISTS(
[glibmm-2.4 >= 2.14.0],
[AC_DEFINE([HAVE_GLIB_REGEX], 1, [Define to 1 if glibmm provides Glib::Regex class.])
AC_MSG_RESULT([yes])
],
[AC_MSG_RESULT([no])]
)
Change to autoconf PKG_CHECK_EXISTS for set_default_icon_name() method (#762184) Previously the autoconf check for Gtk::Window::set_default_icon_name() method was a compile test because the documentation reported the method was available in gtkmm from 2.6 [1], however it wasn't available on RHEL / CentOS 5.x with gtkmm 2.10. Then commit [2] added detection and enabling of C++11 compilation, but after the above autoconf check. So on Fedora 23 the compiler based autoconf check for set_default_icon_name() method failed because C++11 compilation had not yet been enabled: > checking for Gtk::Window::set_default_icon_name method... no checking for gtk_show_uri function... yes checking for Gtk::MessageDialog::get_message_area() method... yes > checking for glibmm >= 2.45.40 which requires C++11 compilation... yes > checking whether g++ supports C++11 features by default... no > checking whether g++ supports C++11 features with -std=gnu++11... yes The gtkmm source code reveals that set_default_icon_name() method was only added in gtkmm 2.11.1 [3] so switch to a PKG_CHECK_EXISTS for this version of gtkmm. [1] gtkmm GTK::Window Class Reference https://developer.gnome.org/gtkmm/3.6/classGtk_1_1Window.html#a533d03e9b92d8ccd142ab3a44005cae4 [2] Enable C++11 compilation when using glibmm 2.45.40 and later (#756035) d6d7cb2bbf2fc381b890f63bbbf626eacfc8cdf8 [3] gtkmm NEWS file https://git.gnome.org/browse/gtkmm/tree/NEWS?h=gtkmm-2.14.0#n565 Bug 762184 - Autoconf check for C++11 comes after compile test for Gtk::Window::set_default_icon_name()
2016-02-17 07:28:35 -07:00
dnl Check for gtkmm >= 2.11.1 to determine availability of Gtk::Window::set_default_icon_name()
dnl NOTE:
Change to autoconf PKG_CHECK_EXISTS for set_default_icon_name() method (#762184) Previously the autoconf check for Gtk::Window::set_default_icon_name() method was a compile test because the documentation reported the method was available in gtkmm from 2.6 [1], however it wasn't available on RHEL / CentOS 5.x with gtkmm 2.10. Then commit [2] added detection and enabling of C++11 compilation, but after the above autoconf check. So on Fedora 23 the compiler based autoconf check for set_default_icon_name() method failed because C++11 compilation had not yet been enabled: > checking for Gtk::Window::set_default_icon_name method... no checking for gtk_show_uri function... yes checking for Gtk::MessageDialog::get_message_area() method... yes > checking for glibmm >= 2.45.40 which requires C++11 compilation... yes > checking whether g++ supports C++11 features by default... no > checking whether g++ supports C++11 features with -std=gnu++11... yes The gtkmm source code reveals that set_default_icon_name() method was only added in gtkmm 2.11.1 [3] so switch to a PKG_CHECK_EXISTS for this version of gtkmm. [1] gtkmm GTK::Window Class Reference https://developer.gnome.org/gtkmm/3.6/classGtk_1_1Window.html#a533d03e9b92d8ccd142ab3a44005cae4 [2] Enable C++11 compilation when using glibmm 2.45.40 and later (#756035) d6d7cb2bbf2fc381b890f63bbbf626eacfc8cdf8 [3] gtkmm NEWS file https://git.gnome.org/browse/gtkmm/tree/NEWS?h=gtkmm-2.14.0#n565 Bug 762184 - Autoconf check for C++11 comes after compile test for Gtk::Window::set_default_icon_name()
2016-02-17 07:28:35 -07:00
dnl The documentation says that set_default_icon_name() is available in gtkmm >= 2.6,
dnl however the code reveals that it is only available in gtkmm >= 2.11.1.
dnl * gtkmm GTK::Window Class Reference
dnl https://developer.gnome.org/gtkmm/3.6/classGtk_1_1Window.html#a533d03e9b92d8ccd142ab3a44005cae4
Change to autoconf PKG_CHECK_EXISTS for set_default_icon_name() method (#762184) Previously the autoconf check for Gtk::Window::set_default_icon_name() method was a compile test because the documentation reported the method was available in gtkmm from 2.6 [1], however it wasn't available on RHEL / CentOS 5.x with gtkmm 2.10. Then commit [2] added detection and enabling of C++11 compilation, but after the above autoconf check. So on Fedora 23 the compiler based autoconf check for set_default_icon_name() method failed because C++11 compilation had not yet been enabled: > checking for Gtk::Window::set_default_icon_name method... no checking for gtk_show_uri function... yes checking for Gtk::MessageDialog::get_message_area() method... yes > checking for glibmm >= 2.45.40 which requires C++11 compilation... yes > checking whether g++ supports C++11 features by default... no > checking whether g++ supports C++11 features with -std=gnu++11... yes The gtkmm source code reveals that set_default_icon_name() method was only added in gtkmm 2.11.1 [3] so switch to a PKG_CHECK_EXISTS for this version of gtkmm. [1] gtkmm GTK::Window Class Reference https://developer.gnome.org/gtkmm/3.6/classGtk_1_1Window.html#a533d03e9b92d8ccd142ab3a44005cae4 [2] Enable C++11 compilation when using glibmm 2.45.40 and later (#756035) d6d7cb2bbf2fc381b890f63bbbf626eacfc8cdf8 [3] gtkmm NEWS file https://git.gnome.org/browse/gtkmm/tree/NEWS?h=gtkmm-2.14.0#n565 Bug 762184 - Autoconf check for C++11 comes after compile test for Gtk::Window::set_default_icon_name()
2016-02-17 07:28:35 -07:00
dnl * gtkmm NEWS file
dnl https://git.gnome.org/browse/gtkmm/tree/NEWS?h=gtkmm-2.14.0#n565
AC_MSG_CHECKING([for Gtk::Window::set_default_icon_name() method])
PKG_CHECK_EXISTS(
[gtkmm-2.4 >= 2.11.1],
[AC_DEFINE([HAVE_SET_DEFAULT_ICON_NAME], 1,
[Define to 1 if gtkmm-2.4 provides Gtk::Window::set_default_icon_name() method.])
AM_CONDITIONAL([INSTALL_PIXMAPS_DIR], false)
AC_MSG_RESULT([yes])
],
[AM_CONDITIONAL([INSTALL_PIXMAPS_DIR], true)
AC_MSG_RESULT([no])
]
)
dnl GTKMM 2.16 needed for gtk_show_uri()
AC_MSG_CHECKING([for gtk_show_uri function])
PKG_CHECK_EXISTS(
[gtkmm-2.4 >= 2.16.0],
[AC_DEFINE([HAVE_GTK_SHOW_URI], 1, [Define to 1 if gtkmm provides gtk_show_uri() function.])
AC_MSG_RESULT([yes])
],
[AC_MSG_RESULT([no])]
)
dnl Check for gtkmm >= 2.22 to determine availability of Gtk::MessageDialog::get_message_area().
AC_MSG_CHECKING([for Gtk::MessageDialog::get_message_area() method])
PKG_CHECK_EXISTS(
[gtkmm-2.4 >= 2.22.0],
[AC_DEFINE([HAVE_GET_MESSAGE_AREA], 1,
[Define to 1 if gtkmm provides Gtk::MessageDialog::get_message_area() method.])
AC_MSG_RESULT([yes])
],
[AC_MSG_RESULT([no])]
)
need_cxx_compile_stdcxx_11=no
dnl Check for glibmm >= 2.45.40 which requires C++11 compilation.
AC_MSG_CHECKING([for glibmm >= 2.45.40 which requires C++11 compilation])
PKG_CHECK_EXISTS(
[glibmm-2.4 >= 2.45.40],
[need_cxx_compile_stdcxx_11=yes
AC_MSG_RESULT([yes])
],
[AC_MSG_RESULT([no])]
)
dnl Check for libsigc++ >= 2.5.1 which requires C++11 compilation.
AC_MSG_CHECKING([for libsigc++ >= 2.5.1 which requires C++11 compilation])
PKG_CHECK_EXISTS(
[sigc++-2.0 >= 2.5.1],
[need_cxx_compile_stdcxx_11=yes
AC_MSG_RESULT([yes])
],
[AC_MSG_RESULT([no])]
)
dnl Enable C++11 compilation only if required.
if test "x$need_cxx_compile_stdcxx_11" = xyes; then
AX_CXX_COMPILE_STDCXX_11()
fi
dnl======================
dnl check whether to build documentation - gnome-doc-utils
dnl======================
AC_ARG_ENABLE(
[doc],
AS_HELP_STRING(
[--disable-doc],
dnl Autoconf quadrigraphs '@<:@' = '[' and '@:>@' = ']'
[disable building help documentation @<:@default=enabled@:>@]),
[enable_doc=$enableval],
[enable_doc=yes]
)
AC_MSG_CHECKING([whether help documentation should be built])
if test "x$enable_doc" = xyes; then
AC_DEFINE([ENABLE_HELP_DOC], [1], [Define to 1 when help documentation is built])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
if test "x$enable_doc" = xyes; then
GNOME_DOC_INIT
else
dnl Do not care if GDU is not found
GNOME_DOC_INIT(,,[:])
fi
AM_CONDITIONAL([BUILD_HELP_DOC], [test "x$enable_doc" = xyes])
dnl======================
dnl check whether to use native libparted dmraid support
dnl======================
AC_ARG_ENABLE(
[libparted_dmraid],
AS_HELP_STRING(
[--enable-libparted-dmraid],
[use native libparted /dev/mapper dmraid support @<:@default=disabled@:>@]),
[enable_libparted_dmraid=$enableval],
[enable_libparted_dmraid=no]
)
AC_MSG_CHECKING([whether to use native libparted /dev/mapper dmraid support])
if test "x$enable_libparted_dmraid" = xyes; then
AC_DEFINE([USE_LIBPARTED_DMRAID], [1],
[Define to 1 to use native libparted /dev/mapper dmraid support])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
dnl======================
dnl check whether to enable online resize support
dnl======================
AC_ARG_ENABLE(
[online-resize],
AS_HELP_STRING(
[--enable-online-resize],
[enable online resize support @<:@default=auto@:>@]),
[enable_online_resize=$enableval],
[enable_online_resize=$have_online_resize]
)
AC_MSG_CHECKING([whether online resize support is enabled])
if test "x$enable_online_resize" = xyes; then
AC_DEFINE([ENABLE_ONLINE_RESIZE], [1], [Define to 1 if online resize is enabled])
AC_MSG_RESULT([yes])
else
AC_MSG_RESULT([no])
fi
AC_CONFIG_FILES([
2004-09-19 14:24:53 -06:00
Makefile
compose/Makefile
data/Makefile
data/icons/Makefile
doc/Makefile
help/Makefile
2004-09-19 14:24:53 -06:00
include/Makefile
src/Makefile
2004-09-20 09:46:21 -06:00
po/Makefile.in
2004-09-19 14:24:53 -06:00
])
AC_OUTPUT
dnl======================
dnl Summary
dnl======================
echo ""
echo "======================== Final configuration ==========================="
echo " Installing into prefix : $prefix"
echo ""
echo " Build help documentation? : $enable_doc"
echo ""
echo " Use native libparted dmraid support? : $enable_libparted_dmraid"
echo ""
echo " --- Features Based On Libparted Version ---"
Fix failure to recognise whole disk file systems in certain cases (#743181) When the following conditions were met GParted would fail to recognise a newly created whole disk device file system, and instead show an unknown file system filling the disk: 1) Disk was previously partitioned and contained at least one partition. 2) Using libparted version 2.0 to 3.0 inclusive. Initial status: # blkid | fgrep sdc # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 # parted /dev/sdc GNU Parted 2.4 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 107GB 107GB primary When creating the loop partition table libparted would not inform the kernel to delete the old partitions. /proc/partitions still contained the details of the old partitions. (parted) mktable loop Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Number Start End Size File system Flags (parted) quit # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 Creation of the whole disk device file system goes unnoticed by blkid because the kernel and therefore blkid's cache have stale partition information. # mkfs.xfs -f /dev/sdc # blkid | fgrep sdc NOTE: On a Linux Software RAID array, as opposed to a hard disk, blkid does notice creation of the whole disk device file system. However the kernel still has old partition details. This was fixed in libparted 3.1 by commit: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=f5c909c0cd50ed52a48dae6d35907dc08b137e88 libparted: remove has_partitions check to allow loopback partitions Fix by deleting old partitions before creating the loop table when compiled with a broken version of libparted. The GParted UI provides no feedback while a new partition table is created, and with some versions of GTK the UI become unresponsive too, so it is important to be as fast as possible. Evaluated three different methods, deleting 15 and 22 MSDOS partitions on a physical 5400 RPM hard drive using libparted 2.4: M1) Delete and commit one partition at a time. Takes up to 24 seconds to delete 15 partitions. With 22 partitions libparted always reports finding some of the partitions busy and unable to inform the kernel about the modifications. Too slow and doesn't work. M2) Delete all partitions in one go and commit once. Takes up to 1.4 seconds to delete either 15 or 22 partitions. Never removes partitions 17 and higher from the kernel. Doesn't work. M3) Write GPT table (letting libparted delete any old partitions). Takes up to 0.8 seconds to delete either 15 or 22 partitions. Fast and works. Use method 3 - write a GPT table thus using libparted code to inform the kernel of the old partition deletions. Bug 743181 - Add unpartitioned drive read-write support
2015-02-21 09:43:42 -07:00
echo " Need delete old partitions before"
echo " creating a loop table workaround? : $need_loop_delete_old_ptns_workaround"
echo " Need partition table re-read workaround? : $need_pt_reread_workaround"
echo " Supports large sector sizes (> 512 bytes)? : $support_large_sector_sizes"
echo " Have old libparted file system resizing API? : $have_old_lp_fs_resize_api"
echo " Have new libparted file system resizing LIB? : $have_new_lp_fs_resize_lib"
echo " Enable online resize support? : $enable_online_resize"
echo ""
echo " If all settings are OK, type make and then (as root) make install"
echo "========================================================================"