ports/net-p2p/ktorrent - can't compile

Laurence Sanford lauasanf at wilderness.homeip.net
Mon Aug 28 01:28:58 UTC 2006


Just looking for pointers, as I've seen them here from time to time when 
a port won't build. I'm using the following command line:

portupgrade -NR ktorrent

All dependencies build successfully. The ktorrent build fails like this:

/usr/X11R6/bin/moc ./peermanager.h -o peermanager.moc
source='peermanager.cpp' object='peermanager.lo' libtool=yes \
        depfile='.deps/peermanager.Plo' 
tmpdepfile='.deps/peermanager.TPlo' \
        depmode=gcc3 /bin/sh ../../admin/depcomp \
        /bin/sh /usr/local/bin/libtool --silent --mode=compile --tag=CXX 
c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I./.. -I/usr/local/include 
-I/usr/X11R6/include  -I/usr/local/include  -D_THREAD_SAFE -pthread 
-DQT_THREAD_SUPPORT   -I/usr/local/include -I/usr/local/include  
-I/usr/X11R6/include -D_GETOPT_H -D_THREAD_SAFE   -Wnon-virtual-dtor 
-Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -O2 
-fno-strict-aliasing -pipe -fno-exceptions -fno-check-new -fno-common 
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT 
-DQT_NO_TRANSLATION -fexceptions   -c -o peermanager.lo `test -f 
'peermanager.cpp' || echo './'`peermanager.cpp
In file included from ./../mse/encryptedauthenticate.h:25,
                 from peermanager.cpp:34:
./../mse/bigint.h:26:17: gmp.h: No such file or directory
In file included from ./../mse/encryptedauthenticate.h:25,
                 from peermanager.cpp:34:
./../mse/bigint.h:93: error: `mpz_t' does not name a type
gmake[3]: *** [peermanager.lo] Error 1
gmake[3]: Leaving directory 
`/usr/ports/net-p2p/ktorrent/work/ktorrent-2.0.1/libktorrent/torrent'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory 
`/usr/ports/net-p2p/ktorrent/work/ktorrent-2.0.1/libktorrent'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory 
`/usr/ports/net-p2p/ktorrent/work/ktorrent-2.0.1'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/net-p2p/ktorrent.


Anyone run into this problem and worked around it?


More information about the freebsd-questions mailing list