Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Moving a gentoo installation from VM to hardware
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
eohrnberger
Apprentice
Apprentice


Joined: 09 Dec 2004
Posts: 240

PostPosted: Sun Nov 24, 2013 4:15 pm    Post subject: Moving a gentoo installation from VM to hardware Reply with quote

So, I wanted to build a pure 64 bit gentoo installation, at least as much as possible. I started the project as a VirtualBox VM, and now I want to move this built instance of gentoo Linux from VM to native on hardware.

I've tarred off the VM's file systems to the file server on the network from within the VM booting from a 64 bit installation CD ISO image, and now have laid those tars down on a hard disk while running off the installation CD on the hardware. Chrooted into the environment and installed grub boot loader, and it boots OK. So far so good.

But there are problems. When I try to compile a simple 'hello world' C program as a test, I get the following compilation error:

In file included from /usr/include/stdio.h:28:0,
from test.c:1:
/usr/include/features.h:358:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.

If I take the #include <stdio.h> line out, it complies and runs correctly. So that's good.

If I try and re-emerge gcc to get the missing headers back (I should have them in the tar ball, eh? Probably not the right thing to do anyway) emerge reports:

configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/libdecnumber':
configure: error: C preprocessor "/lib/cpp" fails sanity check

WTF?

I've included build.log, but there are multiple config.log and I don't see how I could 'attach' gcc-build-logs.tar.bz2 to this post.

Where am I missing a step? There must be something that I'm missing to make this work correctly. A tar of a system should be moveable between hardware, how else would you recover from a hardware failure?

Code:

 * Package:    sys-devel/gcc-4.7.3-r1
 * Repository: gentoo
 * Maintainer: toolchain@gentoo.org
 * USE:        abi_x86_64 amd64 cxx elibc_glibc fortran gtk kernel_linux mudflap multilib nls nptl openmp userland_GNU
 * FEATURES:   ccache distcc preserve-libs userpriv usersandbox
>>> Unpacking source...
>>> Unpacking gcc-4.7.3.tar.bz2 to /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
>>> Unpacking gcc-4.7.3-patches-1.3.tar.bz2 to /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
>>> Unpacking gcc-4.7.3-uclibc-patches-1.0.tar.bz2 to /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
>>> Unpacking gcc-4.7.3-piepatches-v0.5.5.tar.bz2 to /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
>>> Unpacking gcc-4.4.3-specs-0.2.0.tar.bz2 to /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
 * Applying Gentoo patches ...
 *   10_all_default-fortify-source.patch ...
 [ ok ]
 *   11_all_default-warn-format-security.patch ...
 [ ok ]
 *   12_all_default-warn-trampolines.patch ...
 [ ok ]
 *   15_all_libgfortran-Werror.patch ...
 [ ok ]
 *   15_all_libgomp-Werror.patch ...
 [ ok ]
 *   16_all_libgo-Werror-pr53679.patch ...
 [ ok ]
 *   17_all_libitm-Werror.patch ...
 [ ok ]
 *   18_all_libgcc-cross-canadian.patch ...
 [ ok ]
 *   25_all_alpha-mieee-default.patch ...
 [ ok ]
 *   26_all_alpha-asm-mcpu.patch ...
 [ ok ]
 *   29_all_arm_armv4t-default.patch ...
 [ ok ]
 *   30_all_arm_armv4-no-thumb-fix-link.patch ...
 [ ok ]
 *   33_all_armhf.patch ...
 [ ok ]
 *   34_all_ia64_note.GNU-stack.patch ...
 [ ok ]
 *   38_all_sh_pr24836_all-archs.patch ...
 [ ok ]
 *   39_all_gfortran-sysroot-pr54725.patch ...
 [ ok ]
 *   42_all_superh_default-multilib.patch ...
 [ ok ]
 *   48_all_x86_pr53113_libitm-avx.patch ...
 [ ok ]
 *   49_all_x86_pr52695_libitm-m64.patch ...
 [ ok ]
 *   50_all_libiberty-asprintf.patch ...
 [ ok ]
 *   51_all_libiberty-pic.patch ...
 [ ok ]
 *   52_all_netbsd-Bsymbolic.patch ...
 [ ok ]
 *   67_all_gcc-poison-system-directories.patch ...
 [ ok ]
 *   74_all_gcc47_cloog-dl.patch ...
 [ ok ]
 *   Skipping 90_all_gcc-4.7-x32.patch due to EPATCH_EXCLUDE ...
 *   91_all_4.8.0_arm-plugin-headers.patch ...
 [ ok ]
 *   92_all_freebsd-pie.patch ...
 [ ok ]
 *   93_all_4.8.0_gengtype-lex_parallel_build.patch ...
 [ ok ]
 *   94_all_pr57777-O3-avx2.patch ...
 [ ok ]
 *   95_all_4.7.4_mxop-wrong-code.patch ...
 [ ok ]
 *   96_all_4.7.4_PR57269-ICE-gconv_open.patch ...
 [ ok ]
 *   97_all_native-ivybridge.patch ...
 [ ok ]
 * Done with patching
 * Applying uClibc patches ...
 *   90_all_100-uclibc-conf.patch ...
 [ ok ]
 *   90_all_301-missing-execinfo_h.patch ...
 [ ok ]
 *   90_all_302-c99-snprintf.patch ...
 [ ok ]
 *   90_all_305-libmudflap-susv3-legacy.patch ...
 [ ok ]
 * Done with patching
 * Applying pie patches ...
 *   01_all_gcc47_configure.patch ...
 [ ok ]
 *   02_all_gcc47_config.in.patch ...
 [ ok ]
 *   03_all_gcc47_Makefile.in.patch ...
 [ ok ]
 *   05_all_gcc47_gcc.c.patch ...
 [ ok ]
 *   06_all_gcc46_esp.h.patch ...
 [ ok ]
 *   10_all_gcc46_default-ssp.patch ...
 [ ok ]
 *   15_all_gcc44_decl-tls-model.patch ...
 [ ok ]
 *   16_all_gcc47_nopie_option.patch ...
 [ ok ]
 *   20_all_gcc46_config_crtbeginp.patch ...
 [ ok ]
 *   24_all_gcc44_invoke.texi.patch ...
 [ ok ]
 *   33_all_gcc46_config_rs6000_linux64.h.patch ...
 [ ok ]
 * Done with patching
 * updating multilib directories to be: ../lib64 ../lib32
 * Running elibtoolize in: gcc-4.7.3/
 *   Applying portage/2.2 patch ...
 *   Applying sed/1.5.6 patch ...
 *   Applying as-needed/2.2.6 patch ...
 * Using GNU config files from /usr/share/gnuconfig
 *   Updating config.sub
 [ ok ]
 *   Updating libjava/classpath/config.sub
 [ ok ]
 *   Updating libjava/libltdl/config.sub
 [ ok ]
 *   Updating config.guess
 [ ok ]
 *   Updating libjava/classpath/config.guess
 [ ok ]
 *   Updating libjava/libltdl/config.guess
 [ ok ]
 * Fixing misc issues in configure files
 * Applying gcc-configure-texinfo.patch ...
 [ ok ]
 * Touching generated files
 *   Touching gcc/cstamp-h.in
 *   Touching gcc/config.in
 *   Touching libitm/aclocal.m4
 *   Touching libitm/Makefile.in
 *   Touching libitm/testsuite/Makefile.in
 *   Touching libitm/configure
 *   Touching libitm/config.h.in
 * Applying gcc-spec-env.patch ...
 [ ok ]
>>> Source unpacked in /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work
>>> Compiling source in /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3 ...
 * CFLAGS="-O2 -pipe"
 * CXXFLAGS="-O2 -pipe"
 * Configuring gcc ...
 * configuring for GCC_LANG: c,c++,fortran

 * PREFIX:         /usr
 * BINPATH:         /usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3
 * LIBPATH:         /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3
 * DATAPATH:      /usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3
 * STDCXX_INCDIR:   /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4

 * Configuring GCC with:
 *    --prefix=/usr
 *    --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3
 *    --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include
 *    --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3
 *    --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man
 *    --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info
 *    --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4
 *    --host=x86_64-pc-linux-gnu
 *    --build=x86_64-pc-linux-gnu
 *    --disable-altivec
 *    --disable-fixed-point
 *    --without-cloog
 *    --without-ppl
 *    --disable-lto
 *    --enable-nls
 *    --without-included-gettext
 *    --with-system-zlib
 *    --enable-obsolete
 *    --disable-werror
 *    --enable-secureplt
 *    --enable-multilib
 *    --with-multilib-list=m32,m64
 *    --enable-libmudflap
 *    --disable-libssp
 *    --enable-libgomp
 *    --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python
 *    --enable-checking=release
 *    --disable-libgcj
 *    --enable-libstdcxx-time
 *    --enable-languages=c,c++,fortran
 *    --enable-shared
 *    --enable-threads=posix
 *    --enable-__cxa_atexit
 *    --enable-clocale=gnu
 *    --enable-targets=all
 *    --with-bugurl=http://bugs.gentoo.org/
 *    --with-pkgversion=Gentoo 4.7.3-r1 p1.3, pie-0.5.5

/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --without-cloog --without-ppl --disable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --enable-multilib --with-multilib-list=m32,m64 --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python --enable-checking=release --disable-libgcj --enable-libstdcxx-time --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion=Gentoo 4.7.3-r1 p1.3, pie-0.5.5
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for libitm support... yes
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... unsupported
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking for x86_64-pc-linux-gnu-gnatbind... no
checking for gnatbind... no
checking for x86_64-pc-linux-gnu-gnatmake... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2
checking for objdir... .libs
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... yes
*** This configuration is not supported in the following subdirectories:
     zlib target-zlib target-libjava gnattools target-libada target-libgo target-libffi target-libobjc target-libssp target-boehm-gc
    (Any other directories should still work fine.)
checking for default BUILD_CONFIG... bootstrap-debug
checking for bison... bison -y
checking for bison... bison
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for expect... expect
checking for runtest... no
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-as... x86_64-pc-linux-gnu-as
checking for x86_64-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for ld... (cached) /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld
checking for x86_64-pc-linux-gnu-ld... (cached) /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld
checking for x86_64-pc-linux-gnu-lipo... no
checking for lipo... no
checking for x86_64-pc-linux-gnu-nm... x86_64-pc-linux-gnu-nm
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for x86_64-pc-linux-gnu-windres... no
checking for windres... no
checking for x86_64-pc-linux-gnu-windmc... no
checking for windmc... no
checking for x86_64-pc-linux-gnu-objcopy... x86_64-pc-linux-gnu-objcopy
checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
checking for x86_64-pc-linux-gnu-readelf... x86_64-pc-linux-gnu-readelf
checking for cc... cc
checking for c++... c++
checking for gcc... gcc
checking for gcj... no
checking for gfortran... gfortran
checking for gccgo... no
checking for ar... /usr/x86_64-pc-linux-gnu/bin/ar
checking for as... /usr/x86_64-pc-linux-gnu/bin/as
checking for dlltool... no
checking for dlltool... no
checking for ld... /usr/x86_64-pc-linux-gnu/bin/ld
checking for lipo... no
checking for lipo... no
checking for nm... /usr/x86_64-pc-linux-gnu/bin/nm
checking for objdump... /usr/x86_64-pc-linux-gnu/bin/objdump
checking for ranlib... /usr/x86_64-pc-linux-gnu/bin/ranlib
checking for readelf... /usr/x86_64-pc-linux-gnu/bin/readelf
checking for strip... /usr/x86_64-pc-linux-gnu/bin/strip
checking for windres... no
checking for windres... no
checking for windmc... no
checking for windmc... no
checking where to find the target ar... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target as... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target cc... just compiled
checking where to find the target c++... just compiled
checking where to find the target c++ for libstdc++... just compiled
checking where to find the target dlltool... host tool
checking where to find the target gcc... just compiled
checking where to find the target gcj... host tool
checking where to find the target gfortran... just compiled
checking where to find the target gccgo... host tool
checking where to find the target ld... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target lipo... host tool
checking where to find the target nm... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target objdump... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target ranlib... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target readelf... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target strip... pre-installed in /usr/x86_64-pc-linux-gnu/bin
checking where to find the target windres... host tool
checking where to find the target windmc... host tool
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether -fkeep-inline-functions is supported... yes
configure: creating ./config.status
config.status: creating Makefile
 * Compiling gcc ...
make -j6 'LDFLAGS=-Wl,-O1 -Wl,--as-needed' STAGE1_CFLAGS= LIBPATH=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3 'BOOT_CFLAGS=-m64 -O2 -pipe' bootstrap-lean
echo stage3 > stage_final
make[1]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
make[2]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
make[2]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
mkdir -p -- build-x86_64-pc-linux-gnu/libiberty
Configuring in build-x86_64-pc-linux-gnu/libiberty
mkdir -p -- build-x86_64-pc-linux-gnu/fixincludes
Configuring in build-x86_64-pc-linux-gnu/fixincludes
Configuring stage 1 in ./intl
Configuring stage 1 in ./libiberty
Configuring stage 1 in ./libdecnumber
configure: creating cache ../config.cache
configure: loading cache ../config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... makeinfo --split-size=5000000 --split-size=5000000
checking for perl... perl
checking build system type... checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking host system type... configure: creating cache ./config.cache
checking whether make sets $(MAKE)... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
configure: creating cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... configure: creating cache ./config.cache
makeinfo --split-size=5000000 --split-size=5000000
checking whether make sets $(MAKE)... x86_64-pc-linux-gnu
checking target system type... checking for perl... perl
yes
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether NLS is requested... yes
x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking build system type... checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for xgettext... x86_64-pc-linux-gnu
checking host system type... /usr/bin/xgettext
x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for msgmerge... /usr/bin/msgmerge
checking for C compiler default output file name... checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... a.out
checking whether the C compiler works... yes
checking for C compiler default output file name... checking whether we are cross compiling... no
checking for suffix of executables... checking for C compiler default output file name...
checking for suffix of object files... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... a.out
checking whether the C compiler works... o
checking whether we are using the GNU C compiler... yes
checking whether we are cross compiling... no
checking for suffix of executables... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89...
checking for suffix of object files... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g...
checking for suffix of object files... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... unsupported
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for aclocal... aclocal
checking for autoconf... autoconf
checking for autoheader... autoheader
unsupported
checking how to run the C preprocessor... checking whether x86_64-pc-linux-gnu-gcc supports -W... yes
checking whether x86_64-pc-linux-gnu-gcc supports -Wall... yes
unsupported
checking whether x86_64-pc-linux-gnu-gcc supports -Wwrite-strings... unsupported
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... checking build system type... yes
checking whether x86_64-pc-linux-gnu-gcc supports -Wstrict-prototypes... x86_64-pc-linux-gnu
checking host system type... yes
x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for library containing strerror... checking whether x86_64-pc-linux-gnu-gcc supports -Wmissing-prototypes... yes
checking whether x86_64-pc-linux-gnu-gcc supports -Wold-style-definition... /lib/cpp
yes
a.out
checking whether the C compiler works... checking whether x86_64-pc-linux-gnu-gcc supports -Wmissing-format-attribute... yes
checking whether we are cross compiling... no
checking for suffix of executables... none required
checking how to run the C preprocessor... unknown
checking for _LARGE_FILES value needed for large files... yes
checking whether x86_64-pc-linux-gnu-gcc supports -Wcast-qual... configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/build-x86_64-pc-linux-gnu/fixincludes':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
yes
checking whether x86_64-pc-linux-gnu-gcc supports -pedantic -Wlong-long... yes
checking how to run the C preprocessor...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... make[2]: *** [configure-build-fixincludes] Error 1
make[2]: *** Waiting for unfinished jobs....
yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... unknown
checking how to run the C preprocessor... /lib/cpp
configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/intl':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
/lib/cpp
make[2]: *** [configure-stage1-intl] Error 1
configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/libdecnumber':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
/lib/cpp
make[2]: *** [configure-stage1-libdecnumber] Error 1
configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/libiberty':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
unsupported
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... make[2]: *** [configure-stage1-libiberty] Error 1
unknown
checking for _LARGE_FILES value needed for large files... unknown
checking how to run the C preprocessor... /lib/cpp
configure: error: in `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/build-x86_64-pc-linux-gnu/libiberty':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
make[2]: *** [configure-build-libiberty] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
 * ERROR: sys-devel/gcc-4.7.3-r1::gentoo failed (compile phase):
 *   emake failed with bootstrap-lean
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4285:  Called toolchain_src_compile
 *   environment, line 4987:  Called gcc_do_make
 *   environment, line 2521:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 *
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.7.3-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.7.3-r1::gentoo'`.
 *
 * Please include /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-build-logs.tar.bz2 in your bug report.
 *
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3'
[/code]
Back to top
View user's profile Send private message
croutch
n00b
n00b


Joined: 04 Aug 2012
Posts: 32
Location: göteborg

PostPosted: Sun Nov 24, 2013 4:40 pm    Post subject: Reply with quote

When i google this error line from your log configure error c preprocessor /lib/cpp fails sanity check gentoo.

I found thoes posts.

https://forums.gentoo.org/viewtopic-t-226590-start-0.html

https://forums.gentoo.org/viewtopic.php?t=294108
Back to top
View user's profile Send private message
eohrnberger
Apprentice
Apprentice


Joined: 09 Dec 2004
Posts: 240

PostPosted: Sun Nov 24, 2013 4:51 pm    Post subject: Reply with quote

croutch wrote:
When i google this error line from your log configure error c preprocessor /lib/cpp fails sanity check gentoo.

I found thoes posts.

https://forums.gentoo.org/viewtopic-t-226590-start-0.html

https://forums.gentoo.org/viewtopic.php?t=294108


Thanks for the pointer, I tried as the post suggests: emerge --ask --verbose --oneshot linux-headers

However, that results in the following error message:

Code:

>>> Install linux-headers-3.9 into /var/tmp/portage/sys-kernel/linux-headers-3.9/image/ category sys-kernel
make -j6 headers_install INSTALL_HDR_PATH=/var/tmp/portage/sys-kernel/linux-headers-3.9/image///usr/include/.. ARCH=x86 CROSS_COMPILE=x86_64-pc-linux-gnu-
  CHK     include/generated/uapi/linux/version.h
  UPD     include/generated/uapi/linux/version.h
  WRAP    arch/x86/include/generated/asm/clkdev.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
  SYSTBL  arch/x86/syscalls/../include/generated/asm/syscalls_32.h
  HOSTCC  arch/x86/tools/relocs
In file included from /usr/include/stdio.h:28:0,
                 from arch/x86/tools/relocs.c:1:
/usr/include/features.h:358:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.


I'm thinking that sort sort of hardware dependent pointer or directory symlink is wrong, as we've changed the hardware, from the VM to the actual native hardware. What and where it is, I have no idea, and this is just a guess on my part.
Back to top
View user's profile Send private message
newbenji
n00b
n00b


Joined: 05 Sep 2003
Posts: 69
Location: Denmark, Odense

PostPosted: Tue Feb 10, 2015 9:38 am    Post subject: Reply with quote

eohrnberger wrote:
croutch wrote:
When i google this error line from your log configure error c preprocessor /lib/cpp fails sanity check gentoo.

I found thoes posts.

https://forums.gentoo.org/viewtopic-t-226590-start-0.html

https://forums.gentoo.org/viewtopic.php?t=294108


Thanks for the pointer, I tried as the post suggests: emerge --ask --verbose --oneshot linux-headers

However, that results in the following error message:

Code:

>>> Install linux-headers-3.9 into /var/tmp/portage/sys-kernel/linux-headers-3.9/image/ category sys-kernel
make -j6 headers_install INSTALL_HDR_PATH=/var/tmp/portage/sys-kernel/linux-headers-3.9/image///usr/include/.. ARCH=x86 CROSS_COMPILE=x86_64-pc-linux-gnu-
  CHK     include/generated/uapi/linux/version.h
  UPD     include/generated/uapi/linux/version.h
  WRAP    arch/x86/include/generated/asm/clkdev.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_32.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_64.h
  SYSHDR  arch/x86/syscalls/../include/generated/uapi/asm/unistd_x32.h
  SYSTBL  arch/x86/syscalls/../include/generated/asm/syscalls_32.h
  HOSTCC  arch/x86/tools/relocs
In file included from /usr/include/stdio.h:28:0,
                 from arch/x86/tools/relocs.c:1:
/usr/include/features.h:358:25: fatal error: sys/cdefs.h: No such file or directory
compilation terminated.


I'm thinking that sort sort of hardware dependent pointer or directory symlink is wrong, as we've changed the hardware, from the VM to the actual native hardware. What and where it is, I have no idea, and this is just a guess on my part.


Sorry taking this on up.
Did you ever solve this one as i have same problem
Back to top
View user's profile Send private message
eohrnberger
Apprentice
Apprentice


Joined: 09 Dec 2004
Posts: 240

PostPosted: Wed Feb 11, 2015 12:40 am    Post subject: Reply with quote

No, never did figure it out, but built the system from scratch, via the Gentoo Handbook. Oh well.
Back to top
View user's profile Send private message
newbenji
n00b
n00b


Joined: 05 Sep 2003
Posts: 69
Location: Denmark, Odense

PostPosted: Wed Feb 11, 2015 7:28 am    Post subject: Reply with quote

eohrnberger wrote:
No, never did figure it out, but built the system from scratch, via the Gentoo Handbook. Oh well.

Solved it.

The recommended rsync with exlude sys excluded this dir offcourse..
Back to top
View user's profile Send private message
k2t0f12d
n00b
n00b


Joined: 04 Aug 2011
Posts: 5

PostPosted: Wed Feb 25, 2015 7:17 am    Post subject: Reply with quote

newbenji wrote:
eohrnberger wrote:
No, never did figure it out, but built the system from scratch, via the Gentoo Handbook. Oh well.

Solved it.

The recommended rsync with exlude sys excluded this dir offcourse..


Ding ding ding ding ding

Same problem trying to clone one KVM vhost to another with tar --exlude=sys! Oops, heh.
Back to top
View user's profile Send private message
newbenji
n00b
n00b


Joined: 05 Sep 2003
Posts: 69
Location: Denmark, Odense

PostPosted: Wed Feb 25, 2015 7:33 am    Post subject: Reply with quote

k2t0f12d wrote:
newbenji wrote:
eohrnberger wrote:
No, never did figure it out, but built the system from scratch, via the Gentoo Handbook. Oh well.

Solved it.

The recommended rsync with exlude sys excluded this dir offcourse..


Ding ding ding ding ding

Same problem trying to clone one KVM vhost to another with tar --exlude=sys! Oops, heh.


Then i hope this solved it :-)
Back to top
View user's profile Send private message
steveL
Watchman
Watchman


Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery

PostPosted: Wed Feb 25, 2015 2:58 pm    Post subject: Reply with quote

--exclude=/sys iirc. (ie full path)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum