Gentoo Archives: gentoo-user

From: Mick <michaelkintzios@×××××.com>
To: gentoo-user <gentoo-user@l.g.o>
Subject: [gentoo-user] Cloned partition won't emerge some packages
Date: Sat, 08 Jan 2011 23:19:16
Message-Id: AANLkTim-cJVNnbo_=n14Cvujzv9_hYaitTYvBvR1vw9X@mail.gmail.com
1 I used:
2
3 tar -X file.list -lcvSf - . | (cd /new_gentoo_partition; tar -xpvf - )
4
5 to clone a gentoo / partition to another partition on the same disk (I
6 want to run some tests from it).
7
8 The file.list has this is in it:
9
10 tmp/*
11 proc/*
12 sys/*
13 dev/*
14 etc/mtab
15 usr/portage/distfiles/*
16
17
18 However, I can't emerge some packages from it like gcc or subversion ...
19
20 This is what gcc shows:
21 =============================
22 checking for suffix of executables... yes
23 checking whether i686-pc-linux-gnu-gcc accepts -g...
24 checking for suffix of object files...
25 checking for suffix of object files... yes
26 checking for i686-pc-linux-gnu-gcc option to accept ANSI C... o
27 checking whether we are using the GNU C compiler... o
28 checking whether we are using the GNU C compiler... yes
29 checking whether i686-pc-linux-gnu-gcc accepts -g... yes
30 checking whether i686-pc-linux-gnu-gcc accepts -g... yes
31 checking for i686-pc-linux-gnu-gcc option to accept ANSI C... yes
32 checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
33 checking for special C compiler options needed for large files... no
34 checking for _FILE_OFFSET_BITS value needed for large files... none needed
35 no
36 checking for _LARGE_FILES value needed for large files... none needed
37 checking for special C compiler options needed for large files... no
38 checking for _FILE_OFFSET_BITS value needed for large files...
39 checking build system type... i686-pc-linux-gnu
40 no
41 checking host system type... checking how to run the C preprocessor...
42 i686-pc-linux-gnu
43 checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
44 checking for library containing strerror... no
45 checking for _LARGE_FILES value needed for large files... none required
46 checking how to run the C preprocessor... no
47 checking how to run the C preprocessor... /lib/cpp
48 configure: error: in
49 `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/build-i686-pc-linux-gnu/libiberty':
50 configure: error: C preprocessor "/lib/cpp" fails sanity check
51 See `config.log' for more details.
52 /lib/cpp
53 /lib/cpp
54 configure: error: in `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/intl':
55 configure: error: C preprocessor "/lib/cpp" fails sanity check
56 See `config.log' for more details.
57 make[2]: *** [configure-build-libiberty] Error 1
58 make[2]: *** Waiting for unfinished jobs....
59 configure: error: in
60 `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/libiberty':
61 configure: error: C preprocessor "/lib/cpp" fails sanity check
62 See `config.log' for more details.
63 make[2]: *** [configure-stage1-intl] Error 1
64 make[2]: *** [configure-stage1-libiberty] Error 1
65 make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
66 make[1]: *** [stage1-bubble] Error 2
67 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
68 make: *** [bootstrap-lean] Error 2
69 emake failed
70 * ERROR: sys-devel/gcc-4.4.4-r2 failed:
71 * emake failed with bootstrap-lean
72 *
73 * Call stack:
74 * ebuild.sh, line 56: Called src_compile
75 * environment, line 4988: Called toolchain_src_compile
76 * environment, line 5583: Called gcc_src_compile
77 * environment, line 3138: Called gcc_do_make
78 * environment, line 2925: Called die
79 * The specific snippet of code:
80 * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
81 LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET}
82 || die "emake failed with ${GCC_MAKE_TARGET}";
83 *
84 * If you need support, post the output of 'emerge --info
85 =sys-devel/gcc-4.4.4-r2',
86 =============================
87
88 I don't understand what this is about: "configure: error: C
89 preprocessor "/lib/cpp" fails sanity check"
90
91 I attach the config.log which has some errors in it.
92
93 Have you come across anything like this in your travels?
94
95 I don't really know what's wrong with the cloned system or how to fix it. :-(
96 --
97 Regards,
98 Mick

Attachments

File name MIME type
config.log text/plain

Replies

Subject Author
Re: [gentoo-user] Cloned partition won't emerge some packages Daniel D Jones <ddjones@××××××××××××.org>
Re: [gentoo-user] Cloned partition won't emerge some packages Alex Schuster <wonko@×××××××××.org>