From: "Stoyan Zoubev" <s_zoubev@prosyst.bg>
To: "CrossGCC" <crossgcc@sources.redhat.com>
Subject: Error building binutils for HP PA-RASC target
Date: Tue, 24 Oct 2000 05:48:00 -0000 [thread overview]
Message-ID: <012101c03dc1$162379a0$0bcea8c0@psb> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Hi,
Â
I am trying to build a cross compiler for HP
PA-RISC target on an Intel-based Linux machine, following the instructions
in "Getting started with Linux/PARISC: How to Build the Toolchain"( http://thepuffingroup.com/parisc/recipe.html )
:
I am using binutils-2.10, gcc-2.95.2, glibc-2.1.3.
And when I run
Â
<path to binutils sources>/configure
--host=i386-linux --prefix=/opt/parisc -- \ Â Â Â
   target=hppa-linux --enable-targets=hppa64-linux
--disable-nls
Â
I get the following error:
...
*** BFD does not support target
hppa64-linux. *** Look in bfd/config.bfd for supported targets.
Configure in /home/zoubev/build/binutils/opcodes
failed, exiting.
Â
Can someone explain me what the problem
is?Â
Â
Best regards,
St.Zoubev
reply other threads:[~2000-10-24 5:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='012101c03dc1$162379a0$0bcea8c0@psb' \
--to=s_zoubev@prosyst.bg \
--cc=crossgcc@sources.redhat.com \
/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).