public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "felix-gcc at fefe dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53240] New: gcc 4.7 cross compiler build fails in libssp; link test not allowed after GCC_NO_EXECUTABLES Date: Fri, 04 May 2012 21:54:00 -0000 [thread overview] Message-ID: <bug-53240-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53240 Bug #: 53240 Summary: gcc 4.7 cross compiler build fails in libssp; link test not allowed after GCC_NO_EXECUTABLES Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: felix-gcc@fefe.de checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. make[1]: *** [configure-target-libssp] Error 1 make[1]: Leaving directory `/home/leitner/cross-build/arm/obj/gcc3' make: *** [all] Error 2 I ran the original configure with --target=arm-linux-gnueabi --prefix=/opt/cross --with-sysroot=/opt/cross/arm-linux-gnueabi --enable-languages=c,c++ The eglibc documentation on how to get a cross toolchain recommends disabling SSP, but I need SSP! That's an integral security feature, it needs to work!
next reply other threads:[~2012-05-04 21:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-04 21:54 felix-gcc at fefe dot de [this message] 2012-05-04 22:05 ` [Bug bootstrap/53240] " pinskia at gcc dot gnu.org 2012-05-04 22:30 ` felix-gcc at fefe dot de 2012-05-04 22:42 ` pinskia at gcc dot gnu.org
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-53240-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).