checking signedness of mincore parameter... configure: error: failed, do *not* attempt to use --disable-mincore unless you are running Win32.

[Dave T]

I am using Ubuntu 6.06LTS and am trying to compile the latest version of rtorrent since it ships with 4.2 and only 4.3 is available from apt-get. But during the ./configure script it breaks with this error. Am I possibly missing something? I am fairly sure I got all the .dev packages it needs. This is on g++ version4.

[rakshasa]

Post the part of config.log that shows the compilation error for the test.

[dy]

i had same error. configuration cant find the g++. check your /usr/bin for that binary.

[Dave T]

configure:15861: checking signedness of mincore parameter configure:15871: g++ -c -O2 -Wall -g -DDEBUG -I/usr/include/sigc++-2.0 -I/usr ./configure: line 15872: g++: command not found configure:15877: $? = 127 configure: failed program was: | #include <sys/types.h> | #include <sys/mman.h> | void f() { mincore((char*)0, 0, (unsigned char*)0); } | configure:15918: g++ -c -O2 -Wall -g -DDEBUG -I/usr/include/sigc++-2.0 -I/usr ./configure: line 15919: g++: command not found configure:15924: $? = 127 configure: failed program was: | #include <sys/types.h> | #include <sys/mman.h> | void f() { mincore((char*)0, 0, (char*)0); } | configure:15958: error: failed, do *not* attempt to use --disable-mincore unles

You guys rock. Thanks. I installed g++ 4.0 from the Ubuntu add/remove, and it was called g++-4.0 so of course it could not be found. A link called g++ to the compiler did the trick. Sorry for bothering you folks.

[anonymous]

OK, I am missing something. Configure works, but the make script is called Makefile, no biggie but 'sh ./Makefile' does not function. The 'install' document is a little behind the current state of the project. If you folks can help me rtorrent working in Ubuntu here I can rewrite it to work with the state of things.

What am I missing to get Makefile working? I see that 'libtool' and 'missing' are both manipulated by configure. But what is the next step here, is there a page in the rtorrent project site I need to read? I will RTFM if there is one.

Dave

[anonymous]

Just type "make" to compile it, and "make install" to install it. You'll need GNU make for that of course.

[Dave T]

Ok, I was WAY too tired. I was trying ./make, and of course should have been sleeping instead. Thanks all. Pls kill this ticket.

[artifex@freemail.hu]

Sorry for reopening but with libtorrent rev768 on FreeBSD-6.10-p10 it happen again. I am using for compile:

Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.4 [FreeBSD] 20050518

config.log:

configure:22436: checking signedness of mincore parameter
configure:22446: g++ -c -pipe -O2 -DNDEBUG -fvisibility=hidden -I/usr/local/include   -I/usr/local/include/sigc++-2.0 -I/usr/local/lib/sigc++-2.0/include    conftest.cc >&5
cc1plus: error: unrecognized command line option "-fvisibility=hidden"
configure:22452: $? = 1
configure: failed program was:
| #include <sys/types.h>
|       #include <sys/mman.h>
|       void f() { mincore((char*)0, 0, (unsigned char*)0); }
|
configure:22493: g++ -c -pipe -O2 -DNDEBUG -fvisibility=hidden -I/usr/local/include   -I/usr/local/include/sigc++-2.0 -I/usr/local/lib/sigc++-2.0/include    conftest.cc >&5
cc1plus: error: unrecognized command line option "-fvisibility=hidden"
configure:22499: $? = 1
configure: failed program was:
| #include <sys/types.h>
|           #include <sys/mman.h>
|           void f() { mincore((char*)0, 0, (char*)0); }
|
configure:22533: error: failed, do *not* attempt to use --disable-mincore unless you are running Win32.

If I remove -fvisibility=hidden from configure script everything works fine.

[anonymous]

-fvisibility=hidden is only available on gcc 4+ but the configure script fails to check that

to workaround, comment out the following line in libtorrent/configure.ac:

CC_ATTRIBUTE_DEFAULT([CXXFLAGS="$CXXFLAGS -fvisibility=hidden"])

[rakshasa]

This should be a new bug report, not re-opening one that isn't actually related. Will be fixed in the next commit.