View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001654 | libmicrohttpd | build system | public | 2011-02-01 16:19 | 2011-02-15 11:19 |
| Reporter | rmmonster | Assigned To | Christian Grothoff | Due Date | |
| Priority | normal | Severity | crash | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0001654: fail to build | ||||
| Description | try to "make" after $ sudo apt-get install automake autoconf libtool make gcc g++ $ sudo apt-get install zlib1g-dev libgsf-1-dev libmpeg2-4-dev libpoppler-dev $ svn checkout https://ng.gnunet.org/svn/Extractor $ cd Extractor $ ./bootstrap $ ./configure $ make; sudo make install; make check $ sudo apt-get install gnutls-dev libcurl4-gnutls-dev $ svn co https://ng.gnunet.org/svn/libmicrohttpd $ cd libmicrohttpd/ $ ./bootstrap $ ./configure --with-gnutls --enable-messages --enable-curl as told by https://gnunet.org/node/1154 on uname -a Linux <systemname> 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux | ||||
| Additional Information | Making check in contrib make[1]: Betrete Verzeichnis '/home/<user>/<somefolder>/gnunet/libmicrohttpd/contrib' make[1]: F | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Sorry, the error pops at "make check", after $ sudo apt-get install automake autoconf libtool make gcc g++ $ sudo apt-get install zlib1g-dev libgsf-1-dev libmpeg2-4-dev libpoppler-dev $ svn checkout https://ng.gnunet.org/svn/Extractor [^] $ cd Extractor $ ./bootstrap $ ./configure $ make; sudo make install; make check $ sudo apt-get install gnutls-dev libcurl4-gnutls-dev $ svn co https://ng.gnunet.org/svn/libmicrohttpd [^] $ cd libmicrohttpd/ $ ./bootstrap $ ./configure --with-gnutls --enable-messages --enable-curl $ make $ sudo make install not as written above while trying to "make". | |
| That is very strange, daemontest should print out an error code if it fails (and it should not fail to begin with). Now, just leaving out the "make check" part will get you around the compilation/installation problem, but it would be nice if we could figure out what actually happened there with the 'make check'. Can you apt-get install valgrind and run valgrind --trace-children=yes make check &> valgrind.log (in the "libmicrohttpd" directory) and attach valgrind.log to this bugreport. Maybe it'll tell something. | |
| Here is the problem (hidden in the logs): Failed to bind to port 1080: Address already in use Error (code: 2) The test(s) simply don't pass because they use port 1080 and you're already using that one. Not an issue, you can either stop it and the tests will pass, or simply skip the "make check" step (no harm done). I'll update the docs. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-02-01 16:19 | rmmonster | New Issue | |
| 2011-02-01 16:42 | rmmonster | Note Added: 0004239 | |
| 2011-02-02 00:09 | Christian Grothoff | Note Added: 0004240 | |
| 2011-02-02 13:10 | rmmonster | File Added: valgrind.log | |
| 2011-02-03 16:34 | Christian Grothoff | Note Added: 0004242 | |
| 2011-02-03 16:34 | Christian Grothoff | Status | new => resolved |
| 2011-02-03 16:34 | Christian Grothoff | Resolution | open => fixed |
| 2011-02-03 16:34 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2011-02-15 11:19 | Christian Grothoff | Status | resolved => closed |