Changes between Version 6 and Version 7 of user-troubleshooting


Ignore:
Timestamp:
Oct 25, 2006 2:58:15 PM (13 years ago)
Author:
andreasw
Comment:

added warning about environment variables, and added subheaders

Legend:

Unmodified
Added
Removed
Modified
  • user-troubleshooting

    v6 v7  
    33The very first thing to do is have a look at the [wiki:current-issues current issues page] and see if your problem is known and if workarounds are posted there.
    44
     5
    56The next is a plea to be considerate:  The project managers for the packages provided on COIN try to make the usage of their code easy and will try to help in case you run into problems.  However, before contacting the project manager (via the project's mailing list or by submitting a trouble ticket), '''please make sure you carefully read and followed the instructions''' given on the project's home page and on these wiki pages for [http://projects.coin-or.org/BuildTools BuildTools].
    67
    78== Problems During Downloading ==
     9
     10=== Using the correct version of subversion ===
    811
    912If you want to use subversion from the command line (with the {{{svn}}} program), you need to '''make sure that you have a version of {{{svn}}} that is able to use the SSL layer''', i.e., that it is able to connect to {{{https://...}}} URLs.  You can find out if your version of {{{svn}}} supports this by typing {{{svn --version}}}.  If it says "{{{handles 'https' scheme}}}," you are fine.  Otherwise, you need to obtain a different version, or compile the {{{svn}}} executable yourself.  In that case, make sure you specify {{{--with-ssl}}} when you run {{{configure}}} for subversion.  For information on how to obtain subversion, click [wiki:user-download here]. ''Note: We are successfully using '''subversion version 1.3.1''' to download the code; older versions might not work properly.''
     
    1215
    1316== Problems During Configuration ==
     17
     18=== How to read the config.log file ===
    1419
    1520If you run {{{configure}}} and it doesn't complete with "{{{configuration of XXX successfull}}}", something went wrong.  There is no point in trying to do a {{{make}}} anyway, since the Makefiles will not have been created yet.  Make sure you read the [wiki:user-configure Preparing the compilation] information provided in these wiki pages.
     
    6772In case you are not able to resolve the problem on your own and want to ask for help, you should '''submit a ticket''' at the Trac home page for the COIN project that doesn't configure properly.  To submit a ticket, you click on the "New Ticket" tab at the top of the project's page and fill out the information (after you registered and logged into the Trac system).  It might be a good idea to attach the {{{config.log}}} file that represents your failed configuration run.  You should '''provide your email address''' in the first box of the page that comes up, so that you will be notified of changes to the ticket, and so that someone might be able to contact you in case more information is required.
    6873
     74=== Be aware of environment variables ===
     75
     76Note that the {{{configure}}} script also looks at certain environment variables to determine values.  For example, all the variables listed as [wiki:user-configure#VariableArgumentsforconfigure variable arguments for configure], such as compiler names and options, are picked up by the {{{configure}}} script.  Also, some COIN specific options, such as {{{---with-library-lib}}} can be replaced by environment variables; for example, {{{CPXINCDIR}}} might be defined in your environment from an earlier version of COIN, and it is understood now as the argument of {{{--with-cplex-lib}}}.
     77
    6978== Problems During Compilation ==
    7079
     80=== Output of make ===
     81
    7182If you run {{{make}}} to compile the code, you will see a lot of output.  Since most COIN projects use the GNU autotools, the output might be somewhat complicated, but in principle you see every command that is executed.  If the compilation fails, it might be a good idea to have a '''careful look at the error message and at the source file that could not be compiled'''.  You might be able to resolve the problem by adapting the source code; in that case it would be nice if you could '''let the project manager know about your bug fix''' by submitting a ticket that includes the changes you made.  If you are not able to resolve the problem on your own and want to ask for help, you can '''submit a ticket''', and include the output of {{{make}}} and also the {{{config.log}}} file of the COIN sub-project where the failure occurs.  The {{{config.log}}} file includes information about your environment that might be helpful to track the problem.