public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: ellen@tteng.com.br, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, weber@informatik.fh-trier.de Subject: Re: c/5443: build cross compiler gcc 3.0.2 - as: unrecognized option `-x' Date: Mon, 21 Jan 2002 18:33:00 -0000 [thread overview] Message-ID: <20020122023357.3604.qmail@sources.redhat.com> (raw) Synopsis: build cross compiler gcc 3.0.2 - as: unrecognized option `-x' State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Mon Jan 21 18:33:57 2002 State-Changed-Why: Did you follow all the instructions for building a cross compiler at: http://gcc.gnu.org/onlinedocs/gcc-3.0.2/gcc_4.html#SEC58 and: http://www.objsw.com/CrossGCC/ You need to build an IA64 capable version of binutils. The as command will then have a -x option. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5443
next reply other threads:[~2002-01-22 2:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-21 18:33 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-28 12:36 Damian Weber 2002-01-28 12:33 rodrigc 2002-01-21 7:36 weber
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=20020122023357.3604.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=ellen@tteng.com.br \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=weber@informatik.fh-trier.de \ /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).