Gentoo Archives: gentoo-embedded

From: Natanael Copa <mlists@××××××.org>
To: gentoo-embedded@l.g.o
Subject: [gentoo-embedded] more problems with gdbm
Date: Thu, 22 Sep 2005 16:01:54
Message-Id: 4332D527.1020101@tanael.org
1 I have more problems with gdbm.
2
3 The "emerge -e world" died with:
4
5 gcc -march=i386 -Os -pipe -fomit-frame-pointer -D_REENTRANT
6 -D_POSIX_PTHREAD_SEMANTICS -DOPENSSL_NO_KRB5 -Wall -D_GNU_SOURCE
7 -DNDEBUG -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I../../include -c
8 rlm_counter.c -o rlm_counter.o
9 rlm_counter.c:38:18: gdbm.h: No such file or directory
10 distcc[11435] ERROR: compile rlm_counter.c on 192.168.65.159 failed
11 gmake[6]: *** [rlm_counter.o] Error 1
12 gmake[6]: Leaving directory
13 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2/src/modules/rlm_counter'
14 gmake[5]: *** [common] Error 1
15 gmake[5]: Leaving directory
16 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2/src/modules'
17 gmake[4]: *** [all] Error 2
18 gmake[4]: Leaving directory
19 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2/src/modules'
20 gmake[3]: *** [common] Error 1
21 gmake[3]: Leaving directory
22 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2/src'
23 gmake[2]: *** [all] Error 2
24 gmake[2]: Leaving directory
25 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2/src'
26 gmake[1]: *** [common] Error 1
27 gmake[1]: Leaving directory
28 `/var/tmp/portage/freeradius-1.0.2-r5/work/freeradius-1.0.2'
29 make: *** [all] Error 2
30
31 There is a gdbm.h file in /usr/include/gdbm.
32
33 I managed to work around it with CFLAGS=".... -I/usr/include/gdbm"
34 freeradius.
35
36 Looks like there are several problems with gdbm around here. Cound this
37 be related to the python problem? while it was possible to recompile
38 freeradius with -I/usr/include/gdbm python still failed with the linker
39 error.
40
41 --
42 Natanael Copa
43 --
44 gentoo-embedded@g.o mailing list

Replies

Subject Author
Re: [gentoo-embedded] more problems with gdbm Mike Frysinger <vapier@g.o>