{section: Overview}
-As of 7.5.5, Condor uses cmake to configure the build. For instructions on building Condor prior to that, see "Building Condor prior to 7.5.5" below.
+As of version 7.5.5, Condor uses cmake to configure the build. For instructions on building Condor prior to that, see BuildingCondorOnUnixOld.
{section: Confirm the build environment}
The README.building does a decent job of covering this, but usually
@@ -75,8 +75,6 @@
{section: Configure your build}
-{subsection: Condor versions 7.5.5 and later}
-
See the new build {link: https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=BuildModernization instructions}
The common options for configuring Condor to be built the 'UW way' are passed to cmake by running =configure_uw=. This will configure the build to use the UW externals collection rather than local system libraries.
@@ -120,138 +118,10 @@
-DWITH_LIBCGROUP:BOOL=OFF
{endcode}
-{subsection: Configuring Condor 7.5.4 and earlier}
-{subsubsection: build_init}
-{code}
-% ./build_init
-{endcode}
-{subsubsection: On "native" platforms}
-On these platforms, configure should just "work":
-*:: *hppa_hpux_11*
-*:: *ia64_rhas_3*
-*:: *ppc64_sles_9*
-*:: *ppc_aix_5.2-pl5*
-*:: *ps3_ydl_5.0*
-*:: *sun4u_sol_5.9*
-*:: *x86_64_deb_5.0*
-*:: *x86_64_rhap_5*
-*:: *x86_64_rhas_3*
-*:: *x86_deb_4.0*
-*:: *x86_deb_5.0*
-*:: *x86_macos_10.4*
-*:: *x86_rhap_5*
-*:: *x86_rhas_3*
-
-{code}
-% ./configure
-{endcode}
-
-{subsubsection: On "non-native" platforms}
-On anything other than the above, *but in the same family*--e.g.,
-ia64_rhas_4, you probably want to try and build the most minimal Condor
-build possible. Configure will mostly detect the right things about
-the platform identification. If this builds, then you can start turning
-on more feature as you need them and rebuilding.
-
-{code}
-% ./configure \
- --disable-proper \
- --without-globus \
- --without-krb5 \
- --disable-full-port \
- --without-voms \
- --without-srb \
- --without-hadoop \
- --without-postgresql \
- --without-curl \
- --with-pcre \
- --disable-quill \
- --disable-gcc-version-check \
- --disable-glibc-version-check \
- --without-gsoap \
- --without-glibc \
- --without-cream \
- --without-openssl
-{endcode}
-
-{subsubsection: If ./configure has problems identifying your machine}
-If everything seems to work, but the package name on the tarballs
-are wrong after you build them, then you'll want to use
---with-platform=*os*-*arch*-*distro* as in =--with-platform=linux-ia64-sles8=.
-
-In the case where =./configure= just goes very very wrong, you may have
-to supply more arguments to configure which control deeper compilation
-aspects. These arguments are somewhat fiddly since they often define actual
-preprocessor symbols that the Condor code uses for conditional compilation.
-This means that some of these arguments can not be specified arbitrarily.
-It may be possible if you are "close" to a unix family we already support
-that you can select a combination of these that will allow the build to be
-completed.
-
-These are:
-
-*: --with-arch _{quote:<}architecture{quote:>}_
-This can only be one of:
-*:: I386
-*:: X86_64
-*:: PPC
-*:: ALPHA
-*:: CONDOR_PPC
-*:: IA64
-*:: CONDOR_PPC
-*:: HPPA
-*:: SUN4X
-*:: UNKNOWN_ARCH
-*: --with-os _{quote:<}OS Name{quote:>}_
-This can only be one of:
-*:: AIX
-*:: HPUX
-*:: LINUX
-*:: SOLARIS
-*:: DARWIN
-*: --with-kernel
-Mostly arbitrary, I don't think this is extensively used for conditional
-compilation. This will be something like 2.6.9-89.0.7.EL.cernsmp
-if on linux.
-*: --with-os_version _{quote:<}version{quote:>}_
-This can only be one of:
-*:: OSX_10_4
-*:: OSX_UNKNOWN
-*:: AIX5
-*:: AIXUNKNOWN
-*:: HPUX10
-*:: HPUX11
-*:: SOLARIS26
-*:: SOLARIS27
-*:: SOLARIS28
-*:: SOLARIS29
-*:: FREEBSD[5-7]
-*:: LINUX_TAO1
-*:: LINUX_TAO_UNKNOWN
-*:: LINUX_YD30
-*:: LINUX_YD50
-*:: LINUX_YD_UNKNOWN
-*:: LINUX_GENTOO1.12.11.1
-*:: LINUX_GENTOO_UNKNOWN
-*:: LINUX_FC[1-N]
-*:: LINUX_RH72
-*:: LINUX_RH80
-*:: LINUX_RH9
-*:: LINUX_SLES81
-*:: LINUX_SLES9
-*:: LINUX_SuSE_UNKNOWN
-*:: LINUX_DEBIAN40
-*:: LINUX_DEBIAN50
-*:: LINUX_DEBIAN_UNKNOWN
-*:: LINUX_UNKNOWN
-*: --with-sysname
-This can be arbitrary.
{section: Building your source}
-{subsection: Condor versions 7.5.5 and later}
-
While there are many targets to =make=, I will only describe the two that are
most likely what you want.
@@ -265,38 +135,16 @@
UW download site for the machine upon which you are building.
-{subsection: Condor versions 7.5.4 and older}
-Before 7.5.5, Condor used configure + imake to generate makefiles.
-
-While there are many targets to =make=, I will only describe the two that are
-most likely what you want.
-
-{subsubsection: release}
-=make release= will make a set of executable binaries and place them in
-=release_dir/=. They will be dynamically linked and suitable for testing
-by pointing a $(RELEASE_DIR) at it from a condir_configure file.
-{subsubsection: public}
-=make public= will produce packages similar to what you can download from the
-our download site for the machine upon which you are building. If you ever
-see two or more dashes in a row in the file name, it means they are named wrong
-and you might have to use =--with-platform= on configure and try again.
{section: Running the developer test suite}
{subsection: Building the tests}
-{subsubsection: Condor 7.5.5 and later}
{code}
$ make tests
{endcode}
-{subsubsection: Condor 7.5.4 and earlier}
-{code}
-$ cd src/condor_tests
-$ make
-{endcode}
-
{subsection: Running the tests}
{code}
$ cd src/condor_tests
