From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cxx/nocxx error building gcc-4.5.3-r1
Date: Thu, 08 Dec 2011 10:27:50 +0100 [thread overview]
Message-ID: <4EE08316.2000303@fu-berlin.de> (raw)
In-Reply-To: <4EE07D8D.1030101@fu-berlin.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just for clarification:
- -* means -cxx and -nocxx
This can produce the failure you get. Therefore you should set cxx
(normally you should want a c++ compiler).
If you have "-* cxx nocxx ...." you will have to remove one of the two
useflags.
Hinnerk
On 08.12.2011 10:04, Hinnerk van Bruinehsen wrote:
> Hi,
>
> since you have not posted your specific USE-flags, it gets harder
> to help you. I think you could try to add cxx to your USE-flags. If
> the does not help you, you should post your USE-flags and
> eventually the output of emerge --info to make it easier for us to
> help you.
>
> regards
>
> Hinnerk
>
> On 08.12.2011 09:15, Walter Dnes wrote:
>> I'm doing a fresh 32-bit install on an older Dell with an AMD
>> K8, for experimentation. I'm getting a build failure on gcc as
>> listed below. I start off my USE variable with "-*" and then add
>> on stuff as necessary. A Google search turned up
>> http://www.gossamer-threads.com/lists/gentoo/dev/242446 where
>> vapier says...
>
>>> this way when i do cut over from USE=nocxx to USE=cxx, we
>>> don't end up with users missing C++ compilers simply because
>>> they have old make.conf settings that started out with: USE="-*
>>> ..."
>
>> That appears to be relavant to me. But I'm not a developer, and
>> I don't claim to totally understand what he's talking about. I
>> do have some ebuilds that use C++. Should I add "cxx" to my USE
>> variable? The build error message follows...
>
>> * Fixing misc issues in configure files * Applying
>> gcc-configure-texinfo.patch ... * Touching generated files *
>> Touching gcc/cstamp-h.in * Touching gcc/config.in * Touching
>> libjava/aclocal.m4 * Touching libjava/Makefile.in * Touching
>> libjava/configure * Applying gcc-spec-env.patch ...
>>>>> Source unpacked in
>>>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work Compiling
>>>>> source in
>>>>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3 ...
>> * CFLAGS="-O2 -march=native -pipe" * CXXFLAGS="-O2 -march=native
>> -pipe" * Configuring gcc ... * We are migrating USE=nocxx to
>> USE=cxx, but your USE settings do not make * sense. Please make
>> sure these two flags line up logically in your setup. * ERROR:
>> sys-devel/gcc-4.5.3-r1 failed (compile phase): * USE='cxx
>> nocxx' and USE='-cxx -nocxx' make no sense * * Call stack: *
>> ebuild.sh, line 56: Called src_compile * environment, line
>> 4463: Called toolchain_src_compile * environment, line 5158:
>> Called gcc_do_configure * environment, line 2417: Called die
>> * The specific snippet of code: * die "USE='cxx
>> nocxx' and USE='-cxx -nocxx' make no sense"; *
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJO4IMVAAoJEJwwOFaNFkYcBEoIAJMvgDfaMmjs4fsW+JQTUhyG
TRvZ9/izNITIhdFR0uA0Qv6bdCUIMl65WlhV7GqKwxanO8CMrtM50uX5KxgzdgS7
6f5o8v/AFGLFAg6MsZjGIGHaovmtlgB0K2qbj1N6GA031Ldj9OWEZj7LeCCm4WsO
MaKZ5DCSV5INY8B6aYLeLrW0Ojo3RrwYAzXax5OhxdJ1FhxH6cM51dOg+vxMXrac
QBJj7xzU4vs7SrsrMUFQuBEHZEheSYjIYVXRwlYYEL1vTzGOPloaCso8RzGvapGr
GVTkad1o4+VbAEpWDA4psktWeeyTUlLRdXkTvUKwfemV/MuMBeBnejEcsC7gNtU=
=YEpY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-12-08 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 8:15 [gentoo-user] cxx/nocxx error building gcc-4.5.3-r1 Walter Dnes
2011-12-08 9:04 ` Hinnerk van Bruinehsen
2011-12-08 9:27 ` Hinnerk van Bruinehsen [this message]
2011-12-09 0:45 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE08316.2000303@fu-berlin.de \
--to=h.v.bruinehsen@fu-berlin.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox