public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wen.jian.ongx at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47052] New: make: *** [configure-target-libstdc++-v3] Error 1 Cross compile GCC for Alpha Architecture Date: Thu, 23 Dec 2010 14:02:00 -0000 [thread overview] Message-ID: <bug-47052-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47052 Summary: make: *** [configure-target-libstdc++-v3] Error 1 Cross compile GCC for Alpha Architecture Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: wen.jian.ongx@gmail.com Hi there ,, I'm Cross compiling a GNU GCC for Alpha Architecture on my i686-pc-linux-gnu machine. The crosstool that I used is gcc-4.0.2-glibc-2.3.6 and the output is shown below , checking if alpha-unknown-linux-gnu-gcc supports -fno-rtti -fno-exceptions ... no checking whether the linker (alpha-unknown-linux-gnu-ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... GNU/Linux ld.so checking command to parse alpha-unknown-linux-gnu-nm output... ok checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool updating cache ./config.cache configure: loading cache ./config.cache checking how to run the C++ preprocessor... /lib/cpp loading cache ./config.cache within ltconfig checking host system type... alpha-unknown-linux-gnu checking build system type... i686-pc-linux-gnu ltcf-cxx.sh: error: problem compiling test program checking for objdir... .libs checking for alpha-unknown-linux-gnu-c++ option to produce PIC... -DPIC checking if alpha-unknown-linux-gnu-c++ PIC flag -DPIC works... no checking if alpha-unknown-linux-gnu-c++ static flag works... no finding the maximum length of command line arguments... (cached) 49153 checking if alpha-unknown-linux-gnu-c++ supports -c -o file.o... (cached) yes checking whether the linker (alpha-unknown-linux-gnu-ld) supports shared libraries... checking how to hardcode library paths into programs... unsupported checking whether stripping libraries is possible... yes checking dynamic linker characteristics... GNU/Linux ld.so checking command to parse alpha-unknown-linux-gnu-nm output... failed checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes appending configuration tag "CXX" to libtool checking for exception model to use... configure: error: unable to detect exception model make: *** [configure-target-libstdc++-v3] Error 1
next reply other threads:[~2010-12-23 14:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-23 14:02 wen.jian.ongx at gmail dot com [this message] 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 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@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).