|
From: David B. <bo...@wa...> - 2006-02-11 10:06:27
|
Hi Jon, I use a Gentoo box too ( :-) ) So my config.log looks like yours... Le vendredi 10 f=C3=A9vrier 2006 =C3=A0 22:01 +0000, Jon Roadley-Battin a= =C3=A9crit : > Hi thanks,=20 > If I can get this sorted and can easily emerge stuff I can push on > with getting this into Portage as well as seeing if I can help > I have uploaded the cofig.log to my ISP server-space. >=20 > http://fluidmotion.pwp.blueyonder.co.uk/config.log >=20 > From it it seems that configure cannot find DB4, yet it is saved in > the default (Gentoo default) place. > The includes are located at: >=20 > /usr/include/db4.2=20 >=20 > with /usr/include/db.h being a symlink to /usr/include/db4.2/db.h > I actually made a symlink to db4.2 called just db4 in /usr/include to > see if that was the problem (no joy). >=20 At the db4 check, there are 2 steps. 1- numexp-core searches for the /usr/include/db4/db.h but if it doesn't find it,... 2- it searches for /usr/include/db.h So I can see on your config.log you made the symlink to db4.2 I don't think the problem is there.. On my box, the first test fails. But the second one is good. So you can remove your link... :-) On your config.log, the little C testing program is compiled but it hurts on that : configure:23892: i686-pc-linux-gnu-gcc -o conftest -O3 -march=3Dpentium4 -fforce-addr -pipe -fomit-frame-pointer conftest.c /usr/lib/libdb.a >&5 /usr/lib/libdb.a(mut_pthread.o): In function `__db_pthread_mutex_init_4002': mut_pthread.c:(.text+0x8c): undefined reference to `pthread_mutexattr_destroy' mut_pthread.c:(.text+0x173): undefined reference to `pthread_condattr_setpshared' mut_pthread.c:(.text+0x18e): undefined reference to `pthread_mutexattr_init' mut_pthread.c:(.text+0x1b1): undefined reference to `pthread_mutexattr_setpshared' /usr/lib/libdb.a(mut_pthread.o): In function `__db_pthread_mutex_lock_4002': mut_pthread.c:(.text+0x1f9): undefined reference to `pthread_mutex_trylock' You can find those functions in /usr/include/pthread.h or the files called from this one. On my box, all them come with the glibc... You said you added ~x64 ~ppc to KEYWORDS. Shouldn't it be ~amd64 ~ppc ? I have no knowledge about ebuild files, but I can see amd64 more often than x64. (maybe I'm wrong... ;-)) I hope all this will help you... :-) Tell us. Regards David. |