Changes between Version 4 and Version 5 of pm-get-autotools


Ignore:
Timestamp:
Sep 8, 2006 3:17:29 PM (14 years ago)
Author:
lou
Comment:

Provide a bit more explanation for why it's necessary to install autotools from FSF source

Legend:

Unmodified
Added
Removed
Modified
  • pm-get-autotools

    v4 v5  
    11= Using the Correct Version of the Autotools =
    22
    3 We ask that every developer in COIN use the same version of the autotools.  This is necessary in order to ensure that the custom defined COIN additions work.  Also, this way we guarantee that each developer generates the same output files, which avoids the mess that would occur if this were not the case.
     3We ask that every developer in COIN use the same distribution of the same version of the autotools.  This is necessary in order to ensure that the custom defined COIN additions work.  Also, this way we guarantee that each developer generates the same output files, which avoids the mess that would occur if this were not the case. Specifically, the precompiled versions of autotools included in packaged distributions often contain small modifications to the m4 macros that are supplied with autoconf, automake, and libtool. These differences make their way into generated Makefiles and configure scripts. Allowing these differences to creep into the repository will result in chaos. For this reason, we ask that you download the original source packages for the autotools from GNU and build and install them by hand on your system.
    44
    5 Since precompiled versions of the tools often differ (they may incorporate changes from the basic GNU release), we ask that you download the original source packages for the autotools from GNU and install them by hand on your system.
    6 
    7 '''We recommend that you install the self-compiled tools in your $HOME directory''', i.e., in {{{$HOME/bin}}}, and other configuration files in {{{$HOME/share}}}.  This can be done by:
     5'''We recommend that you install the self-compiled tools in your $HOME directory''', ''i.e.'', in {{{$HOME/bin}}}, and other configuration files in {{{$HOME/share}}}.  This can be done by:
    86{{{
    97mkdir tmp
     
    2927rm -fr tmp
    3028}}}
    31 Alternatively, you may install them (from the GNU source, not as binaries!!!) in another directory, (such as {{{/usr/local}}}), but then you will have to set the environment variable {{{AUTOTOOLS_DIR}}} to this directory in your shell's login file (e.g., {{{~/.bashrc}}} or {{{~/.cshrc}}}).  Only do this, if you actually installed the autotools into that directory yourself from the GNU source code, otherwise you will encounter many conflicts!!!
     29If you would prefer to place them in another directory, you will need to set the environment variable {{{AUTOTOOLS_DIR}}} to this directory in your shell's login or shell initialisation file (e.g., {{{~/.profile}}}, {{{~/.bashrc}}}, {{{~/.login}}}, or {{{~/.cshrc}}}).  '''Do not specify a standard system directory''' (''e.g.'', {{{/usr/local}}}) unless you actually installed the autotools into that directory yourself from the GNU source code, otherwise you will encounter many conflicts!!!
    3230
    3331The tools that you should install are:
     
    4745Make sure you get the correct version for each tool, as indicated in the list above.
    4846
    49 After they are installed, you also need to '''ensure that your $PATH variable is set so that your self-installed versions of the tools are the ones that are actually used.'''
     47After they are installed, you also need to '''ensure that your {{{$PATH}}} variable is set so that your self-installed versions of the tools are the ones that are actually used.'''
    5048
    5149When you run {{{configure}}} in your local copy with the {{{--enable-maintainer-mode}}} flag (which you should do as a developer), it will test to see if the above conditions are met and will fail if they are not met.