Changes between Version 1 and Version 2 of user-troubleshooting


Ignore:
Timestamp:
May 27, 2006 11:43:18 PM (14 years ago)
Author:
andreasw
Comment:

finished first draft

Legend:

Unmodified
Added
Removed
Modified
  • user-troubleshooting

    v1 v2  
    11= Troubleshooting =
    22
    3 First a plea:  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 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].
     3First 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].
    44
    55== Problems During Downloading ==
    66
    7 If 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'' and is able to connect the {{{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.
     7If 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'' and is able to connect the {{{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].
    88
    99For most of the COIN projects, we use the {{{externals}}} feature of subversion, which allows us to get the correct version for all dependencies for each project.  You might noticed that this slows the downloading down a bit; you just need to be patient ;)
     
    1313If 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.
    1414
    15 If you still run into trouble, the screen output or the output files {{{config.log}}} generated by {{{configure}}} might help.  It is important to know that for a COIN configuration usually several {{{configure}}} scripts are run recursively.  Therefore, you should try to find out which configuration script was the one that failed.  In the screen output, you find a line like "{{{configure: configuring in Clp}}}" when
     15If you still run into trouble, the screen output or the output files {{{config.log}}} generated by {{{configure}}} might help.  It is important to know that for a COIN configuration usually several {{{configure}}} scripts are run recursively.  Therefore, you should try to find out which configuration script was the one that failed.  In the screen output, you find a line like "{{{configure: configuring in Clp}}}" just before a new configure script is started.  The see some more detailed output than what you see on the screen, you should then look at the {{{config.log}}} file in the subdirectory that corresponds to the {{{configure}}} script that failed.  In this output file, you should go to the bottom, and then page up a little bit; at the end of the file is some summary output even if the configuration failed, and the failed test is the one just before that output.
     16
     17In 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 project.  To submit a ticket, you click on the "New Ticket" tab at the top of the project's page and fill out the information.  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.
     18
     19== Problem During Compilation ==
     20
     21If 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.