mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-09-13 19:25:13 +00:00
56c56b3bf8
The colors are not based on the semantics of the message but rather
on the message itself. This means that the default human-perceived
semantics (red = bad, green = good) don't really apply and spotting a
color does not mean anythting.
This is amplified by the sheer amount of output which configure produces
and the fact that some of the messages have negative semantics or
additional output.
In case of any problem the user will have to go through everything
anyways as spotting a red or yellow line has 0 information value.
Here are a few examples:
1) some 'no' messages are not a problem:
checking minix/config.h presence... no
2) some 'no' messages are actually positive:
checking for special C compiler options needed for large files... no
3) in some cases a 'yes' would mean that something is broken or needs
workaround
checking whether stat file-mode macros are broken... no
checking whether wint_t is too small... no
checking whether stdint.h predates C++11... no
checking whether the inttypes.h PRIxNN macros are broken... no
checking whether clang gives bogus warnings for -Wdouble-promotion... no
checking whether gettimeofday clobbers localtime buffer... no
4) due to string match based colors extra text makes messages yellow
checking for a traditional french locale... none
checking for working nanosleep... no (mishandles large arguments)
checking for library containing gethostbyname... none required
checking whether mbrtowc handles incomplete characters... (cached) guessing yes
5) in some cases the yes/no is very context dependant
checking whether pthread_rwlock_rdlock prefers a writer to a reader... no
checking whether this build is done by a static analysis tool... no
6) detected paths to binaries and libs are yellow despite being present
checking for objdump... objdump
checking for atomic ops implementation... gcc
As of the reasons above I don't think the colorization of the configure
output helps users or developers to debug the build process and
thus is not worth the extra code or output clutter.
This reverts commit
|
||
|---|---|---|
| .. | ||
| virt-acl.m4 | ||
| virt-apparmor.m4 | ||
| virt-arg.m4 | ||
| virt-atomic.m4 | ||
| virt-attr.m4 | ||
| virt-audit.m4 | ||
| virt-bash-completion.m4 | ||
| virt-blkid.m4 | ||
| virt-capng.m4 | ||
| virt-chrdev-lock-files.m4 | ||
| virt-compile-pie.m4 | ||
| virt-compile-warnings.m4 | ||
| virt-curl.m4 | ||
| virt-dbus.m4 | ||
| virt-debug.m4 | ||
| virt-default-editor.m4 | ||
| virt-devmapper.m4 | ||
| virt-dlopen.m4 | ||
| virt-driver-bhyve.m4 | ||
| virt-driver-esx.m4 | ||
| virt-driver-hyperv.m4 | ||
| virt-driver-interface.m4 | ||
| virt-driver-libvirtd.m4 | ||
| virt-driver-libxl.m4 | ||
| virt-driver-lxc.m4 | ||
| virt-driver-modules.m4 | ||
| virt-driver-network.m4 | ||
| virt-driver-openvz.m4 | ||
| virt-driver-phyp.m4 | ||
| virt-driver-qemu.m4 | ||
| virt-driver-remote.m4 | ||
| virt-driver-test.m4 | ||
| virt-driver-vbox.m4 | ||
| virt-driver-vmware.m4 | ||
| virt-driver-vz.m4 | ||
| virt-dtrace.m4 | ||
| virt-external-programs.m4 | ||
| virt-firewalld-zone.m4 | ||
| virt-firewalld.m4 | ||
| virt-fuse.m4 | ||
| virt-gluster.m4 | ||
| virt-gnutls.m4 | ||
| virt-hal.m4 | ||
| virt-host-validate.m4 | ||
| virt-init-script.m4 | ||
| virt-lib.m4 | ||
| virt-libiscsi.m4 | ||
| virt-libnl.m4 | ||
| virt-libpcap.m4 | ||
| virt-libssh.m4 | ||
| virt-libxml.m4 | ||
| virt-linker-no-indirect.m4 | ||
| virt-linker-no-undefined.m4 | ||
| virt-linker-relro.m4 | ||
| virt-loader-nvram.m4 | ||
| virt-login-shell.m4 | ||
| virt-macvtap.m4 | ||
| virt-netcf.m4 | ||
| virt-nls.m4 | ||
| virt-nss.m4 | ||
| virt-numactl.m4 | ||
| virt-numad.m4 | ||
| virt-nwfilter.m4 | ||
| virt-openwsman.m4 | ||
| virt-parted.m4 | ||
| virt-pciaccess.m4 | ||
| virt-pm-utils.m4 | ||
| virt-polkit.m4 | ||
| virt-pthread.m4 | ||
| virt-readline.m4 | ||
| virt-result.m4 | ||
| virt-sanlock.m4 | ||
| virt-sasl.m4 | ||
| virt-secdriver-apparmor.m4 | ||
| virt-secdriver-selinux.m4 | ||
| virt-selinux.m4 | ||
| virt-ssh2.m4 | ||
| virt-storage-dir.m4 | ||
| virt-storage-disk.m4 | ||
| virt-storage-fs.m4 | ||
| virt-storage-gluster.m4 | ||
| virt-storage-iscsi-direct.m4 | ||
| virt-storage-iscsi.m4 | ||
| virt-storage-lvm.m4 | ||
| virt-storage-mpath.m4 | ||
| virt-storage-rbd.m4 | ||
| virt-storage-scsi.m4 | ||
| virt-storage-sheepdog.m4 | ||
| virt-storage-vstorage.m4 | ||
| virt-storage-zfs.m4 | ||
| virt-sysctl.m4 | ||
| virt-tls-priority.m4 | ||
| virt-udev.m4 | ||
| virt-virtualport.m4 | ||
| virt-win-common.m4 | ||
| virt-win-cygwin.m4 | ||
| virt-win-mingw.m4 | ||
| virt-win-symbols.m4 | ||
| virt-win-windres.m4 | ||
| virt-wireshark.m4 | ||
| virt-xdr.m4 | ||
| virt-yajl.m4 | ||