public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yuri at tsoft dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/47536] gcc-4.5.2 fails to build on Solaris 10 i386 Date: Sun, 30 Jan 2011 23:13:00 -0000 [thread overview] Message-ID: <bug-47536-4-uOaeME72pS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47536-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47536 --- Comment #7 from Yuri <yuri at tsoft dot com> 2011-01-30 22:03:50 UTC --- Actually g++ produces the correct assembler file, but still calls original Sun assembler /usr/ccs/bin/as instead of the GNU one from the path, regardless of the option --with-gnu-as passed to gcc configure. Removing /usr/ccs/bin/as fixes the problem. So there are two issues with gcc-4.5.2 on Solaris: 1. Inability to detect GNU assembler in path (unwarranted requirement to pass --with-gnu-as). Broken build when either no GNU assembler in path or no option --with-gnu-as passed. 2. GNU assembler from path isn't used by g++, causing Sun assembler to fail on GNU-formatted assembler file.
next prev parent reply other threads:[~2011-01-30 22:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-29 22:33 [Bug c++/47536] New: " yuri at tsoft dot com 2011-01-29 22:36 ` [Bug c++/47536] " pinskia at gcc dot gnu.org 2011-01-29 22:40 ` yuri at tsoft dot com 2011-01-30 1:23 ` yuri at tsoft dot com 2011-01-30 11:48 ` yuri at tsoft dot com 2011-01-30 22:28 ` yuri at tsoft dot com 2011-01-30 22:40 ` redi at gcc dot gnu.org 2011-01-30 23:13 ` yuri at tsoft dot com [this message] 2011-01-30 23:27 ` yuri at tsoft dot com 2011-01-31 0:46 ` redi at gcc dot gnu.org 2011-01-31 1:40 ` yuri at tsoft dot com 2011-01-31 10:16 ` ebotcazou 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-47536-4-uOaeME72pS@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).