public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "josephpattara at gmail 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:35:00 -0000 [thread overview]
Message-ID: <bug-64919-4-KKBPAGUKxt@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 #13 from Joseph John <josephpattara at gmail dot com> ---
Yes. i also tried without the mlp64 option both for building the 4.7.4 and also
for building the 4.9.2 using the 4.7.4 but again I have the same issue. Means.
* 4.7.4 build is successful.
* 4.9.2 build fails at libstdc++-v3 as below.
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/type_traits:471:60:
error: template argument 1 is invalid
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/type_traits:479:62:
error: template argument 1 is invalid
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/type_traits:483:63:
error: template argument 1 is invalid
In file included from
/home/jjohn/hpux/gcc_492/gcc-4.9.2/libstdc++-v3/include/precompiled/stdc++.h:103:0:
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/future:1509:5:
error: looser throw specifier for 'virtual
std::__future_base::_Async_state_commonV2::~_Async_state_commonV2()'
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/future:316:15:
error: overriding 'virtual
std::__future_base::_State_baseV2::~_State_baseV2() noexcept (true)'
In file included from
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/regex:57:0,
from
/home/jjohn/hpux/gcc_492/gcc-4.9.2/libstdc++-v3/include/precompiled/stdc++.h:108:
/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include/bits/regex_automaton.h:159:24:
error: 'std::__detail::_NFA_base::_NFA_base' names constructor
Makefile:1596: recipe for target
'ia64-hp-hpux11.31/bits/stdc++.h.gch/O2ggnu++0x.gch' failed
make[5]: *** [ia64-hp-hpux11.31/bits/stdc++.h.gch/O2ggnu++0x.gch] Error 1
make[5]: Leaving directory
'/home/jjohn/hpux/gcc_492/gcc_build/ia64-hp-hpux11.31/libstdc++-v3/include'
The reason I went with using the mpl64 option was with out that option when I
was doing a 4.9.2 building using the GCC 4.2.3 which was available by default I
was getting the linker issue which is specified in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577. The only way I got get pass
the linker errro just after the libbackend.a creation was using the -mlp64
option for 4.9.2 build.
Were you successful in making the 4.9.2 build?
next prev parent reply other threads:[~2015-10-20 15:35 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 [this message]
2015-10-20 15:51 ` jvb at cyberscience dot com
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-KKBPAGUKxt@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).