| Summary: | sci-physics/root-5.34.00 USE=c++0x - ? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mathieu Segaud <mathieu.segaud> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | kredba |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mathieu Segaud
2012-06-28 11:13:43 UTC
Please attach the entire build log to this bug report. /usr/portage/sci-physics/root/root-5.34.00.ebuild: line 144: version_is_at_least: command not found ^[[33;01m*^[[0m You are using a g++ without C++0x capabilities ^[[31;01m*^[[0m ERROR: sci-physics/root-5.34.00 failed (setup phase): ^[[31;01m*^[[0m Need an C++0x capable compiler (In reply to comment #1) > Please attach the entire build log to this bug report. ... no need to attach, it's short so I'll paste it here: * Package: sci-physics/root-5.34.00 * Repository: gentoo * Maintainer: bircoph@gmail.com sci-physics@gentoo.org * USE: X amd64 c++0x doc elibc_glibc examples fftw graphviz kernel_linux math multilib opengl openmp reflex ssl userland_GNU * FEATURES: compressdebug installsources sandbox splitdebug * There are extra options on packages not yet in Gentoo: * AliEn, castor, Chirp, dCache, gfal, gLite, Globus, * HDFS, Monalisa, MaxDB/SapDB, SRP. * You can use the env variable EXTRA_ECONF variable for this. * For example, for SRP, you would set: * EXTRA_ECONF="--enable-srp --with-srp-libdir=/usr/lib64" * You are using a g++ without C++0x capabilities * ERROR: sci-physics/root-5.34.00 failed (setup phase): * Need an C++0x capable compiler * * Call stack: * ebuild.sh, line 85: Called pkg_setup * root-5.34.00.ebuild, line 146: Called die * The specific snippet of code: * die "Need an C++0x capable compiler" * * If you need support, post the output of `emerge --info '=sci-physics/root-5.34.00'`, * the complete build log and the output of `emerge -pqv '=sci-physics/root-5.34.00'`. * The complete build log is located at '/var/log/portage/sci-physics:root-5.34.00:20120628-121738.log.gz'. * For convenience, a symlink to the build log is located at '/var/tmp/p2/portage/sci-physics/root-5.34.00/temp/build.log.gz'. * The ebuild environment file is located at '/var/tmp/p2/portage/sci-physics/root-5.34.00/temp/die.env'. * Working directory: '/var/tmp/p2/portage/sci-physics/root-5.34.00' * S: '/var/tmp/p2/portage/sci-physics/root-5.34.00/work/root' By the way to all the bugwranglers, with all due respect, sticking strictly to the rules with a trivial bug(typo) like this one, i.e. requesting emerge --info or full build log, could needlessy piss off the users which are reporting bugs. You really should decide where this is needed (like for example we _really_ have too much bugs to squash), that the risk to loosing reporters is of less importance. The bug opener has described exactly the bug in two sentences. The ONLY thing he could have mentioned is that versionator.eclass is not even inherited by the ebuild, when it should be obviously. P.S. emerge --info make often no sense after the introduction of /etc/portage/env, it lies, lie even applied to the single package. It's important to document build failures so that other people using the same bug tracker can find them before filing duplicate bug reports. Since no build failure output was given, I requested it. I don't see how that could be wrong from anyone's perspective. |
