openafs/build-tools/libafsdep

config.guess
config.sub
git-version
install-sh
ltmain.sh
missing
mkinstalldirs
Move build support files into build-tools Now that we have a build-tools directory, move the various support files used by Autoconf and Automake into it as well to reduce clutter at the top level. Change-Id: Ieae317524d5354e3a6168507c569378f7913b05f Reviewed-on: http://gerrit.openafs.org/2432 Tested-by: Russ Allbery <rra@stanford.edu> Reviewed-by: Derrick Brashear <shadow@dementia.org> Tested-by: Derrick Brashear <shadow@dementia.org> 2010-07-15 01:29:34 +01:00			`config.guess`
			`config.sub`
Use git describe to determine build version This patch makes the configure and build system use the output from 'git describe' to determine the version of the software being built. This means that all that is necessary to create a new release is to tag the repository - removing the double sources of version information. There are a couple of fallbacks for systems which do not have git available for builds. Firstly, if a file called '.version' exists in the top level of the repository, then the version information is pulled from this file. The intention is that those packaging up git checkouts for onwards distribution will use 'git describe > .version' before producing their tarballs. Secondly, if we cannot find any version information then the version will default to 'UNKNOWN' This all mirrors the way that many others have integrated git with automake and friends - although the implementation is independent. Change-Id: I7fa4605e52181d60657ad794ca8efdb5a9fb1449 Reviewed-on: http://gerrit.openafs.org/1824 Tested-by: Derrick Brashear <shadow@dementia.org> Reviewed-by: Andrew Deason <adeason@sinenomine.net> Reviewed-by: Derrick Brashear <shadow@dementia.org> Reviewed-by: Russ Allbery <rra@stanford.edu> 2010-06-26 19:35:18 +01:00			`git-version`
Move build support files into build-tools Now that we have a build-tools directory, move the various support files used by Autoconf and Automake into it as well to reduce clutter at the top level. Change-Id: Ieae317524d5354e3a6168507c569378f7913b05f Reviewed-on: http://gerrit.openafs.org/2432 Tested-by: Russ Allbery <rra@stanford.edu> Reviewed-by: Derrick Brashear <shadow@dementia.org> Tested-by: Derrick Brashear <shadow@dementia.org> 2010-07-15 01:29:34 +01:00			`install-sh`
build: package ltmain.sh in the libafs_tree Commit 0a58d2188[1] "cf: Run AFS_LT_INIT after setting CC" moved the location of LT_INIT (libtool initialization) to a common macro, so it is now expanded in configure-libafs. This breaks the linux DKMS packaging, which uses configure-libafs to build the kernel module, since the ltmain.sh aux file is not included in the dkms package. For now, just include the ltmain.sh aux file in the libafs_tree files to fix DKMS build. Later, we should restructure the autoconf macros so the LT_INIT macro is not expanded in the configure-libafs configure script, since we do not need libtool to build the kernel module. Thanks to Alex T Prengel for reporting this issue on the openafs-info mail list. 1) 0a58d21881d7e91deccb416e8d2c272e14b412dd cf: Run AFS_LT_INIT after setting CC Change-Id: I5aec1711ab33cc619c233889db3f55f83343c4d9 Reviewed-on: https://gerrit.openafs.org/15076 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Cheyenne Wills <cwills@sinenomine.net> Reviewed-by: Benjamin Kaduk <kaduk@mit.edu> 2022-07-19 00:17:26 +01:00			`ltmain.sh`
Move build support files into build-tools Now that we have a build-tools directory, move the various support files used by Autoconf and Automake into it as well to reduce clutter at the top level. Change-Id: Ieae317524d5354e3a6168507c569378f7913b05f Reviewed-on: http://gerrit.openafs.org/2432 Tested-by: Russ Allbery <rra@stanford.edu> Reviewed-by: Derrick Brashear <shadow@dementia.org> Tested-by: Derrick Brashear <shadow@dementia.org> 2010-07-15 01:29:34 +01:00			`missing`
			`mkinstalldirs`