summaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Typo in configuration helpedupont2019-02-011-1/+1
|
* build-sys: fix crypt() detection without -lcryptJohannes Nixdorf2019-01-231-1/+4
| | | | | | | | | | The check tested whether code using crypt() links without -lcrypt, but didn't set have_crypt to yes if it succeeded. This fixes the check erroneously failing when compiling against musl libc. Signed-off-by: Johannes Nixdorf <mixi@shadowice.org>
* build-sys: do not require crypt()Karel Zak2018-12-031-1/+5
| | | | | | | The function is necessary only for newgrp and sulogin. Addresses: https://github.com/karelzak/util-linux/issues/584 Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: do not require dirfd()Karel Zak2018-12-031-4/+6
| | | | | | | The dirfd() is required on many places, but it should not be required for all utils by ./configure.ac. Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: improve error messageKarel Zak2018-12-031-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lib/timer: add fallback if timer_create() not availableKarel Zak2018-12-031-0/+4
| | | | | | | | | | | | | * add struct ul_timer as API abstraction to hide differences between timer_create() and setitimer() * add setitimer() detection to ./configure.ac * add fallback code to use setitimer() if timer_create() not available (for example on OSX) Addresses: https://github.com/karelzak/util-linux/issues/584 Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: make sure HAVE_TIMER_CREATE definedKarel Zak2018-12-031-1/+3
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: make fdisk, sfdisk, cfdisk optional (enabled by default)Carlos Santos2018-11-291-3/+11
| | | | | | | | | | Useful for embedded systems, on which only few utilities are required. [kzak@redhat.com: - rename to --disable-fdisks - use $enable_{c,s,}fdisk in code] Signed-off-by: Carlos Santos <casantos@datacom.com.br> Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.33)Karel Zak2018-11-061-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.33-rc2)Karel Zak2018-10-191-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add USE_LIBMOUNT_SUPPORT_NAMESPACESKarel Zak2018-10-051-3/+12
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.33-rc1)Karel Zak2018-09-251-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: default to /lib64 for ${exec_prefix}/lib64Karel Zak2018-09-041-0/+1
| | | | | | | | We already default to /lib for the default $exec_prefix, but the current configure does not care about /lib64 although the use-case is exactly same as for /lib. Signed-off-by: Karel Zak <kzak@redhat.com>
* su: add --whitelist-environmentKarel Zak2018-08-151-0/+1
| | | | | | | | | | | | | | | | | | | * usable with --login to whitelist specified environment variables * the list is ignored for the core variables like HOME, SHELL, USER, LOGNAME and PATH (su --login always resets these variables) Note that su(1) requires password and after successful authentication user has full control over the session, so he can set arbitrary environment variables. The whitelist makes things more user friendly only. The patch removes unnecessary optimization when allocate environ[]. It seems better to keep all in glibc hands and just reset the environment array only. Addresses: https://github.com/karelzak/util-linux/issues/221 Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add -Wdiscarded-qualifiersKarel Zak2018-07-201-0/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add -Wno-cast-function-type for pythonKarel Zak2018-07-181-0/+4
| | | | | | | | | | | | | | | | | libmount/python/pylibmount.c:158:19: warning: cast between incompatible function types from ‘PyObject * (*)(PyObject *)’ {aka ‘struct _object * (*)(struct _object *)’} to ‘PyObject * (*)(PyObject *, PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object *)’} [-Wcast-function-type] This is generic problem in all Python C code and gcc v8. The another possible (and probably more correct) way is to add unused argument to all API functions. Unfortunately, this solution is pretty invasive. The question is if gcc is not too paranoid in this case. For more details see https://bugs.python.org/issue33012. It seems Python guys also prefer CFLAGS modification for now. Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: cleanup --with/--without help stringsKarel Zak2018-05-031-6/+6
| | | | | | | | --with- means disabled by default or modify any default path --without- means enabled by default Reported-by: L A Walsh <lkml@tlinx.org> Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: --without-systemd disables --with-systemdsystemunitdirKarel Zak2018-05-031-3/+11
| | | | | | | Make sure --without-systemd disables also --with-systemdsystemunitdir. Reported-by: L A Walsh <lkml@tlinx.org> Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: extend "Could not locate the pkg-config" error messageKarel Zak2018-04-301-1/+1
| | | | | Addresses: https://github.com/karelzak/util-linux/issues/631 Signed-off-by: Karel Zak <kzak@redhat.com>
* Merge branch 'choom'Karel Zak2018-04-161-0/+4
|\
| * choom: new command to adjust OOM-killer score valueKarel Zak2018-04-161-0/+4
| | | | | | | | | | | | | | | | | | Let's provide command line tool, man page with OOM description and bash-completion. It seems better than force end-users to use "echo" to /proc. Addresses: https://github.com/karelzak/util-linux/issues/609 Signed-off-by: Karel Zak <kzak@redhat.com>
* | rename: test availability of __fpurge() and fpurge()G.raud Meyer2018-04-091-0/+2
|/
* build-sys: release++ (v2.32)Karel Zak2018-03-211-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* fstrim: fix fs.h and mount.h collisionKarel Zak2018-03-201-1/+10
| | | | | | | | | Unfortunately, old version of the file linux/fs.h defines MS_* macros, so the file cannot be included together with sys/mount.h. We include sys/mount.h from libmount.h now. Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.32-rc2)Karel Zak2018-03-011-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: forgot update NEWS for v2.32-rc1Karel Zak2018-02-221-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* misc: fix typos using codespellRuediger Meier2018-02-161-8/+8
| | | | | | Some more funny typos, please review carefully. Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
* build-sys: disable bz2 tarball and fix some am warningsRuediger Meier2018-02-151-1/+2
| | | | | | | | | | | | | | | | | | | Nobody needs the .bz2 tarball. We dont't even upload it to kernel.org. BTW we fix dozens of these automake warnings: automake-1.13/am/ltlibrary.am: warning: 'libblkid.la': linking libtool libraries using a non-POSIX automake-1.13/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac' So we can remove -Wno-portability. The only warning left is this last GNU-make'ism which somebody may fix when reading it: sys-utils/Makemodule.am:191: warning: addprefix sys-utils/,$(SETARCH_LINKS: non-POSIX variable name sys-utils/Makemodule.am:191: (probably a GNU make extension) Makefile.am:90: 'sys-utils/Makemodule.am' included from here Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
* build-sys: (configure) fix bashismsMike Frysinger2018-01-301-4/+4
| | | | | | The `test` command only recognizes =, not ==. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* cal: Use ALTMON_* correctlyRafal Luzynski2018-01-221-0/+53
| | | | | | | | | | | cal: use ALTMON_* and _NL_ABALTMON_* constants to display months in a standalone form correctly. These constants have just been newly added to glibc. ALTMON_x has been used in BSD family since 1990s and has been accepted as the future POSIX extension. _NL_ABALTMON_* is exclusively a GNU extension but it is expected to be added to POSIX in future. More info: https://sourceware.org/bugzilla/show_bug.cgi?id=10871
* build-sys: don't check for swapon() number of argumentsKarel Zak2017-12-181-14/+4Star
| | | | | | | | The syscall swapon() with two arguments is supported since Linux 1.3.2 and it's really long time ago... Let's assume that all libc header files have been already fixed. Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: lsns requires libmountKarel Zak2017-11-271-0/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lsns: add netnsid columnMasatake YAMATO2017-11-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Linux network subsystem assigns an unique integer to a network namespace. term0# ip netns add UTIL-LINUX-LSNS-TEST-NS term0# ip netns list UTIL-LINUX-LSNS-TEST-NS term0# ip link add name lsns-vetha type veth peer name lsns-vethb term0 # ip link set lsns-vethb netns UTIL-LINUX-LSNS-TEST-NS term0# ip netns list UTIL-LINUX-LSNS-TEST-NS (id: 0) term0# ip link show dev lsns-vetha 230: lsns-vetha@if229: <BROADCAST,MULTICAST> mtu 1500 qdisc noop ... link/ether 3e:27:68:ba:b3:95 brd ff:ff:ff:ff:ff:ff link-netnsid 0 In this example 0 is assigned to UTIL-LINUX-LSNS-TEST-NS net namespace. The name, UTIL-LINUX-LSNS-TEST-NS, and it semantics is given and defined by iproute2 in userland; and nothing to do with util-linux. However, the id, 0, is managed in linux kernel. If lsns can show the ids, it helps users understand the state of network namespaces. This commit adds NETNSID column to the output. Here is an example of session: term0# ip netns exec UTIL-LINUX-LSNS-TEST-NS cat (Open another terminal) term1# ./lsns --type net NS TYPE NPROCS PID USER NETNSID COMMAND 4026531993 net 383 1 root unassigned /usr/lib/systemd/... 4026532433 net 1 1219 rtkit unassigned /usr/libexec/rtkit-daemon 4026532562 net 1 18201 root 0 cat 0 is shown as NETNSID for the cat process. For the initial name space, "unassigned" is printed. For the namespaces other type than net, "n/a" is printed. If an error occurred during getting the id, "n/a" is printed. Changes in V2: * Remove wrongly used & operators. * Make netnsid field empty if value for the column is not available. Suggested by Karel Zak. * Remove redundant condtion for checking the avaiablebility of netlink socket. Suggested by Karel Zak. Signed-off-by: Masatake YAMATO <yamato@redhat.com>
* build-sys: add --enable-asan and --memcheck-asan for testsKarel Zak2017-11-231-0/+11
| | | | | | | | | The command ./configure --enable-asan adds -fsanitize=address to the compiler command line. In the regression tests leaks detection is disabled by default. You have to use --memcheck-asan on test command line to enable. Signed-off-by: Karel Zak <kzak@redhat.com>
* libmount: use eacess() rather than open() to check mtab/utabKarel Zak2017-10-201-0/+1
| | | | | | | | | The open() syscall is probably the most strong way how to check write accessibility in all situations, but it's overkill and on some paranoid systems with enabled audit/selinux. It fills logs with "Permission denied" entries. Let's use eaccess() if available. Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.31)Karel Zak2017-10-191-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.31-rc2)Karel Zak2017-10-031-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: release++ (v2.31-rc1)Karel Zak2017-09-221-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: make rfkill optional (and enabled by default)Karel Zak2017-09-191-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add libtinfow checkKarel Zak2017-09-191-15/+9Star
| | | | | | | | | | | | It seems some systems differentiate between tinfo and tinfow. And it seems that mix ncursesw and tinfo (wide vs. non-wide char) is problem for the systems. Note that for example Fedora have ncursesw as well as ncurses, but only one tinfo library. So, we need fallback this scenario. Reported-by: Stanislav Brabec <sbrabec@suse.cz> Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add --disable-rfkillKarel Zak2017-08-311-1/+7
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* rfkill: use libsmartcols outputSami Kerola2017-08-301-0/+1
| | | | | | | This also makes the rfkill to output status when executed without arguments. That is believed ot be more useful than usage() output. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* rfkill: make programming style to match util-linux projectSami Kerola2017-08-301-0/+1
| | | | | | | | Use the usual facilities, add translation strings, move global variables at the beginning of the file, make usage() look as expected, add standard command-line option parsing. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* rfkill: make command to build in util-linux projectSami Kerola2017-08-301-0/+3
| | | | | | | After this commit the command merely builds, but does not confirm style used in util-linux project. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* build-sys: define dependence between chsh and getusershellKarel Zak2017-08-301-0/+2
|
* build-sys: support ncursesw without headers in ncursesw/ directoryKarel Zak2017-08-011-2/+16
| | | | | | | | | | | | Let's check always for alone ncurses.h and term.h if the preferred variant with ncursesw/ subdirectory is not available. The patch also minimize number of HAVE_...NCURSES_H macros in config.h. We don't need to check for ncurses.h if ncurses/ncurses.h is available. Reported-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Karel Zak <kzak@redhat.com>
* build: use --runstatedir instead of --localstatedirAndreas Henriksson2017-07-311-7/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The util-linux code was previously aligned to use @localstatedir@ and the util-linux build system was set to override the default to use /run. Current GNU Coding Standards introduced the @runstatedir@ variable for this purpose. Lets use that instead. The GNU default for @runstatedir@ is ${localstatedir}/run so util-linux still override the default to be /run to preserve the status quo from before. The only difference is that you'll now pass --runstatedir to override the location on the command line instead of --localstatedir. (FWIW, Debhelper in compat 11 will automatically start passing --runstatedir=/run to all autotools configured builds. It already passes --localstatedir=/var (to avoid it ending up with the GNU default /usr/local/var) which breaks the util-linux build system code that tries to default it to /run. This change will thus allow util-linux and debhelper to work better together and avoid the need for a package-specific override.) Relevant historic commits: * commit 07a16b9d1e5a48550a0d19abb9a900853433ffa2 "build-sys: change --localstatedir to /run" * commit 80c51185d50f00a2701f9379f10fc48a0f885dfc "uuidd: use run configured state directory" * commit 01c5b787947aeaffc7e56000827e3edefa357c59 "agetty: use configured run state directory" [kzak@redhat.com: - add $runstatedir fallback for autoconf < 2.70 - check for unmodified $localstatedir] CC: Sami Kerola <kerolasa@iki.fi> Signed-off-by: Andreas Henriksson <andreas@fatal.se> Signed-off-by: Karel Zak <kzak@redhat.com>
* whereis: include native multiarch path in lib search pathsAndreas Henriksson2017-07-311-0/+5
| | | | | | | | | | | | | | | | | This includes atleast the native multiarch path in the paths to search. (Maybe also other multiarch paths should also be searched? But atleast this is a first step.) Before this change (on Debian): $ whereis libc libc: /usr/share/man/man7/libc.7.gz After this change: $ whereis libc libc: /usr/lib/x86_64-linux-gnu/libc.so /usr/lib/x86_64-linux-gnu/libc.a /usr/share/man/man7/libc.7.gz Addresses: https://bugs.debian.org/856968 Signed-off-by: Andreas Henriksson <andreas@fatal.se>
* ldattach: simplify debugging function when vwarnx(3) is availableSami Kerola2017-07-151-0/+1
| | | | | | | The vwarnx(3) is probably not available in all libc implementations, in such cases use the earlier printout as a fallback. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* reset: remove script from the packageSami Kerola2017-07-151-8/+0Star
| | | | | | | This script requires ncurses to work, and the ncurses provides reset so there should not be need to keep this script hanging around. Signed-off-by: Sami Kerola <kerolasa@iki.fi>