KH schrieb: > Hi, > > I seem to have som problem here. > >>>> Emerging (3 of 107) app-arch/lzma-utils-4.32.7 > * lzma-4.32.7.tar.gz RMD160 SHA1 SHA256 size ;-) > ... > > [ ok ] > * checking ebuild checksums ;-) > ... > > [ ok ] > * checking auxfile checksums ;-) > ... > > [ ok ] > * checking miscfile checksums ;-) > ... > > [ ok ] >>>> Unpacking source... >>>> Unpacking lzma-4.32.7.tar.gz to > /var/tmp/portage/app-arch/lzma-utils-4.32.7/work >>>> Source unpacked in /var/tmp/portage/app-arch/lzma-utils-4.32.7/work >>>> Compiling source in > /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7 ... > * econf: updating lzma-4.32.7/config.guess with > /usr/share/gnuconfig/config.guess > * econf: updating lzma-4.32.7/config.sub with > /usr/share/gnuconfig/config.sub > ./configure --prefix=/usr --host=i486-pc-linux-gnu > --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share > --sysconfdir=/etc --localstatedir=/var/lib --build=i486-pc-linux-gnu > checking if debugging code should be compiled... no > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking for i486-pc-linux-gnu-g++... i486-pc-linux-gnu-g++ > checking for C++ compiler default output file name... > configure: error: C++ compiler cannot create executables > See `config.log' for more details. > > !!! Please attach the following file when seeking support: > !!! /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/config.log > * > * ERROR: app-arch/lzma-utils-4.32.7 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 2100: Called _eapi0_src_compile > * ebuild.sh, line 607: Called econf > * ebuild.sh, line 543: Called die > * The specific snippet of code: > * die "econf failed" > * The die message: > * econf failed > * > * If you need support, post the topmost build error, and the call stack > if relevant. > * A complete build log is located at > '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/environment'. > * > >>>> Failed to emerge app-arch/lzma-utils-4.32.7, Log file: > >>>> '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/build.log' > > > I am using the new gcc with CFLAGS="-O2 -march=native -mtune=native > -pipe". I am able to emerge -av1 glibc and binutils plus gcc itselve.I > cannot run the eav system because of the above error. > Any hint? > GIve us the /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/config.log, then we will tell you more.
signature.asc
Description: OpenPGP digital signature
