public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gnugcc at marino dot st" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47052] make: *** [configure-target-libstdc++-v3] Error 1 Cross compile GCC for Alpha Architecture Date: Sat, 07 Apr 2012 06:49:00 -0000 [thread overview] Message-ID: <bug-47052-4-AtIWH6frqD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47052-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47052 John Marino <gnugcc at marino dot st> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gnugcc at marino dot st --- Comment #3 from John Marino <gnugcc at marino dot st> 2012-04-07 06:48:47 UTC --- For what it's worth, this report is *not* invalid. I'm attempting to cross-compile libstdc++-v3 from FreeBSD 9.0 to ARMv5 using gcc 4.6.3 (the latest of the 4.6 series) and I'm hitting this error too. In fairness, it's a patched version of gcc 4.6.3 to target Android on ARM. This was an attempt to extend the existing lang/gnatdroid-armv5 cross-compiler port on FreeBSD to include c++, objC, and Fortran. The commonality between the original report and mine is the cross-compile. maybe that's the case where the configure test is lacking.
next prev parent reply other threads:[~2012-04-07 6:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-23 14:02 [Bug libstdc++/47052] New: " wen.jian.ongx at gmail dot com 2010-12-30 17:04 ` [Bug libstdc++/47052] " rwild at gcc dot gnu.org 2011-01-03 13:36 ` paolo.carlini at oracle dot com 2011-01-27 14:47 ` paolo.carlini at oracle dot com 2012-04-07 6:49 ` gnugcc at marino dot st [this message] 2012-04-07 7:20 ` gnugcc at marino dot st
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=bug-47052-4-AtIWH6frqD@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).