public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld dot DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/39150] Configure scripts have no 64-Bit Solaris defined (only i386-solaris*). Date: Tue, 20 Jul 2010 19:21:00 -0000 [thread overview] Message-ID: <20100720192047.1857.qmail@sourceware.org> (raw) In-Reply-To: <bug-39150-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #17 from ro at CeBiTec dot Uni-Bielefeld dot DE 2010-07-20 19:20 ------- Subject: Re: Configure scripts have no 64-Bit Solaris defined (only i386-solaris*). > ------- Comment #16 from rob1weld at aol dot com 2010-07-20 19:02 ------- > (In reply to comment #15) >> (In reply to comment #13) >> OpenSolaris recently added support for the ARM Processor, so that adds a few >> more 'multi-lib modes' that need to be supported, along with the expanded line True, but irrelevant: each port only supports the multilibs it needs, and not several different configurations with each from the set of multilibs becoming the default. >> of SPARC Processors now being supported. The OpenSolaris Group also has a 'call >> for Ports', so in theory our mechanism _must_ be general enough to support any >> possible Processor ... The mechanism is, of course. > Additional note for this RFE (which _might_ get re-opened, someday): > > OpenSolaris now runs on mips-sun-solaris2.11 > http://hub.opensolaris.org/bin/view/Project+mips/Tools Far from it: there are minimal binutils and gcc patches yet, nothing more. Rainer -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39150
next prev parent reply other threads:[~2010-07-20 19:21 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-11 4:14 [Bug bootstrap/39150] New: " rob1weld at aol dot com 2009-02-11 20:56 ` [Bug bootstrap/39150] " pinskia at gcc dot gnu dot org 2009-02-12 13:36 ` rob1weld at aol dot com 2009-02-13 8:37 ` rob1weld at aol dot com 2009-02-13 9:12 ` rob1weld at aol dot com 2009-02-16 13:12 ` rob1weld at aol dot com 2009-10-23 12:13 ` grobian at gentoo dot org 2010-04-28 19:55 ` ro at gcc dot gnu dot org 2010-04-28 19:56 ` ro at gcc dot gnu dot org 2010-04-28 20:55 ` ro at gcc dot gnu dot org 2010-04-28 22:10 ` ebotcazou at gcc dot gnu dot org 2010-04-28 22:18 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-05-04 7:21 ` rob1weld at aol dot com 2010-05-06 19:27 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-05-06 19:54 ` ebotcazou at gcc dot gnu dot org 2010-05-17 2:34 ` rob1weld at aol dot com 2010-07-20 19:02 ` rob1weld at aol dot com 2010-07-20 19:21 ` ro at CeBiTec dot Uni-Bielefeld dot DE [this message] 2010-07-21 23:17 ` rob1weld at aol dot com 2010-07-22 11:50 ` rob1weld at aol dot com 2010-08-30 16:36 ` rwild at gcc dot gnu dot org [not found] <bug-39150-4@http.gcc.gnu.org/bugzilla/> 2011-07-06 11:38 ` ro at gcc dot gnu.org 2011-07-07 9:26 ` ro at gcc dot gnu.org 2011-07-07 10:02 ` ro at gcc dot gnu.org 2011-07-18 16:40 ` ro 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=20100720192047.1857.qmail@sourceware.org \ --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).