public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvb at cyberscience dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/64919] bootstrap failure of gcc-4.9.2 on ia64-hpux in libgcc Date: Tue, 20 Oct 2015 15:51:00 -0000 [thread overview] Message-ID: <bug-64919-4-UrlAMHs0xX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64919 --- Comment #14 from John Buddery <jvb at cyberscience dot com> --- I did get a working 4.9.2 build, with the workaround from my earlier comment. It's a 32 bit build, bootstrapped with the hp 4.6.2 gcc distribution, my config line was: $ ../gcc-4.9.2/configure --disable-libgomp --with-as=/opt/hp-gcc/bin/as --enable-languages=c,c++ --prefix=/usr/local/gcc-4.9.2 --with-gmp=/usr/local/gcc-4.9.2 --with-mpc=/usr/local/gcc-4.9.2 --with-mpfr=/usr/local/gcc-4.9.2 I don't remember any errors in libstdc++. I would recommend installing gawk if you haven't already - the HP awk can cause issues when building gcc.
next prev parent reply other threads:[~2015-10-20 15:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-64919-4@http.gcc.gnu.org/bugzilla/> 2015-02-03 13:48 ` tgard at opentext dot com 2015-04-27 9:55 ` jvb at cyberscience dot com 2015-07-27 4:20 ` alm at sibmail dot ru 2015-07-27 4:44 ` alm at sibmail dot ru 2015-07-27 10:01 ` jvb at cyberscience dot com 2015-07-29 4:23 ` alm at sibmail dot ru 2015-10-19 16:46 ` josephpattara at gmail dot com 2015-10-20 5:35 ` alm at sibmail dot ru 2015-10-20 15:35 ` josephpattara at gmail dot com 2015-10-20 15:51 ` jvb at cyberscience dot com [this message] 2021-04-16 21:30 ` 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-64919-4-UrlAMHs0xX@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).