Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 262869 - Gentoo lzma emerging app-arch/lzma-utils-4.32.7
Summary: Gentoo lzma emerging app-arch/lzma-utils-4.32.7
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-18 02:20 UTC by Craig
Modified: 2009-12-27 17:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
environment log (lzma,82.40 KB, text/plain)
2009-03-18 02:21 UTC, Craig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Craig 2009-03-18 02:20:40 UTC
trying to get x11 to work cant install many things
one bug said try using revdep-rebuild && emerge gcc and i did that am still getting the issue. so i assume its a different bug. any help would be great. not a pro at gentoo but not a noob to linux.


build log below 

>>> 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=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-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 x86_64-pc-linux-gnu-g++... x86_64-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
 [31;01m*[0m 
 [31;01m*[0m ERROR: app-arch/lzma-utils-4.32.7 failed.
 [31;01m*[0m Call stack:
 [31;01m*[0m               ebuild.sh, line   49:  Called src_compile
 [31;01m*[0m             environment, line 2153:  Called _eapi0_src_compile
 [31;01m*[0m               ebuild.sh, line  607:  Called econf
 [31;01m*[0m               ebuild.sh, line  543:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m   			die "econf failed"
 [31;01m*[0m  The die message:
 [31;01m*[0m   econf failed
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant.
 [31;01m*[0m A complete build log is located at '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/env>>> 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=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-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 x86_64-pc-linux-gnu-g++... x86_64-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
 [31;01m*[0m 
 [31;01m*[0m ERROR: app-arch/lzma-utils-4.32.7 failed.
 [31;01m*[0m Call stack:
 [31;01m*[0m               ebuild.sh, line   49:  Called src_compile
 [31;01m*[0m             environment, line 2153:  Called _eapi0_src_compile
 [31;01m*[0m               ebuild.sh, line  607:  Called econf
 [31;01m*[0m               ebuild.sh, line  543:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m   			die "econf failed"
 [31;01m*[0m  The die message:
 [31;01m*[0m   econf failed
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant.
 [31;01m*[0m A complete build log is located at '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/environment'.
 [31;01m*[0m ironment'.
 [31;01m*[0m 

Reproducible: Always

Steps to Reproduce:
emerge -avuDN worle or
Comment 1 Craig 2009-03-18 02:21:29 UTC
Created attachment 185370 [details]
environment log
Comment 2 Rafał Mużyło 2009-03-18 02:52:27 UTC
Please, attach something more useful,
like that config.log.
Comment 3 Rafał Mużyło 2009-03-18 02:54:33 UTC
Though I suspect this is the reason:
CXXFLAGS='{CFLAGS}'
a typo in the make.conf, should probably be:
CXXFLAGS='${CFLAGS}'
Comment 4 Craig 2009-03-18 03:14:45 UTC
thanks you are great WOOT thanks for the help. the ${CFLAGS} was missing